[outages] Charter Peering issues??(At least ICMP)
*Network
network at cisp.com
Fri Jan 18 07:46:22 EST 2013
We have a customer in Toledo, Oh that is experiencing the same issue going to 75.137.33.22
Tracing route to 75-137-33-22.static.jcsn.tn.charter.com [75.137.33.22]
over a maximum of 30 hops:
1 3 ms 1 ms <1 ms 172.23.0.1
2 1 ms 1 ms 1 ms velocity.org [67.211.164.2]
3 2 ms 2 ms 2 ms 68.70.176.49
4 4 ms 4 ms 4 ms vlan213.car1.detroit1.level3.net [4.53.76.5]
5 10 ms 10 ms 11 ms ae-8-8.ebr2.chicago1.level3.net [4.69.133.242
6 124 ms 26 ms 10 ms ae-23-52.car3.chicago1.level3.net [4.69.138.3
7 10 ms 10 ms 10 ms telia-level3-10.chicago1.level3.net [4.68.63.
8 94 ms 114 ms 27 ms nyk-bb2-link.telia.net [80.91.249.111]
9 34 ms 34 ms 33 ms ash-bb4-link.telia.net [80.91.245.98]
10 33 ms 33 ms 73 ms ash-bb3-link.telia.net [213.155.135.204]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
We contacted our next hop provider and they said that it was an issue with Telia and that they could not open a ticket with them. I went onto a Telia looking glass server in Charlotte, NC and conducted this trace:
traceroute to 75.137.33.22 (75.137.33.22), 30 hops max, 40 byte packets
1 cco-ic-151314-cha-b1.c.telia.net (213.248.84.146) 6.998 ms cco-ic-150436-cha-b1.c.telia.net (80.239.167.210) 7.154 ms cco-ic-151314-cha-b1.c.telia.net (213.248.84.146) 8.809 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
We are going to get with the customer to see if he can get us some trace routes coming from Charter to see what that looks like.
I will keep you posted.
Tim Van Voorhis | Senior Network Engineer | CCNP
[cid:image003.jpg at 01CB2757.45B66350]
419.724.5354 office
419.304.0306 cell
419.724.3547 24x7 support
support at cisp.com<mailto:support at cisp.com> | www.cisp.com<http://www.cisp.com/>
Don't wait for a disaster to happen to try and recover from it, contact us today - http://www.cisp.com
From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On Behalf Of Mitch
Sent: Friday, January 18, 2013 12:21 AM
To: outages at outages.org
Subject: [outages] Charter Peering issues??(At least ICMP)
Anyone else having any issues reaching IP's on Charter communications? We have 3 sites down from our monitoring tool(peered via Level 3) and trace routes from level3's looking glass fail. Their looking glass also shows no routers to the /4 that our IP is part of. I've noticed issues from Centurylink's Looking glass as well on certain POP's and from Cogent as well.
Traceroutes: I had to remove our office IP's for privacy but I think it gets the point across that we can't reach both ways. Oddly enough SSH seems to work sometimes so I wonder if its mostly an ICMP issue with occasional drops of other traffic.
Office is in Ohio, IP/other route is in Tennessee but we also have it down in South and North Carolina.
>From our office to the IP in question:
Tracing route to 75-137-33-21.static.jcsn.tn.charter.com<http://75-137-33-21.static.jcsn.tn.charter.com> [75.137.33.21]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 172.23.0.1
2 34 ms 35 ms 35 ms <Scrubbed>
3 176 ms 203 ms 203 ms <Scrubbed>
4 22 ms 22 ms * vlan213.car1.Detroit1.Level3.net<http://vlan213.car1.Detroit1.Level3.net> [4.53.76.5]
5 35 ms 35 ms 34 ms ae-8-8.ebr2.Chicago1.Level3.net<http://ae-8-8.ebr2.Chicago1.Level3.net> [4.69.133.242]
6 37 ms 37 ms 37 ms ae-23-52.car3.chicago1.level3.net<http://ae-23-52.car3.chicago1.level3.net> [4.69.138.37]
7 79 ms 44 ms 41 ms 4.68.127.138
8 84 ms 71 ms 71 ms nyk-bb1-link.telia.net<http://nyk-bb1-link.telia.net> [213.155.131.240]
9 94 ms 58 ms 58 ms ash-bb3-link.telia.net<http://ash-bb3-link.telia.net> [213.155.134.149]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Traceroutes from our router back to our office:(got into it via DSL link)
1 * * *
2 * * *
3 * * *
4 * * *
Traceroutes from our router to 8.8.8.8<http://8.8.8.8>:
Tracing route to 8.8.8.8 from 75.137.33.22 over a maximum of 30 hops
1 5ms 3ms 5ms 75.137.33.21
2 14ms 9ms 12ms 10.214.212.1
3 8ms 10ms 12ms 96.34.70.4
4 11ms 27ms 11ms 96.34.71.178
5 18ms 26ms 20ms 96.34.79.74
6 18ms 22ms 18ms 96.34.79.62
7 35ms 32ms 31ms 96.34.78.18
8 44ms 35ms 35ms 96.34.2.70
9 33ms 31ms 34ms 96.34.3.17
10 31ms 33ms 33ms 96.34.150.46
11 32ms 31ms 32ms 72.14.239.100
12 33ms 34ms 32ms 66.249.94.24
13 34ms 34ms 49ms 209.85.248.57
14 * * *
15 34ms 32ms 31ms 8.8.8.8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130118/5c2e26a0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 7395 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/outages/attachments/20130118/5c2e26a0/attachment.jpg>
More information about the Outages
mailing list