Router is upset.
September 13, 2005 on 2:20 pm | In Foobars, Updates by Josh Jones | 9 CommentsWe’re now having some problems with our core router (most likely due to the power stuff yesterday) and are experiencing a lot of packet loss to many customers.
We’re working on it as hard as we can!
We’ll post when we have more news.. hopefully you’ll be able to get here to read it.
9 Responses to “Router is upset.”
Powered by WordPress. Pool theme by Borja Fernandez, modified by DreamHost.
Like WordPress? Consider attending WordCamp LA.
Entries and comments feeds.
^Top^
September 13th, 2005 at 2:32 pm
Having problems will mail coming through. It seems to be trickling but I’m wondering about mail that was received during the downtime. Is it in queue and can be expected to arrive, or… ??
(I just sent out multiple queries yesterday about vacation rentals and have gotten almost nothing back, when I should have gotten well over a hundred responses)
September 13th, 2005 at 2:41 pm
Latency seems higher but other than that it appears to be working fine for me.
PING willscorner.net (66.33.208.206): 56 data bytes
64 bytes from 66.33.208.206: icmp_seq=0 ttl=56 time=99.151 ms
64 bytes from 66.33.208.206: icmp_seq=1 ttl=56 time=101.968 ms
64 bytes from 66.33.208.206: icmp_seq=3 ttl=56 time=98.772 ms
64 bytes from 66.33.208.206: icmp_seq=4 ttl=56 time=98.649 ms
64 bytes from 66.33.208.206: icmp_seq=5 ttl=56 time=99.606 ms
64 bytes from 66.33.208.206: icmp_seq=6 ttl=56 time=100.422 ms
64 bytes from 66.33.208.206: icmp_seq=7 ttl=56 time=117.931 ms
64 bytes from 66.33.208.206: icmp_seq=8 ttl=56 time=108.904 ms
64 bytes from 66.33.208.206: icmp_seq=9 ttl=56 time=107.854 ms
I usually get about 80ms and I’m off the global crossing uplink. Otherwise everything else seems fine. Thank you btw for bringing dedicated machine up first. My client was really happy :-)
September 13th, 2005 at 2:43 pm
Basically one of our core routers started behaving a little strangely, getting a high load, and then its active supervisor (which is pretty much it’s CPU) died.
The backup supervisor came online and it’s still up and running, but we’re still seeing a high load and a little packet loss.
We’re doing traffic analysis to see just what the hell’s going on (while we work on a bunch of other leftover issues from yesterday).
September 13th, 2005 at 2:46 pm
wow. sounds like you kids are really earning your salaries this week. thanks for all your hard work in trying to keep all of our websites etc. running!
September 13th, 2005 at 2:49 pm
Have you had any reports of SMTP not working? I can receive email, but not send. And it keeps asking me for a password each time I try to send (inputing the correct password doesn’t help).
September 13th, 2005 at 3:21 pm
Maybe you guys are having another DOS attack.
That would be prefect wouldn’t it.
September 13th, 2005 at 4:22 pm
No, we’re seeing normal traffic on our uplinks. If it was that I’d be at home in bed by now.
We’re talking to Cisco. I’m on my 6th Red Bull today! Should be fixed soon. Or soonish!
September 13th, 2005 at 4:39 pm
My site has slowed down to a trickle =/ Thanks for all the hard work to fix things though! It is much appreciated! :)
December 16th, 2005 at 5:00 pm
Just wanted to wonder… Is everything OK now? No further DDOS’s or anything of the kind?
Regards