Anyone else suddenly seeing uber-sucky Comcast connectivity?

[hrafn.livejournal.com]

Is anyone else suddenly seeing many periods of zero connectivity from Comcast, starting immediately after the renumbering that took place Thursday the 26th between 0430 and 0600? I'd like to pursue this but need data before contacting them. Technical details below the cut.

Comcast renumbered me from one class-A to another (from net 24 to net 76); this was the fourth unannounced renumbering in less than 9 months, after years of stability. -Immediately- after this latest renumbering, I started experiencing over a dozen instances -a day- in which packets would stop (hung ssh conns, all pings fail, total DNS outage, traceroute fails at the first hop---apparently complete PHY failure), lasting for several minutes. Then, the cable modem (one of the 3Com sharkfins) would do its little bingBINGbingbong song, flash its lights, make little grumbling noises, and eventually bring the connection back up.

Nothing at all has changed in the interior wiring in years. Power-cycling the modem hasn't changed anything (of course, but I had to rule out screwed-up internal state). When I'm not getting zero connectivity, I'm getting excellent connectivity (few or no packet drops on the cablemodem part of the route). I get video from Comcast as well and it is also completely unaffected, making me extremely dubious that this could be any sort of physical cabling issue.

Instead, I think Comcast changed hardware somewhere at their cable headend simultaneously with the renumbering, and the new hardware sucks rocks. But I despair of convincing any of their first- or second-line script-reading drones (who will no doubt -insist- that I reboot my computer before anything else---riiiight), and would like some data before I waste a lot of time trying to escalate this to anyone in their NOC who has the first clue about how a network really works.

Thanks!

Comments

[badseed1980.livejournal.com]

I haven't noticed any connectivity problems, myself.

[thetathx1138.livejournal.com]

If you're not already a reader, hit up the Consumerist.

[hrafn.livejournal.com]

Maybe I am missing something (and I probably am, since I haven't spent a lot of time on it), but most of the articles they have are both old and not pertinent :\

[anyee.livejournal.com]

I've been noticing WoW-related connectivity issues. Three of us connecting from Boston to Seattle got dropped due to packet loss around LA. No one else did. Wonder why.

[laryu.livejournal.com]

Have not noticed any issues in this Comcast household lately.

[no1onthecorner.livejournal.com]

I don't know if this is relevant or helpful, but my household had problems not this past weekend, but the one before - the connection was slow to nonexistent, with periods of working okay, for a couple of days. It's been fine for the past week, as far as I know.

[m-b-w.livejournal.com]

We had almost a full day of outage (modem would not block-sync) on the 24th. It's been pretty stable since (and was very stable for a long time up until then)...
We did not get renumbered; we have had 24.x.x.x addresses for a long time and currently have one still.
Agreed that calling support is probably just an exercise in futility.

[geekpixie.livejournal.com]

That's interesting since we are now a 69, not a 24 or a 76 now. We did have issues about a week ago, but they seem to have resolved.

[xuth.livejournal.com]

I'm in Cambridge (closer to alewife than davis) and I got renumbered fairly recently from 65.x.x.x to 66.x.x.x. I've not noticed any actual problems, just the lost connections when it happens.