What is Digg?Warning: The Content in this Article May be Inaccurate
Readers have reported that this story contains information that may not be accurate.152 Comments
- jotate, on 08/14/2008, -3/+128Buried for misleading headline. This response is entirely stating that Time Warner is not responsible.
- Arkane308, on 08/14/2008, -3/+39If you read the article you see that this title is misleading. This article is about how TWC is explaining that there network is not to blame but the hops to the other network providers.
- shutaro, on 08/14/2008, -2/+32I blame Comcast!
- compgeek, on 08/14/2008, -0/+23Buried as inaccurate
- inactive, on 08/14/2008, -1/+20Changed your signal strength through DOS?
...
What the *****? - chrysrobyn, on 08/14/2008, -1/+18"Responds to" is different from "Responsible for". In this case, they're clearly stating that there is a problem, and they're actually pointing to the people whose fault it is, and it's not Time Warner.
- Slade605, on 08/14/2008, -0/+16Only if your life consists of sitting on a screen that says "Connecting.."
- darkane, on 08/14/2008, -3/+18"Responsible for"? I think the guy from TW just made a pretty good case that it has nothing to do with TW.
- megaton, on 08/14/2008, -1/+16This just in: the backbone affects ALL ISPs in the area.
- inactive, on 08/14/2008, -0/+14Are you ***** kidding me?
NOBODY CAN GUARANTEE QOS IF THE TRAFFIC TRAVERSES THE PUBLIC INTERNET.
That's why it's called the "public internet," because it traverses many carriers. If you ordered a private line (or a MPLS link that is routed over a single carrier) you can get QOS. Otherwise you're at the mercy of the Internet. - Nodnarbs, on 08/14/2008, -14/+27Getting DC'd from WoW is the best thing that can happen to a person. You can get back to your life now.
- MacSuxWindozSux, on 08/14/2008, -5/+19aww damn, I just buried another useless comment. Lovin' it.
- mauvehead, on 08/14/2008, -1/+13Did the submitter even read the article? No where do they claim responsibility for the disconnects. Half the traceroutes don't even touch the TWC network.
Welcome to digg! - inactive, on 08/14/2008, -1/+12Oh, I get it. Submitter wrote misleading title on purpose to stir up inane hatred, which is how it landed on the front page.
***** you, submitter. - AntFoolish, on 08/14/2008, -6/+17I predict a raid on a certain evil headquarters deep in the heart of Stamford, Connecticut. We must smite the evil cable overlords, and avail ourselves to their loot and women.
- inactive, on 08/14/2008, -1/+12READ THE ARTICLE, PLEASE.
- inactive, on 08/14/2008, -5/+16A little break from WoW probably wouldn't hurt some people. Just sayin'.
- FFXIfrohike, on 08/14/2008, -0/+10Agreed. Burento, you're an idiot.
- djscsi, on 08/14/2008, -0/+10Yes, i was just about to post this. Based on TW's (amateur) "analysis" of the problem, it looks like they have overloaded their connections with their peers. In the case of L3 for instance, the TW rep points to L3 as the cause of the problem, but in reality the issue is probably that TW has overloaded their private connection to L3 and needs to add more bandwidth or redundant links to their peers to reduce latency. Either way the article title is misleading and inaccurate. Also, WOW players probably need to get outside anyway so take this as a blessing in disguise.
- demigod, on 08/14/2008, -0/+10Whats interesting here is it looks like its the peer between TW and L3. There is always a possibility that it is a TW issue if they have crappy routes in the peering but more than likely its L3 either throttling the inc traffic from TW or they didn't allocate enough bandwidth on the TW peers.
[edit]If TW really wanted to look like the good guys here, they could open a line of communication with L3 about the peering but i get the feeling they wont and just let it hang until L3 contacts them. Unfortunately, this is pretty typical in backbone companies. - erasmus0284, on 08/14/2008, -0/+10Buried for irresponsible, sensationalist, inaccurate, and unfortunately predictable headline.
- megaton, on 08/14/2008, -0/+9Interesting. Mine tends to be plaid.
- FFXIfrohike, on 08/14/2008, -1/+10RTFA.
- X86BSD, on 08/14/2008, -0/+9BURIED! Jesus people come on quit LYING in the headlines with sensational headlines. It is getting really old.
- Demener, on 08/14/2008, -0/+8Buried for misleading title.
- inactive, on 08/14/2008, -0/+8-20 points for reading comprehension.
- icurnvs, on 08/14/2008, -1/+9I still don't 100% buy Time Warner's side of the story. The guy from Time Warner seemed to cherry-pick the specific instances where he could say that the issues weren't time warner's fault. Misleading title nontheless because the Consumerist article seems to lean on the side of it not being TW's fault.
- Bhatch514, on 08/14/2008, -2/+10LFG Comcast Headquarders Need DPS, Tank.
- inactive, on 08/14/2008, -0/+8I don't feel like waiting twenty years for FiOS, thank you.
- cmjM67, on 08/14/2008, -4/+12I'm from NYC, and I can say that Time Warner Cable ***** blows
- mrjd54, on 08/14/2008, -0/+7Buried. Total lie in the headline. Read the article, dumbass, before you submit it to digg.
- jdandre, on 08/14/2008, -1/+8What is with the title? That is not accurate, at all. What idiot posts stuff without reading it first.
- strictnein, on 08/14/2008, -0/+7That dang Pacific ocean.
- shipwreck58, on 08/14/2008, -2/+9Subject Line content does not match article content. Burried as innacurate..
- foofightrs777, on 08/14/2008, -0/+7She's a 133t h@x0r from 1991 and traveled to the future by modulating her time frequency in Windows 3.11 for Workgroups
- stealthc, on 08/14/2008, -0/+7Wow. The title is exactly the opposite of what the story is really about. Bravo, submitter.
- KaivenTor, on 08/14/2008, -0/+6From the post it looks like the problem is coming from Level3. Hopefully Time Warner will step up and pressure Level3 to get their routing up to par again. But even if Time Warner doesn't, start sending e-mail and phone calls towards Level3 and maybe that will eventually get the message through or at least get a better idea of exactly what's going on.
- Demener, on 08/14/2008, -0/+5Heroic?
- tflowholdings, on 08/14/2008, -0/+5Time Warner Cable doesnt care about WoW people
- Yarnage, on 08/14/2008, -0/+5This is correct. Marked as inaccurate.
- inactive, on 08/14/2008, -1/+6Ummm...no.
The idea that your last mile provider is somehow responsible for the entirety of the Internet is absurd. A private line is the only way to guarantee low latency, which is why any business that is serious about VOIP gets private lines. - Insanitation, on 08/14/2008, -0/+5Misleading? Its a strait up lie!
- mysticalone, on 08/14/2008, -1/+6Rogue in full greens, invite.
- FKnight, on 08/14/2008, -0/+5Buried for flat out lie of a headline.
- BobScratchit, on 08/14/2008, -0/+5LOL, at that rate you could right click an animal corpse to skin it then go and get something to eat and it would be done skinning about the time you got back.
- oxdeltaxo, on 08/14/2008, -0/+5The story pretty much passes the blame to the other isp's that are along the route to the WOW servers, specifically verizon was mentioned twice as being a trouble spot aswell as the backbones.
- pHreaksYcle, on 08/14/2008, -0/+4Dugg for not getting the point.
- Sonan, on 08/14/2008, -5/+9I guess consumerist.com accidentally left the word "Not" out of the title. They tend to do that kind of thing a lot...
- stealthyslyth, on 08/14/2008, -0/+4Amen to that. Horrible customer support, and in general my internet connection tends to be spotty.
- duckwaltz, on 08/14/2008, -0/+4This headline is misleading. If you actually read the blog, you'll notice that its author makes no claim one way or another as to who is responsible.
-
Show 51 - 100 of 154 discussions
Browsing Digg on your phone just got easier with our enhancements to the 
© Digg Inc. 2009
— Content created and posted by Digg users is