Company Forums » Companies beginning with S » SnappyDSL.net (COFS.NET) > Outage?

Outage?

Looks like their connection to InterNAP is broken.

reply to pcmike
It's a DDOS. How hard is it to filter this crap COFS? Come on, 4hrs+ on a stupid DDOS. This is pathetic. I even told NOTA what the issue was and they're still sitting on their hands? It's really not that hard to filter this stuff..

I doubt it’s a DDOS, as it happened way too quick. I was surfing the web when it died, and it was like someone yanked the plug, and I have never seen a DDOS take down a connection that large so quickly, and completely. Also I should note I can only make just one hop out before it dies, and it used to take two before I left their network to their provider. So I’d say something is broke since I should be able to at least make it to their boarder router even if they were experiencing a DDOS attack.

Anyway, they are just down the street from me, so I am going to take a ride over there in the mourning if it isn’t up by then to see what’s happening. If it’s an equipment issue I can probably help them out, as my inventory of spare Cisco equipment is quite substantial, so I might have something laying around that could get them up if I can get a hold of them and work something out if and it's a router or switch that died.

reply to pcmike
My connection is back up, but very sluggish right now.

reply to pcmike
i could ping my gateway ip but that was all from around 9pm thru 3am last night 1/21/05, when i finally gave up. this morning, 1/22/05 is spotty and sluggish. i sent an email this morning with a copy to myself and i was able to get the copy back so i'm sure they got the message. i asked for info to be posted on the system status page. let's hope they have figured out what happened and have it fixed for good.

Well it looks like it’s partly up, but I am seeing a lot of packet loss between the gateway and the second hop, so access is dead slow. I tried calling, but only get the automated attendant. Guess I will try going by the office and see if I can find out what’s going on.

reply to pcmike
I was having DNS issues last night. Could ping my default gateway no problems but no replies to both primary and secondary DNS (I use Tampa, 63.146.194.41 & 63.146.194.57).
Didn't have the others on hand to see if I could get to them.

reply to Dr-IP
Well NOTA doesn't even seem to know what the problem was. I guess COFS thought it was a problem with NOTA cables and so the technicians are NOTA checked their cables with a Fluke and everything was fine. From there apparently someone from COFS showed up and ran ping/traceroutes constantly and things just happen to work themselves out, supposedly. The tech I spoke to was relaying the information he had heard for the tech who was working last night, so it night not all be true.

Anyhow, please let us know what the issue was (even if it was something stupid). I'm also not too happy that I never recieved a callback last night after alerting you to this situation at 9:50pm and in subsequent calls after that.

reply to pcmike
This morning I am still having something around 10% of packet loss (VOIP didn't like it at all , my mother in law was complaining)

reply to pcmike
here is a line quality test run a little while ago.
»/quality/nil/1630789
comments??

69.25.48.97, where the problem is, belongs to InterNAP, your ISP's upstream.

reply to pcmike
argh....this is aggravating man. I am thinking about going cable

reply to pcmike
Tell me about it. I had a voicemail at 8:50am saying that everything was up and fine. Far from it COFS. You need to deal with these packet issues. Everything is NOT up and fine. Something at NOTA is screwed up and needs to be fixed. I'm going out for lunch and what not so I can't call them and expect to be able to give them any helpful information when they call back, so hopefully one of you (ie. Dr-IP) can call and let them know the issue.

Come on COFS, fix this crap already on I might as well switch ISPs. This is a total failure on your part. We're going on ~10hrs of abysmal routes with very high packet loss.

reply to pcmike
I went by their office, looks like no one it there, so the action must all be at the CO. My guess is it’s some router or line between Bell South’s stuff and their POP, as it seems like everyone can at least make it to the DSLAM and their gateway, and it dies there.

“Well NOTA doesn't even seem to know what the problem was. I guess COFS thought it was a problem with NOTA cables and so the technicians are NOTA checked their cables with a Fluke and everything was fine. From there apparently someone from COFS showed up and ran ping/traceroutes constantly and things just happen to work themselves out, supposedly.”

As for strange problems, I ran into one Friday too with my primary MCI circuit at work. Pings and trace routes where perfect, but you couldn’t browse half the internet, yet you could ping the sites which allowed IMC echoes perfectly that you couldn’t connect too. They said there was nothing wrong on their side and tested the line, then blamed it on my equipment, so I changed the router which wasn’t fun since it’s the size of a small refrigerator, dropped all the access lists and nothing changed.

So I used a packet sniffer to see if I could figure out what was wrong. I found out not much was coming back, no surprise there, and what little came back was almost all corrupt with invalid checksums, something you should never see. So I killed the MCI pipe and rerouted traffic down a backup and the problem went away. At that point I called MCI back up and forced them to finally come clean since there was nothing else left for them to blame it on my side, and admit they had a problem with the backbone that they hadn’t been able to fix. I guess they figured they’d fix it before anyone could prove they were at fault.

reply to pcmike
connection is still spotty right now 12 noon 1/22/05.
anybody got eta for fix??

reply to Dr-IP
"argh....this is aggravating man. I am thinking about going cable"

I agree this is frustrating, but when cable goes on the fritz it’s just as bad, as I have run into quite a few people who have lost cable service for days at a time. So it’s not a cure all either. Unfortunately no one providing consumer internet access places much priority a repair services, so long outages are common.

What has really got me mad about the situation with Snappy DSL, is not that they haven’t got it fixed yet, as I know sometimes these kinds of problems can be real tricky to solve, it’s the fact they have left us in the dark as to what is going on. They have been down for over half a day, and they haven’t even posted a single thing about it on their status page, come one guys spend 10 minutes and let us know what is going on.

they have posted a notice on the system status page as of 2pm 1/22/05. evidently they still are having problems and have a partial fix in place and will try to have it fixed by monday.

It looks fixed now or at least it's well patched from where I am at. I am not seeing any packet loss from their boarder router, or anywhere else. So things are looking up, and I see the finally posted something about it almost after fact. It’s good they fixed it, but bad they kept us in the dark so long.

reply to pcmike
Quite frankly, I'd like to know what the exact problem was COFS. The entire issue smacks of a dos attack (ie. core router dropping packets, but everything else is fine). Either a dos attack or some piece of router hardware completely failed. Please clue us in.