US Cable Support > Comcast HSI > [Speed] Congested Comcast Peering with Akamai, Google in Midwest

reply to johnnn

Re: [Speed] Congested Comcast Peering with Akamai, Google in Mid

Both visited during the day on weekdays. They didn't perform tests past basic speedtests to the Comcast server near Detroit. The throughput problem is definitely exacerbated during peak times. Recently it was so bad I couldn't stream a 360p YouTube video from beginning to end without pauses (in video info, stream fluctuates between 200-900kbps).

The reason I believe congestion (at some level) to be the issue is this: I could close the page, retry, get the same poor performance, but then run a shaperprobe and get 36mbps down (shaped to 25mbps after Powerboost tokens spent) from whichever servers host the Shaperprobe test files.

NetFixer, I agree with your assessment.

I'm using anycast (75.75.75.75), and my router doesn't support IPv6.

It may be that your local router is being upgraded... in your first post Hop 3 indicated a 'te' interface.

When I just tracerouted to it now, it's showing as a 'xe' interface.

  3    20 ms    10 ms    10 ms  96.120.41.137
  4    12 ms     7 ms     7 ms  xe-8-2-0-sur01.grandrapids.mi.michigan.comcast.net [68.86.140.185]
  5    17 ms    19 ms    27 ms  te-0-2-0-4-ar01.taylor.mi.michigan.comcast.net [69.139.254.29]
  6    18 ms    17 ms    19 ms  xe-7-3-0-sur01.wannarbor.mi.michigan.comcast.net [68.85.218.201]
 

DrDrew is right. When I do tracerts *to* the edge they travel through an xe interface.

reply to johnnn

reply to depster
FWIW, just a point. As Dr.Drew stated, it's the same physical router. This data needs to also be examined when evaluating the rDNS info on hops;

te-8-2-ur02
xe-7-0-sur01

Even though the IP address is the same, the slot, port, and ring data is different.

Some examples of some meanings;

Some examples;

ge = gigabit ethernet.

te / xe= ten gigabit ethernet.

p, po, pos = Packet Over Sonet (an OC-3 or faster connection).

XE / TE = Juniper / Cisco 10GigE Interface
be / ae = Cisco Bundle Ethernet / Juniper Aggregate Ethernet

he = hundred gigabit ethernet.

1-1, 1-2, 1-11, 6-1, 9-1, 2-2, etc. = slot and port.

ar01, cr01, ur01

User Ring (UR), Area Ring (AR), Core Ring (CR) routing.

EG, you're the best.

I doubt that but thanks for your kind words !

reply to JohnInSJ
That is Comcast's anycast DNS

reply to EG

reply to nate1234

reply to EG

reply to whfsdude

reply to JohnInSJ

C:\>dig -x 68.87.68.162
 
; <<>> DiG 9.9.2 <<>> -x 68.87.68.162
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62426
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;162.68.87.68.in-addr.arpa.     IN      PTR
 
;; ANSWER SECTION:
162.68.87.68.in-addr.arpa. 1196 IN      PTR     nrcns.s3woodstock.ga.atlanta.comcast.net.
 
;; Query time: 31 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Jan 27 13:11:54 2013
;; MSG SIZE  rcvd: 108
 
C:\>dig -x 68.87.72.130
 
; <<>> DiG 9.9.2 <<>> -x 68.87.72.130
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26004
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;130.72.87.68.in-addr.arpa.     IN      PTR
 
;; ANSWER SECTION:
130.72.87.68.in-addr.arpa. 6112 IN      PTR     nrcns.area4.il.chicago.comcast.net.
130.72.87.68.in-addr.arpa. 6112 IN      PTR     chic-cns.area4.il.chicago.comcast.net.
 
;; Query time: 15 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Jan 27 13:12:24 2013
;; MSG SIZE  rcvd: 125
 

reply to depster

So based on the info in this thread, the changes in throughput (things are much improved), and the routing changes I've observed, it looks like Comcast hooked my neighborhood's CMTS (and likely all of wannarbor) into a Super UR whereas before it routed through two regular 10GigE URs on its way to the AR in Pontiac.