[outages] Trans-Atlantic connectivity outages?

Nuno Vieira - nfsi telecom nuno.vieira at nfsi.pt
Fri Feb 19 09:45:16 EST 2010


Hi, 

>From Portugal, i don't see that behaviour. 

Probably is problem that is only affecting a few carriers/isps. 

>From Portugal > USA all good 

traceroute to www.nyiix.net (209.137.140.21), 30 hops max, 40 byte packets 
1 xe13-10GE.xmr1.as25137.net (81.92.200.254) 0.587 ms 0.670 ms 0.707 ms 
2 if-5-1-2.core1.PV9-Lisbon.as6453.net (195.219.186.9) 0.149 ms 0.145 ms if-5-1-1.core1.PV9-Lisbon.as6453.net (195.219.187.49) 0.138 ms 
3 if-14-0-0.mcore3.NJY-Newark.as6453.net (209.58.124.9) 90.439 ms 90.529 ms 90.524 ms 
4 if-4-0.core1.NYT-NewYork.as6453.net (216.6.57.26) 91.009 ms 91.148 ms 91.338 ms 
5 Vlan3.msfc1.NYT-NewYork.as6453.net (64.86.113.9) 90.821 ms 90.911 ms 90.957 ms 
6 Vlan151.msfc1.NYT-NewYork.as6453.net (64.86.113.18) 91.299 ms 91.253 ms 91.237 ms 
7 ert10-04-gi5-1.kdd.net (209.137.129.42) 91.220 ms 91.075 ms 90.905 ms 
8 209.137.137.130 (209.137.137.130) 91.541 ms 93.110 ms 93.300 ms 
9 ns3.nyiix.net (209.137.140.21) 91.592 ms 91.589 ms 91.582 ms 

traceroute to us1.nfsi.pt (209.239.114.141), 30 hops max, 40 byte packets 
1 xe13-10GE.xmr1.as25137.net (81.92.200.254) 0.202 ms 0.288 ms 0.376 ms 
2 mad-b1-link.telia.net (213.248.99.9) 20.328 ms 20.325 ms 20.318 ms 
3 prs-bb1-link.telia.net (80.91.248.128) 48.797 ms 48.791 ms 48.784 ms 
4 ash-bb1-link.telia.net (80.91.252.36) 126.969 ms 126.957 ms 126.999 ms 
5 level3-113898-ash-bb1.telia.net (213.248.88.86) 126.983 ms 126.979 ms 127.017 ms 
6 vlan69.csw1.Washington1.Level3.net (4.68.17.62) 131.694 ms vlan99.csw4.Washington1.Level3.net (4.68.17.254) 131.747 ms vlan69.csw1.Washington1.Level3.net (4.68.17.62) 131.346 ms 
7 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 124.595 ms 123.890 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 129.071 ms 
8 ae-2-2.ebr2.Chicago2.Level3.net (4.69.132.69) 144.928 ms 144.752 ms 144.739 ms 
9 ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193) 146.378 ms 143.611 ms 148.210 ms 
10 ae-4-4.car2.StLouis1.Level3.net (4.69.132.189) 148.101 ms 148.050 ms 147.788 ms 
11 MESH-SOLUTI.car2.StLouis1.Level3.net (4.53.162.78) 234.974 ms 234.967 ms 234.950 ms 
12 static-ip-69-64-45-140.inaddr.intergenia.de (69.64.45.140) 152.641 ms 152.637 ms 152.631 ms 
13 usloft1147.serverloft.eu (209.239.114.141) 157.553 ms 156.899 ms 156.576 ms 

>From Portugal > India all good aswell. 

traceroute to www.tatacommunications.com (121.243.66.50), 30 hops max, 40 byte packets 
1 xe13-10GE.xmr1.as25137.net (81.92.200.254) 0.225 ms 0.303 ms 0.340 ms 
2 if-5-1-1.core1.PV9-Lisbon.as6453.net (195.219.187.49) 0.182 ms if-5-1-2.core1.PV9-Lisbon.as6453.net (195.219.186.9) 0.178 ms if-5-1-1.core1.PV9-Lisbon.as6453.net (195.219.187.49) 0.171 ms 
3 if-1-0-0-469.core4.LDN-London.as6453.net (80.231.76.9) 38.134 ms 38.126 ms 38.119 ms 
4 Vlan1707.icore1.LDN-London.as6453.net (195.219.83.45) 34.810 ms 34.805 ms 34.843 ms 
5 ix-13-4.icore1.LDN-London.as6453.net (195.219.48.162) 33.376 ms 33.372 ms ix-13-43.icore1.LDN-London.as6453.net (195.219.48.178) 27.370 ms 
6 59.163.55.149.static.vsnl.net.in (59.163.55.149) 159.716 ms 159.659 ms * 
7 203.197.33.200.static.vsnl.net.in (203.197.33.200) 159.738 ms 159.732 ms 159.934 ms 
8 * * * 
9 121.243.64.138 (121.243.64.138) 160.621 ms 161.432 ms 161.671 ms 
10 * * * 
11 * * * 
12 * * * 

cheers, 
--nvieira 


----- "Carl Perry" <caperry at edolnx.net> wrote: 
> It doesn't look isolated to India any more either. Our internal links between our US Data Centers and out London Data Centers are showing a 120ms increase in latency as well. Mind you, the latency to India is as high as 300ms so I'm wondering if there are two outages... 
> 
> On 2/19/10 8:27 AM, Bradley Bopp wrote: 
> > Re: [outages] Trans-Atlantic connectivity outages? Hello Carl, 
> > 
> > I take a slightly different path than you but we have had tickets 
> > since yesterday regarding this. We have a major customer with 
> > operations in India that have been unable to RDP or VPN to there 
> > systems here for about 24 hours. 
> > 
> > This is were it seems to break; 
> > 
> > 13. xe-11-2-0-xcr1.fra.cw.net 0.0% 10 116.6 127.2 116.6 
> > 174.4 18.3 
> > 14. ge-2-0-0-dcr2.fra.cw.net 0.0% 10 115.9 151.2 115.9 
> > 314.2 63.7 
> > 15. bharti-gw2.fra.cw.net 10.0% 10 292.3 291.6 287.8 
> > 301.8 4.5 
> > 16. 59.145.7.134 10.0% 10 289.0 293.7 289.0 
> > 303.8 4.5 
> > 17. 61.95.240.130 10.0% 10 288.0 294.5 288.0 
> > 298.2 3.3 
> > 18. ABTS-TN-Static-248.253.246.6 10.0% 10 306.9 295.8 290.8 
> > 306.9 4.7 
> > M 
> > 
> > I am not sure who the Fiber Carrier is out to this point I checked 
> > with HA and it’s not there fiber. I doubt CW built this leg. 
> > 
> > If we can determine the carrier perhaps we can find out if there is 
> > a Trans-Atlantic issue. 
> > 
> > 
> > 
> > 
> > On 2/19/10 9:04 AM, "Carl Perry" <caperry at edolnx.net> wrote: 
> > 
> 

We've been seeing a lot of customers call in with reports of 
> slow access 
> to their servers in the US. Traceroutes back to them all yield 
> round-trip times of 300ms once the connection gets across the ocean. 
> Anyone have any leads on a root cause? 
> 
> 4. 
> 12.87.122.245 
> 
> 
> 0% 9 9 9 9 10 11 
> 5. 
> cr2.hs1tx.ip.att.net 
> 
> 
> 0% 9 9 46 46 46 46 
> 6. 
> cr1.dlstx.ip.att.net 
> 
> 
> 0% 9 9 47 46 47 47 
> 7. 
> cr2.dlstx.ip.att.net 
> 
> 
> 0% 9 9 47 46 47 47 
> 8. 
> cr2.la2ca.ip.att.net 
> 
> 
> 0% 9 9 46 45 46 46 
> 9. 
> gar4.lsrca.ip.att.net 
> 
> 
> 0% 9 9 47 47 47 48 
> 10. 
> 12.86.240.10 
> 
> 
> 0% 9 9 46 45 46 49 
> 11. 
> segment-124-7.sify.net 
> 
> 
> 0% 8 9 269 268 269 269 
> 12. 
> segment-119-227.sify.net 
> 
> 
> 0% 8 9 268 267 268 271 
> 13. 
> segment-119-227.sify.net 
> 
> 
> 0% 8 8 269 267 268 271 
> 14. 
> segment-119-227.sify.net 
> 
> 
> 0% 8 8 270 269 271 274 
> 15. 
> segment-119-227.sify.net 
> 
> 
> 0% 8 8 270 268 270 276 
> 16. 
> segment-119-227.sify.net 
> 
> 
> 0% 8 8 271 269 270 271 
> 17. 
> 210.18.13.233.sify.net 
> 
> 
> 0% 8 8 268 268 268 269 
> 18. 
> segment-124-30.sify.net 
> 
> 
> 0% 8 8 294 284 292 299 
> 
> 
> 4. 
> 12.87.122.245 
> 
> 
> 0% 11 11 10 9 10 11 
> 5. 
> cr2.hs1tx.ip.att.net 
> 
> 
> 0% 11 11 16 16 16 17 
> 6. 
> cr1.dlstx.ip.att.net 
> 
> 
> 0% 11 11 16 16 16 17 
> 7. 
> ggr7.dlstx.ip.att.net 
> 
> 
> 0% 11 11 170 15 56 170 
> 8. 
> 192.205.36.42 
> 
> 
> 0% 11 11 15 15 22 75 
> 9. 
> customer-side-bharti-4-pal6.pal.seabone.net 
> 
> 
> 0% 10 11 286 286 287 287 
> 10. 
> 125.21.167.114 
> 
> 
> 0% 10 10 285 285 285 285 
> 11. 
> 61.95.240.130 
> 
> 
> 0% 10 10 283 283 283 286 
> 12. 
> abts-tn-static-248.253.246.61.airtelbroadband.in 
> 
> 
> 0% 10 10 290 287 290 294 
> 
> 
> 
> ---------------------------------------------------------------------- 
> _______________________________________________ 
> outages mailing list 
> outages at outages.org 
> https://puck.nether.net/mailman/listinfo/outages 
> 
> 
> 
> > Bradley D. Bopp 
> > Director Of Engineering 
> > http://www.nationalnet.com 
> > http://as22384.peeringdb.net 
> 
> > NationalNet is committed to the highest level of Customer Service 
> > available in the Web Hosting business. If you have any questions, 
> > comments or concerns feel free to contact us at 678-247-7000 ext 1 
> > (or toll-free, 888-4-NATNET). 
> 
> 
> 
> 
> _______________________________________________ 
> outages mailing list 
> outages at outages.org 
> https://puck.nether.net/mailman/listinfo/outages 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20100219/79e74ab3/attachment.htm>


More information about the Outages mailing list