You can get $$ back for the down time, you just have to call and request it.

 

MINE SUCK ***, it goes down every 30 mins

 

Really? I've never had problem with my cable internet! It's always fast and reliable, been a customer 2 years now.

My experience is opposite to some; I had the worst experience with DSL! I feel your pains!

 

! ! ! Mines Acting Up Right Now ! ! ! I Hate This Sh|t !

 

Or the fact that their DHCP lease times tend to be 7 days or so, so changing the DNS servers they push with DHCP wouldn't really do much good in the short term anyways. They need a short term solution that dosn't require every customer to issue a DHCPDISCOVER/DHCPREQUEST sequence.

To fix it quickly like they want to , they just need to get another server up.

I don't know exactly how their system is setup, but if I were going to design it (and yes, I had some collegaues who now work for Comcast, and they DO have smart people), I'd setup a loadbalanced cluster of DNS servers behind a single BGP-anycasted IP address.

 

Just wanted to apologize to all Comcast users for the outage. I'm a customer as well. Was downoading pr0n. All done now. Won't happen again.

Joe

 

yea, mine was out too, so I called their tech support and turns out they were having a nationwide outage. So I am assuming that meant that they were updating their servers.

-Ted

 

That is true, but what do most home users do with DSL/cable when there connection gets crappy? They power cycle the model, then their router. Though I do tend to forget not every home user is smart enough to do that. ;x

I am guessing their DNS servers were getting DoS'ed.

Loadbalancers cost money man, Comcast would be dishing out millions for a nationwide load balanced network.
For an ISP of their size they would need something more cost effective without a single point of failure(load balancer).

I wonder how many customers comcast has vs. SBC... hmmm.
I think Comcast probably has more since they are nation wide. :x

EDIT: I just thought about what you said vs. what I said about the load balancers. you said 'a' load balancer, for whatever reason I was thinking all over the place. lol
Still, a single point of failure, and a centrally located DNS cluster would be bad for a nation of cable modem users.

 

Man, you over estimate the intelligence of most users They think the cable modem is 'the brain' and wouldn't touch it even if it were catching their curtains on fire. I mean, I regularly cycle my modem, but my mother just assumes that its a 'bad Internet day' and ignores it for a few hours.

As far as loadbalancers - yeah they are pricey, but Comcast has the $$$. Any in either case, BGP anycasting is free if you know how to do it, does effective load balacing, regional routing and failover redundancy. Its just a huge PITA to setup. Heck, do the anycastings for a few (maybe 10) DNS server IPS, and make those IPs point to 10 different load blanaced clusters all over the nation. Instant nearly unkillable system (just add water + 1 good BGP architect)....heck, if it lets Akamai get through a slashdotting of huge grpahics without problems, I'm sure it can handle a few million 56-byte DNS hits.

And I'm sure Comcast's customer base blows SBC out of the water.

 

is comcast still having problems til today? im at work right now so i havent gone online at home yet.

-Ave

 

Are you using a wireless router? If so it could be someone using your access point. I have 3 access points that I can log on to from my place because no one has a password. Even if you have a key and password it can still be accessed with a bit of time. Sometimes people set up a network and log on to someone elses and never check to make sure it is theirs because it works.

 

I've been using it for about 2 months and mine rocks. I was DL'ing torrents last night and earlier today for 300-600k.

 

Mine didn't work until around 12:30 last night so I called them. I figured out that I forgot to enable my network connection and i also changed the DNS and forgot to set it back. All is well and back to normal here, but I found out that the problem was NATIONAL.