Is It Level3 Or Is It Me?

**SkrU** · 06-15-2008, 11:02 AM

Kinda strange latency issues. I'm thinking about calling Comcast and asking them what is up. This is an intermittent problem, comes and goes.

To 208.100.48.172:

Tracing route to ip172.208-100-48.static.steadfast.net [208.100.48.172]
over a maximum of 30 hops:

1 * * * Request timed out.
2 9 ms 9 ms 9 ms ge-3-15-ur02.royaloak.mi.michigan.comcast.net [6
8.85.235.169]
3 10 ms 23 ms 9 ms te-9-1-ur03.sterlinghub.mi.michigan.comcast.net
[68.87.191.5]
4 10 ms 9 ms 9 ms te-9-4-ur02.sterlinghub.mi.michigan.comcast.net
[68.87.191.1]
5 13 ms 14 ms 12 ms te-0-6-0-0-ar01.taylor.mi.michigan.comcast.net [
68.86.90.106]
6 * 16 ms 18 ms pos-0-6-0-0-cr01.cleveland.oh.ibone.comcast.net
[68.86.85.53]
7 25 ms 23 ms 23 ms pos-0-10-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.54]
8 24 ms 24 ms 23 ms xe-10-3-0.edge1.Chicago2.Level3.net [4.71.248.9]

9 24 ms 23 ms 23 ms ae-24-56.car4.Chicago1.Level3.net [4.68.101.168]

10 60 ms 62 ms 54 ms WBS-CONNECT.car4.Chicago1.Level3.net [4.79.208.1
54]
11 112 ms 38 ms 204 ms ip61.216-86-149.static.steadfast.net [216.86.149
.61]
12 52 ms 52 ms 64 ms ip172.208-100-48.static.steadfast.net [208.100.4
8.172]
Trace complete.

From 208.100.48.172

skr01:~# traceroute 68.87.191.5
traceroute to 68.87.191.5 (68.87.191.5), 30 hops max, 40 byte packets
1 ip189.67-202-68.static.steadfast.net (67.202.68.189) 5.364 ms 0.947 ms 0.975 ms
2 ip60.216-86-149.static.steadfast.net (216.86.149.60) 0.961 ms 0.967 ms 0.977 ms
3 ber2-ge-4-7.chicagoequinix.savvis.net (208.173.176.217) 0.962 ms 0.970 ms 0.972 ms
4 cr2-tengig-0-0-5-0.chicago.savvis.net (204.70.195.117) 3.957 ms 3.962 ms 2.976 ms
5 cr2-pos-0-0-5-0.NewYork.savvis.net (204.70.192.110) 25.941 ms 25.945 ms 25.957 ms
6 dcr4-so-3-2-0.newyork.savvis.net (204.70.195.98) 25.939 ms 25.946 ms 24.958 ms
7 204.70.144.2 (204.70.144.2) 24.933 ms 23.950 ms 24.956 ms
8 pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net (68.86.85.106) 31.936 ms 31.941 ms 31.950 ms
9 te-0-6-0-1-ar01.taylor.mi.michigan.comcast.net (68.86.90.110) 35.931 ms 35.938 ms 35.947 ms
10 te-0-6-0-2-ar01.taylor.mi.michigan.comcast.net (68.85.235.254) 43.924 ms 43.932 ms 43.942 ms
11 te-9-1-ur02.sterlinghub.mi.michigan.comcast.net (68.85.235.253) 45.921 ms 45.930 ms 45.939 ms
12 te-9-4-ur03.sterlinghub.mi.michigan.comcast.net (68.87.191.2) 45.921 ms * 45.310 ms

As you can see, hop 10 going to the server is fubarred. The return traceroute looks okay, but confused about the New York bit. Those usually correct themselves eventually.

Any clues or anyone heard anything regarding level3 having problems?

Thanks in advance!

**SkrU** · 06-15-2008, 05:10 PM

I seem to be getting a loopback on the return via savvis. Any input before I call Comcast is appreciated.

traceroute to 68.87.191.5 (68.87.191.5), 30 hops max, 40 byte packets
1 ip189.67-202-68.static.steadfast.net (67.202.68.189) 0.885 ms 0.945 ms 0.974 ms
2 ip60.216-86-149.static.steadfast.net (216.86.149.60) 77.899 ms 0.952 ms 0.976 ms
3 ber2-ge-4-7.chicagoequinix.savvis.net (208.173.176.217) 0.958 ms 0.966 ms 0.978 ms
4 * cr2-tengig-0-0-5-0.chicago.savvis.net (204.70.195.117) 1279.207 ms *
5 * * *
6 dcr4-so-3-2-0.newyork.savvis.net (204.70.195.98) 25.392 ms 25.926 ms 25.948 ms
7 204.70.144.2 (204.70.144.2) 24.923 ms 25.938 ms 23.950 ms
8 pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net (68.86.85.106) 31.924 ms 30.933 ms 31.947 ms
9 te-0-6-0-1-ar01.taylor.mi.michigan.comcast.net (68.86.90.110) 35.923 ms 35.933 ms 35.939 ms
10 te-0-6-0-2-ar01.taylor.mi.michigan.comcast.net (68.85.235.254) 43.915 ms 42.925 ms 42.936 ms
11 te-9-1-ur02.sterlinghub.mi.michigan.comcast.net (68.85.235.253) 45.916 ms 44.924 ms 44.936 ms
12 te-9-4-ur03.sterlinghub.mi.michigan.comcast.net (68.87.191.2) 45.911 ms * 45.916 ms

**Jon124** · 06-16-2008, 10:32 AM

I have heard from numerous other people that l3 is causing them a bunch of the same issues.

**SkrU** · 06-16-2008, 10:39 AM

I wonder if thats why savvis is sending me to the twilight zone and back.

**Karl** · 06-16-2008, 11:44 AM

Comcast just seems to continually have issues with their BGP configuration, etc. We currently have a contract in place for direct peering with Comcast though and hope to have that up in July or August.

There has also been an issue recently where both Global Crossing and Level(3) peering with Comcast in Chicago has been congested at times. That congestion causes intermittent packet loss and is then the reason we're using Savvis for those routes instead of any of our other carriers, who go over Level(3) or Global Crossing to reach Comcast. Even though it is resulting in higher latency it should not have any packet loss, unlike the other options.