Looks to me like this might be an issue with Level(3)/ATT peering in Chicago. I do have one customer complaint of intermittent connectivity which might be related to this issue, but I don't have an IP from them to test yet. -Bill ---- snip 8< ---- Troy-L3-Edge>traceroute 12.174.136.25 Type escape sequence to abort. Tracing the route to 12.174.136.25 1 ge-6-16.car2.Detroit1.Level3.net (4.53.74.173) [AS 3356] 4 msec 0 msec 4 msec 2 ae-11-11.car1.Detroit1.Level3.net (4.69.133.245) [AS 3356] 24 msec 48 msec 104 msec 3 ae-8-8.ebr2.Chicago1.Level3.net (4.69.133.242) [AS 3356] 8 msec 8 msec 8 msec 4 ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194) [AS 3356] 16 msec 8 msec 8 msec 5 4.69.158.157 [AS 3356] 8 msec 4.69.158.145 [AS 3356] 8 msec 4.69.158.149 [AS 3356] 8 msec 6 192.205.37.149 [AS 7018] 12 msec 8 msec 12 msec 7 cr1.cgcil.ip.att.net (12.122.133.34) [AS 7018] 16 msec * 200 msec 8 cr81.dtrmi.ip.att.net (12.123.139.158) [AS 7018] 200 msec 200 msec 200 msec 9 12.122.102.33 [AS 7018] 200 msec 196 msec 200 msec 10 * * * 11 * * * 12 * * * 13 Troy-L3-Edge> Troy-L3-Edge> Troy-L3-Edge>traceroute 12.174.136.25 Type escape sequence to abort. Tracing the route to 12.174.136.25 1 ge-6-16.car2.Detroit1.Level3.net (4.53.74.173) [AS 3356] 0 msec 4 msec 0 msec 2 ae-11-11.car1.Detroit1.Level3.net (4.69.133.245) [AS 3356] 8 msec 8 msec 8 msec 3 ae-8-8.ebr2.Chicago1.Level3.net (4.69.133.242) [AS 3356] 8 msec 8 msec 8 msec 4 ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194) [AS 3356] 8 msec 8 msec 8 msec 5 4.69.158.149 [AS 3356] 8 msec 4.69.158.145 [AS 3356] 8 msec 4.69.158.153 [AS 3356] 8 msec 6 192.205.37.149 [AS 7018] 12 msec 12 msec 8 msec 7 cr1.cgcil.ip.att.net (12.122.133.34) [AS 7018] 16 msec * 16 msec 8 cr81.dtrmi.ip.att.net (12.123.139.158) [AS 7018] 16 msec 20 msec 20 msec 9 12.122.102.33 [AS 7018] 16 msec 16 msec 16 msec 10 * * * 11 * * * 12 Troy-L3-Edge> ---- snip 8< ---- From: steve.starr@corp.daystarr.net [mailto:steve.starr@corp.daystarr.net] On Behalf Of Starr, Steve Sent: Tuesday, November 05, 2013 9:52 AM To: Bill Wichers Cc: Collin Rose; outages@outages.org Subject: Re: [outages] Level 3 <-> ATT Bill, We are seeing loss to 12.174.136.25 in particular. If you can trace route that please. :: Steve Starr :: Daystarr Communications :: starrs@daystarr.net<mailto:starrs@daystarr.net> :: v - 989.720.6000 :: f - 989.720.6060 On Tue, Nov 5, 2013 at 9:54 AM, Bill Wichers <billw@waveform.net<mailto:billw@waveform.net>> wrote: We connect into Level(3) in detroit too. Want me to run any traceroutes from my side to help you isolate anything? We haven't received any complaints, but we have two other carriers so we might just not be seeing the problem. -Bill
-----Original Message----- From: Outages [mailto:outages-bounces@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Collin Rose Sent: Tuesday, November 05, 2013 9:47 AM To: outages@outages.org<mailto:outages@outages.org> Subject: [outages] Level 3 <-> ATT
Anyone aware of issues between AT&T and Level3 ? We are connecting to Level 3 in Detroit. http://www.internetpulse.net confirms issues.
Collin Rose DayStarr Communications P: (989) 720-1000<tel:%28989%29%20720-1000> F: (989) 720-6060<tel:%28989%29%20720-6060> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages