Is anyone else out there having a bit of congestion getting to TX tonight? Things are slowing way down this evening..
This is a discussion on Anyone having network slowdowns? in the Open Discussion & Chit-chat forum
Is anyone else out there having a bit of congestion getting to TX tonight? Things are slowing way down this evening.. ...
Is anyone else out there having a bit of congestion getting to TX tonight? Things are slowing way down this evening..
Yeah, everything is kinda sucky!
I noticed that my site, which is getting 40k-50k pageviews a day, lately, is crawling the last few hours. Dittos for JagPC.
In MY case, it turned out to be mostly a bad RSS feed, but I figure it's all network related too, in view of recent outages the last couple of weeks ... so...
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
Did that make any sense?
I think JagPC is experiencing network difficulties lately, but it's probably totally out of their control. It's probably a problem with their various providers.
I've saw this happen years ago, when a single flakey router in UUNET slowed down the whole east coast for weeks...
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
Heh! I know... what's UUNET?
http://www.webopedia.com/TERM/U/UUNET.html
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
General overview.
Slow response from TX to TX for the past 2 hours.
Slow as hell to Boston
jaguarpc.com (69.73.128.132)
4 packets transmitted, 2 packets received, 50% packet loss
Host reachable, average round-trip time: 47.354 ms
50% packet loss, must be another DDOS attack?
Very astute!Originally Posted by muks
Except in my case...
Code:Microsoft(R) Windows DOS (C)Copyright Microsoft Corp 1990-1999. C:\>ping jaguarpc.com -n 100 Pinging jaguarpc.com [69.73.128.132] with 32 bytes of data: Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=90ms TTL=52 Reply from 69.73.128.132: bytes=32 time=96ms TTL=52 Reply from 69.73.128.132: bytes=32 time=96ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=80ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=84ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=93ms TTL=52 Reply from 69.73.128.132: bytes=32 time=89ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=92ms TTL=52 Reply from 69.73.128.132: bytes=32 time=86ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=85ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=102ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=131ms TTL=52 Reply from 69.73.128.132: bytes=32 time=114ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=163ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=80ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=87ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=134ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=98ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=103ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=96ms TTL=52 Reply from 69.73.128.132: bytes=32 time=84ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=84ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=84ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=91ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=82ms TTL=52 Reply from 69.73.128.132: bytes=32 time=81ms TTL=52 Reply from 69.73.128.132: bytes=32 time=83ms TTL=52 Ping statistics for 69.73.128.132: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 80ms, Maximum = 163ms, Average = 85ms
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
looks like they already fixed it
sites are loading fine now
By the way, before I posted the ping reply I filed a ticket and guess what they said
funny, i remember posting it must be a DDOS attackWe have updated your online support ticket.
We are facing a network issue due to a severe ddos. We are working on it and will fix it soon. Thank you for your co-operation in this regard."
--------
Regards,
Alex
OWNED
Last edited by muks; 06-27-2005 at 10:06 PM.
lol!Originally Posted by muks
Heh! I had a 26% packet loss the first time I pinged the server. I just kept running 'em until the timeouts went away...Originally Posted by muks
Sorry! Warped sense of humor...![]()
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
BTW, I wonder who's been getting hammered?!?!?
Seems like we've had a lot of syn attacks lately...
DISCLAIMER Any resemblance between the views expressed above and those of the owners and operators of this system is purely coincidental. Any resemblance between these views and my own are non-deterministic. The existence of Vin DSL is questionable. The existence of views in the absence of anyone to hold them is problematic. The existence of the reader is left as an exercise in the second-order coefficient.
There was an outgoing UDP flood that caused some problems last night and I apologize for not posting earlier about it. We have taken steps on most servers to avoid these types of attacks, but some servers were either missed or in this case, a vps instance, which is harder to control.
Copyright © 2011 JaguarPC.com
Bookmarks