[outages] Level 3 -> XO

Wed Sep 26 12:34:51 EDT 2012

Sites are starting to respond now.

 From ATL to xo.com

  5  vlan52.ebr2.atlanta2.level3.net (4.69.150.126)  20.147 ms  11.744 
ms  20.110 ms
  6  ae-2-2.ebr2.miami1.level3.net (4.69.140.141)  31.091 ms  30.005 ms  
22.271 ms
  7  ae-2-52.edge1.miami2.level3.net (4.69.138.107)  21.719 ms  21.678 
ms  21.691 ms
  8  xo-communic.edge1.miami2.level3.net (4.59.80.42) 21.693 ms  21.687 
ms  21.683 ms
  9  vb2001.rar3.dallas-tx.us.xo.net (207.88.13.174)  42.574 ms  42.580 
ms  42.562 ms
10  ae0d0.mcr1.dallas-tx.us.xo.net (216.156.0.82)  92.925 ms  92.904 ms  
92.907 ms
11  216.55.13.100 (216.55.13.100)  40.185 ms  42.484 ms 42.435 ms
12  txplan01-fw01a-eth1.dc.xo.com (205.158.160.201)  41.171 ms  41.126 
ms  41.103 ms
13  xonlbvip.pla.dc.xo.com (205.158.160.76)  41.108 ms 41.094 ms  41.045 ms

--John
On 09/26/2012 11:25 AM, Reed Glauser wrote:
> Yes, we are a customer of XO and there is intermittent connectivity. 
>  Possibly a peering issue similar to one that they had back at the 
> first of the year. Notified XO at 955 am MST and there were barely 
> aware of the issue.
>
> */
> /*
>
> */
> /*
>
> */ Reed Glauser/*
>
> http://www.bidsync.com/images/marketing/dark-blue-hr.gif
>   Systems Engineer
>
> 	
>
> *PH.* 801.765.9245 x477
> *FAX.* 801.765.9246
> *@.* rglauser at bidsync.com <mailto:rglauser at bidsync.com>
>
>
> Leave previous communications attached on all replies.
> This electronic message is confidential and is intended only for the 
> use of the individual to whom it is addressed. If you are not the 
> intended recipient, please immediately notify me by replying to this 
> e-mail and delete the message from your system. Thank you.
>
>
> From: Jayson Navitsky <jnavitsky at gmail.com <mailto:jnavitsky at gmail.com>>
> Date: Wednesday, September 26, 2012 10:12 AM
> To: "outages at outages.org <mailto:outages at outages.org>" 
> <outages at outages.org <mailto:outages at outages.org>>
> Subject: [outages] Level 3 -> XO
>
> We're showing intermittent (well -- now no) connectivity to XO from 
> Level 3 in NYC (and from the looks of the L3 looking glass other areas 
> of the US.) Anyone else seeing this?
>
> NYC to XO Web:
> traceroute to www.xo.com <http://www.xo.com> (205.158.160.76), 30 hops 
> max, 60 byte packets
>  4 ge-9-23.car1.newyork1.level3.net 
> <http://ge-9-23.car1.newyork1.level3.net> (4.26.32.89)  4.240 ms  
> 4.210 ms  4.177 ms
>  5 ae-2-70.edge2.newyork1.level3.net 
> <http://ae-2-70.edge2.newyork1.level3.net> (4.69.155.80)  2.200 ms  
> 2.155 ms  1.895 ms
>  6 206.111.13.65.ptr.us.xo.net <http://206.111.13.65.ptr.us.xo.net> 
> (206.111.13.65)  1.963 ms  1.667 ms  1.624 ms
>  7  * * *
>  8  * * *
>
> NYC to XO (NYC):
> traceroute to 207.86.XXX.x (207.86.XXX.x), 30 hops max, 60 byte packets
>  4 ge-9-23.car1.newyork1.level3.net 
> <http://ge-9-23.car1.newyork1.level3.net> (4.26.32.89)  2.702 ms  
> 2.678 ms  2.667 ms
>  5 ae-4-90.edge2.newyork1.level3.net 
> <http://ae-4-90.edge2.newyork1.level3.net> (4.69.155.208)  1.607 ms  
> 1.558 ms  1.538 ms
>  6 206.111.13.65.ptr.us.xo.net <http://206.111.13.65.ptr.us.xo.net> 
> (206.111.13.65)  1.644 ms  1.575 ms  1.549 ms
>  7  * * *
>  8  * * *
>
> *Show Level 3 (Dallas, TX) Traceroute to 205.158.160.76*
>    1ae-1-60.edge2.Dallas3.Level3.net  <http://ae-1-60.edge2.Dallas3.Level3.net>  (4.69.145.12) 0 msec
>      ae-2-70.edge2.Dallas3.Level3.net  <http://ae-2-70.edge2.Dallas3.Level3.net>  (4.69.145.76) 0 msec
>      ae-4-90.edge2.Dallas3.Level3.net  <http://ae-4-90.edge2.Dallas3.Level3.net>  (4.69.145.204) 4 msec
>    2XO-Level3.edge2.Dallas3.Level3.net  <http://XO-Level3.edge2.Dallas3.Level3.net>  (4.68.127.150) 0 msec 0 msec 12 msec
>    3  *  *  *
>    4  *  *  *
>
> -J
>
>
>
>
> _______________________________________________
> 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/20120926/2457c823/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 137 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/outages/attachments/20120926/2457c823/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7101 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/outages/attachments/20120926/2457c823/attachment-0001.png>