[outages] Anyone aware of L3 issues in the NY area?

[Andy Ashley]

On 01/11/2012 21:10, Jon Radel wrote:
> While there's a LOT more than that that's hosed, including a bunch of 
> our VZ circuits and Internap services, which come and go, I'm not  
> having problems specifically with L3 circuits or their SIP services.  
> As others have reported L3 issues, that's probably just dumb luck on 
> the routing of our circuits.   We've got equipment and circuits 
> terminated at 325 Hudson.
>
We are also waiting with baited breath for news about the fate of Level 
3 at 111 8th (our equipment is in Room 304)
So far so good.

Only issue noticed was an increase from usual 70ms trans-Atlantic rtd to 
~100ms around the 30th Oct, but now back to normal.
Level 3 NOC is telling us that all systems are running normally on 
generators as per the emergency preparedness plan and they continue to 
see no risk to our New York colocation or connectivity..
No info about runtimes or fuel deliveries, etc from them unfortunately.

Thu Nov  1 21:59:34 (GMT) 2012
Packets               Pings
  Host Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. hsrp-v36-csw01.ln1.qubenet.net 0.0%    34    0.6     6.7   0.5 
197.5  33.8
  2. gi-0-1-8.bdr01.ln1.qubenet.net 0.0%    34    0.9     1.7   0.6  
15.1   2.8
  3. hsa2.london2.level3.net 0.0%    34    0.6     4.2   0.6  69.7  13.1
  4. ae-3-3.ebr1.london1.level3.net 0.0%    34    0.9     0.9   0.7   
3.3   0.4
  5. vlan104.ebr2.london1.level3.net 0.0%    34    0.9     0.8   0.6   
2.7   0.4
  6. ae-44-44.ebr1.newyork1.level3.net 0.0%    34   69.5    69.6  69.5  
70.1   0.1
  7. ae-91-91.csw4.newyork1.level3.net 0.0%    34   77.1    72.0  69.3  
80.1   3.5
  8. ae-41-90.car1.newyork1.level3.net 0.0%    33   69.7    83.4  69.4 
190.4  34.1
  9. gi-0-3.bdr01.ny1.qubenet.net 0.0%    33   69.5    69.6  69.4  
70.3   0.1
10. ns0.ny1.qubenet.net 0.0%    33   70.0    70.1  69.7  73.7   0.8

Regards,
Andy Ashley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20121101/24148db2/attachment.htm>