Fuck you Comcast

[Harrison]

I am fucking sick of their shit up here.

]Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Harrison!>tracert http://www.comcast.net

Tracing route to dcs.origin.comcast.akadns.net [216.148.227.202]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * 8 ms c-3-0-ubr01.newbedford.ma.boston.comcast.net [73
.172.12.1]
3 * 8 ms 32 ms ge-1-37-ur01.newbedford.ma.boston.comcast.net [6
8.87.154.1]
4 * * * Request timed out.
5 11 ms 9 ms 9 ms te-8-1-ur01.middleboro.ma.boston.comcast.net [68
.87.144.189]
6 * * 11 ms te-9-3-ur02.brockton.ma.boston.comcast.net [68.8
7.144.49]
7 * * * Request timed out.
8 32 ms * 11 ms po-12-ar02.needham.ma.boston.comcast.net [68.87.
146.45]
9 22 ms * 10 ms po-11-ar01.needham.ma.boston.comcast.net [68.87.
146.37]
10 * * * Request timed out.
11 75 ms 76 ms 75 ms gbr1.cb1ma.ip.att.net [12.127.5.30]
12 * 75 ms 76 ms tbr2.cgcil.ip.att.net [12.122.10.106]
13 100 ms 92 ms 76 ms tbr1.cgcil.ip.att.net [12.122.9.133]
14 83 ms 78 ms 75 ms tbr1.sffca.ip.att.net [12.122.10.6]
15 98 ms 77 ms 78 ms gar4.sffca.ip.att.net [12.123.13.174]
16 80 ms 80 ms 80 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
17 74 ms 80 ms 73 ms rwcsbix11-1-4.attbi.com [63.241.85.234]
18 76 ms 80 ms 77 ms http://www.comcast.net [216.148.227.202]

Trace complete.

C:\Documents and Settings\Harrison!>

This shit is ridiculous, it's going to take me 10 minutes just to submit this post. They are saying there is nothing wrong on their end.

If I understand my tracert correctly, their whole fucking MA network is sucking FAT COCK and it isn't their problem?

[Tikker]

what exactly is the problem?

all I see is a few nodes not responding to icmp (which isn't shocking)

[Jay]

PM kinghooter!

[Narrock]

What exactly is that... just basic IT stuff?

[Arlos]

Well, to be fair, most the stuff that isn't responding to ICMP is at least partially responding to it. (Look at hops 2, 3, 6, 8, 9, etc.) So, those COULD be timeouts on ping there, where he's getting a latency spike such that the ping times out. However, usually when that happens, you'll get a fair number of high-latency numbers at various spots in the traceroute too, and I'm not seeing that here.

Harrison, I realize it'll take a long time to download, but go find something called "Matt's Traceroute" (or it might just be known as WinMTR) and use that. It combines a traceroute with continuous pings to all the hops involved, including the terminal one. As a result, it gives you a much better picture of what the status of the intervening network is really like.

Here's a sample output from WinMTR, run from me to Nameless Tavern (gee, yes, I use NAT at my end! *gasp*):

Code: Select all

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   45 |   45 |    0 |   15 |   62 |   16 |
|                   No response from host -  100 |   45 |    0 |    0 |    0 |    0 |    0 |
|ge-3-21-ur06.sanjose.ca.sfba.comcast.net -    3 |   45 |   44 |    0 |    8 |   31 |   15 |
|te0-7-0-ar01.oakland.ca.sfba.comcast.net -   45 |   45 |   25 |    0 |   12 |   47 |   16 |
|                             68.86.85.77 -    0 |   45 |   45 |    0 |   15 |   47 |   31 |
|     COMCAST-IP.car2.SanJose1.Level3.net -    0 |   45 |   45 |    0 |   15 |   32 |   15 |
|         te-4-4.car2.SanJose1.Level3.net -    0 |   44 |   44 |    0 |   22 |  141 |   15 |
|         vlan99.csw4.SanJose1.Level3.net -    0 |   44 |   44 |   15 |   20 |   32 |   31 |
|       ae-92-92.ebr2.SanJose1.Level3.net -    0 |   44 |   44 |   15 |   19 |   31 |   16 |
|            ae-3.ebr1.Denver1.Level3.net -    0 |   44 |   44 |   31 |   47 |   63 |   63 |
|        ae-1-100.ebr2.Denver1.Level3.net -    0 |   44 |   44 |   31 |   44 |   78 |   47 |
|           ae-3.ebr3.Chicago1.Level3.net -    0 |   44 |   44 |   62 |   78 |   94 |   78 |
|          ae-78.ebr2.Chicago1.Level3.net -    0 |   44 |   44 |   62 |   77 |   94 |   79 |
|       ae-24-54.car4.Chicago1.Level3.net -    0 |   44 |   44 |   62 |   84 |  250 |  203 |
|    WBS-CONNECT.car4.Chicago1.Level3.net -    0 |   44 |   44 |   62 |   77 |  156 |   78 |
|             61.216-86-149.nozonenet.com -    0 |   44 |   44 |   62 |   84 |  250 |   62 |
|                      ensim1.netwisp.com -    0 |   44 |   44 |   62 |   74 |   94 |   78 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( stanimir@cr.nivis.com )

And yes, Mindia, it's very very basic IT stuff.

-Arlos

[Arlos]

OK, I just ran a MTR to the first hop router in Harrison's trace, and I see no problems in Comcast space whatsoever. I mean, it's a LITTLE slower than you might expect given the distance, but not egregiously slow, and I'm sure as hell not seeing any ping timeouts to any of the devices in the Mass area.

Much as I hate Comcast in general, this time they appear to be RIGHT, Harrison, there's nothing wrong in their space. You may well have a problem with your router, cable modem, a cable somewhere, etc. Here's the trace from me to Comcast's router.

Code: Select all

|----------------------------------------------------------------------------------------------|
|                                          WinMTR statistics                                   |
|                       Host                  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|----------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1     -    0 |   51 |   51 |    0 |    6 |   32 |    0 |
|                   No response from host     -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|ge-3-21-ur06.sanjose.ca.sfba.comcast.net     -    4 |   51 |   49 |    0 |    9 |   31 |   16 |
|te0-5-0-4-ar01.oakland.ca.sfba.comcast.net   -    0 |   51 |   51 |    0 |    9 |   16 |   16 |
|te-4-1-cr01.sacramento.ca.cbone.comcast.net  -    0 |   51 |   51 |    0 |   12 |   32 |   16 |
|te-9-1-cr01.losangeles.ca.cbone.comcast.net  -    0 |   51 |   51 |   15 |   20 |   32 |   15 |
|te-1-1-cr01.santateresa.tx.cbone.comcast.net -    0 |   50 |   50 |   31 |   40 |   78 |   47 |
|te-1-1-cr01.denverqwest.co.cbone.comcast.net -    0 |   50 |   50 |   62 |   73 |  109 |   78 |
| te-2-1-cr01.denver.co.cbone.comcast.net     -    0 |   50 |   50 |   46 |   64 |   79 |   78 |
|  te-1-1-cr01.omaha.ne.cbone.comcast.net     -    0 |   50 |   50 |   62 |   73 |   79 |   78 |
|te-1-1-cr01.chicago.il.cbone.comcast.net     -    0 |   50 |   50 |   78 |   80 |   94 |   78 |
|te-1-1-cr01.cleveland.oh.cbone.comcast.net   -    0 |   50 |   50 |   78 |   89 |  110 |   94 |
| te-9-1-cr01.boston.ma.cbone.comcast.net     -    0 |   50 |   50 |  109 |  115 |  172 |  109 |
|te-8-2-ar01.woburn.ma.boston.comcast.net     -    0 |   50 |   50 |  109 |  119 |  218 |  109 |
| po-10-ar02.woburn.ma.boston.comcast.net     -    0 |   50 |   50 |  109 |  117 |  141 |  109 |
|te-8-3-ur02.brockton.ma.boston.comcast.net   -    0 |   50 |   50 |  109 |  120 |  203 |  125 |
|te-9-1-ur01.middleboro.ma.boston.comcast.net -    0 |   50 |   50 |  109 |  119 |  156 |  125 |
|te-8-1-ur01.marion.ma.boston.comcast.net     -    0 |   50 |   50 |  109 |  125 |  203 |  140 |
|te-9-1-ur01.newbedford.ma.boston.comcast.net -    0 |   50 |   50 |  109 |  119 |  157 |  110 |
|c-3-0-ubr01.newbedford.ma.boston.comcast.net -    0 |   50 |   50 |  109 |  120 |  141 |  110 |
|____________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( stanimir@cr.nivis.com )

-Arlos

[Harrison]

That's because it FINALLY sorted itself out. It was going up and down before but it's fine now.

[Harrison]

Code: Select all

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Harrison!>tracert www.comcast.net

Tracing route to dcs.origin.comcast.akadns.net [216.148.227.202]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     9 ms     8 ms    10 ms  c-3-0-ubr01.newbedford.ma.boston.comcast.net [73
.172.12.1]
  3    17 ms    10 ms    11 ms  ge-1-37-ur01.newbedford.ma.boston.comcast.net [6
8.87.154.1]
  4     9 ms    10 ms     8 ms  te-9-1-ur01.marion.ma.boston.comcast.net [68.87.
144.181]
  5    13 ms    10 ms     9 ms  te-8-1-ur01.middleboro.ma.boston.comcast.net [68
.87.144.189]
  6    11 ms    10 ms    10 ms  te-9-3-ur02.brockton.ma.boston.comcast.net [68.8
7.144.49]
  7    12 ms    11 ms    10 ms  te-7-4-ar02.woburn.ma.boston.comcast.net [68.87.
144.41]
  8    11 ms    12 ms    15 ms  po-12-ar02.needham.ma.boston.comcast.net [68.87.
146.45]
  9    11 ms    12 ms    12 ms  po-11-ar01.needham.ma.boston.comcast.net [68.87.
146.37]
10    12 ms    13 ms    12 ms  12.116.130.173
11    75 ms    76 ms    77 ms  gbr1.cb1ma.ip.att.net [12.127.5.30]
12    78 ms    75 ms    75 ms  tbr2.cgcil.ip.att.net [12.122.10.106]
13    84 ms    77 ms    76 ms  tbr1.cgcil.ip.att.net [12.122.9.133]
14    77 ms    78 ms    77 ms  tbr1.sffca.ip.att.net [12.122.10.6]
15    78 ms    77 ms    86 ms  gar4.sffca.ip.att.net [12.123.13.174]
16    80 ms    81 ms    79 ms  idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.218]
17    77 ms    75 ms    75 ms  rwcsbix11-1-4.attbi.com [63.241.85.234]
18    78 ms    76 ms    77 ms  www.comcast.net [216.148.227.202]

Trace complete.

C:\Documents and Settings\Harrison!>

That's what it looks like now, which is normal.

[Arlos]

Well, I'd still recommend getting WinMTR. As you can see, it's a pretty awesome tool. I found it indespensible back when I was working in the industry. (And it gives great data to be able to send to an ISP when they claim it's not an issue at their end. I love being able to show cases where there's no problem for the first 4-5 hops, say, then latency jumps from 30ms to 600. Kinda identifies the problem link....)

-Arlos

[Harrison]

I'm getting it now. I like having nifty little tools like that.

[Tikker]

it could have been something as simple as a new link/peer was added, and stuff was reconverging

[Harrison]

The thing is, they NEVER admit to anything and always tell you a day later "Oh, yeah, we do suck...it was our fault lolz"

It's been like this ever since they monopolized the area. Thankfully Verizon Fios is moving in, I've heard GREAT things about that. I've used Verizon DSL in the past and I think I'm going to get it for my little pad upstairs. Let the rest of the house keep their shit-service. Thank God this upstairs is registered as a separate home.

When I lived one block over, the DSL service and quality was superb...great for gaming.

[Tossica]

Welcome to the internet.


Try dealing with Qwest and getting them to admit fault in unstable point to point T1's. We literally have to replace every piece of gear and cable after the DMARC on BOTH ends before they will accept any responsibility for the issues. Then magically, it all starts working over night and the customer is stuck with a $2500 bill from us for all the time we had to put in to troubleshooting a fucking QWEST issue! FUCKERS!

[Ouchyfish]

I used to have a program that did something similar but it also offered a graphical map of the planet (you could zoom in to states, etc) so you could see where the hops were, etc. I think it was called neotrace

[Gidan]

You could also use pathping. Its built into windows and does roughly the same thing. It traces the path then does something like 100ping to each node on the path.

[Harrison]

Up and down for 3-4 fucking days, I am going to kill someone.

Phone goes out when this goes out too. So, it's definitely their fucking problem. Phone is through Comsuck too.

[Ouchyfish]

lol

[Gidan]

Looks like the internet is broken today, and a bit yesterday. http://www.internethealthreport.com/ good info if you want to see whats going on with the backbones. Verizon is looking like shit atm, globalcrossing was shit the last couple days which happens to be what most of comcast runs on.

[Harrison]

It was down most of today as well...

Having the phone down too is the worst part. I can't call their tech support and unleash furies the likes of which are only read about in biblical texts.

[Harrison]

It's still acting up...and the phone is out again.

[Tikker]

that's what happens when you use a cable co for internet/telephone instead of a real company

[Harrison]

I warned the entire family when they decided to use comcrap for their entire package, because I did it at my old apartment and it was horrid.

No one listens to me and wonders why bad shit happens. I'll have my old DSL service soon enough. Mmmmm dedicated line...

[Ouchyfish]

lol that's what I use. DSL for my Vonage line. Sounds nuts, I know, but it works and cheaply too I might add.