<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
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...<br>
<br>
On 2/19/10 8:27 AM, Bradley Bopp wrote:<br>
<span style="white-space: pre;">> Re: [outages] Trans-Atlantic
connectivity outages? Hello Carl,<br>
><br>
> I take a slightly different path than you but we have had tickets<br>
> since yesterday regarding this.  We have a major customer with<br>
> operations in India that have been unable to RDP or VPN to there<br>
> systems here for about 24 hours.<br>
><br>
> This is were it seems to break;<br>
><br>
>  13. xe-11-2-0-xcr1.fra.cw.net     0.0%    10  116.6 127.2 116.6<br>
> 174.4  18.3<br>
>  14. ge-2-0-0-dcr2.fra.cw.net      0.0%    10  115.9 151.2 115.9<br>
> 314.2  63.7<br>
>  15. bharti-gw2.fra.cw.net        10.0%    10  292.3 291.6 287.8<br>
> 301.8   4.5<br>
>  16. 59.145.7.134                 10.0%    10  289.0 293.7 289.0<br>
> 303.8   4.5<br>
>  17. 61.95.240.130                10.0%    10  288.0 294.5 288.0<br>
> 298.2   3.3<br>
>  18. ABTS-TN-Static-248.253.246.6 10.0%    10  306.9 295.8 290.8<br>
> 306.9   4.7<br>
> M<br>
><br>
> I am not sure who the Fiber Carrier is out to this point I
checked<br>
> with HA and it’s not there fiber.  I doubt CW built this leg.<br>
><br>
> If we can determine the carrier perhaps we can find out if there
is<br>
> a Trans-Atlantic issue.<br>
><br>
><br>
><br>
><br>
> On 2/19/10 9:04 AM, "Carl Perry" <a class="moz-txt-link-rfc2396E" href="mailto:caperry@edolnx.net"><caperry@edolnx.net></a>
wrote:<br>
></span><br>
<blockquote type="cite">We've been seeing a lot of customers call in
with reports of<br>
slow access<br>
to their servers in the US.  Traceroutes back to them all yield<br>
round-trip times of 300ms once the connection gets across the ocean.<br>
Anyone have any leads on a root cause?<br>
  <br>
 4.<br>
12.87.122.245                                                                    
 <br>
 <br>
 <br>
0%    9    9     9    9   10     11<br>
 5.<br>
cr2.hs1tx.ip.att.net                                                             
 <br>
 <br>
 <br>
0%    9    9    46   46   46     46<br>
 6.<br>
cr1.dlstx.ip.att.net                                                             
 <br>
 <br>
 <br>
0%    9    9    47   46   47     47<br>
 7.<br>
cr2.dlstx.ip.att.net                                                             
 <br>
 <br>
 <br>
0%    9    9    47   46   47     47<br>
 8.<br>
cr2.la2ca.ip.att.net                                                             
 <br>
 <br>
 <br>
0%    9    9    46   45   46     46<br>
 9.<br>
gar4.lsrca.ip.att.net                                                            
 <br>
 <br>
 <br>
0%    9    9    47   47   47     48<br>
10.<br>
12.86.240.10                                                                     
 <br>
 <br>
 <br>
0%    9    9    46   45   46     49<br>
11.<br>
segment-124-7.sify.net                                                           
 <br>
 <br>
 <br>
0%    8    9   269  268  269    269<br>
12.<br>
segment-119-227.sify.net                                                         
 <br>
 <br>
 <br>
0%    8    9   268  267  268    271<br>
13.<br>
segment-119-227.sify.net                                                         
 <br>
 <br>
 <br>
0%    8    8   269  267  268    271<br>
14.<br>
segment-119-227.sify.net                                                         
 <br>
 <br>
 <br>
0%    8    8   270  269  271    274<br>
15.<br>
segment-119-227.sify.net                                                         
 <br>
 <br>
 <br>
0%    8    8   270  268  270    276<br>
16.<br>
segment-119-227.sify.net                                                         
 <br>
 <br>
 <br>
0%    8    8   271  269  270    271<br>
17.<br>
210.18.13.233.sify.net                                                           
 <br>
 <br>
 <br>
0%    8    8   268  268  268    269<br>
18.<br>
segment-124-30.sify.net                                                          
 <br>
 <br>
 <br>
0%    8    8   294  284  292    299<br>
  <br>
  <br>
 4.<br>
12.87.122.245                                                                    
 <br>
 <br>
 <br>
0%   11   11    10    9   10     11<br>
 5.<br>
cr2.hs1tx.ip.att.net                                                             
 <br>
 <br>
 <br>
0%   11   11    16   16   16     17<br>
 6.<br>
cr1.dlstx.ip.att.net                                                             
 <br>
 <br>
 <br>
0%   11   11    16   16   16     17<br>
 7.<br>
ggr7.dlstx.ip.att.net                                                            
 <br>
 <br>
 <br>
0%   11   11   170   15   56    170<br>
 8.<br>
192.205.36.42                                                                    
 <br>
 <br>
 <br>
0%   11   11    15   15   22     75<br>
 9.<br>
customer-side-bharti-4-pal6.pal.seabone.net                                      
 <br>
 <br>
 <br>
0%   10   11   286  286  287    287<br>
10.<br>
125.21.167.114                                                                   
 <br>
 <br>
 <br>
0%   10   10   285  285  285    285<br>
11.<br>
61.95.240.130                                                                    
 <br>
 <br>
 <br>
0%   10   10   283  283  283    286<br>
12.<br>
abts-tn-static-248.253.246.61.airtelbroadband.in                                 
 <br>
 <br>
 <br>
0%   10   10   290  287  290    294<br>
  <br>
  <br>
</blockquote>
    <br>
----------------------------------------------------------------------<br>
_______________________________________________<br>
outages mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:outages@outages.org">outages@outages.org</a><br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
<br>
<br>
<span style="white-space: pre;">> Bradley D. Bopp<br>
> Director Of  Engineering<br>
> <a class="moz-txt-link-freetext" href="http://www.nationalnet.com">http://www.nationalnet.com</a><br>
> <a class="moz-txt-link-freetext" href="http://as22384.peeringdb.net">http://as22384.peeringdb.net</a><br>
<br>
> NationalNet is committed to the highest level of Customer Service<br>
> available in the Web Hosting business.  If you have any
questions,<br>
> comments or concerns feel free to contact us at 678-247-7000 ext
1<br>
> (or toll-free, 888-4-NATNET).</span><br>
<br>
<br>
<br>
</body>
</html>