It looks like something must be going on -- Traffic is shifting pretty good across their backbone: 3. v209.core1.atl1.he.net 0.0% 139 3.8 6.9 3.8 19.5 4.0 4. 216.66.2.82 0.0% 138 3.8 4.4 3.8 25.4 2.4 5. vb2000d1.rar3.atlanta-ga.us.xo.net 0.0% 138 61.1 62.2 60.1 67.1 1.3 6. te-3-0-0.rar3.dallas-tx.us.xo.net 0.0% 138 60.0 58.2 56.1 62.9 1.2 7. vb12.rar3.la-ca.us.xo.net 0.0% 138 60.0 58.7 56.8 65.0 1.4 8. ae0d0.mcr1.la-ca.us.xo.net 0.0% 138 60.0 63.9 59.9 148.5 13.5 9. 216.2.226.58 0.0% 138 159.9 72.4 60.1 240.3 36.5 10. 208.69.81.158 0.0% 138 60.1 60.2 60.0 66.6 0.7 On Sun, Jul 26, 2015 at 12:49 AM, Aubrey Wells <awells@digiumcloud.com> wrote:
I got some notifications from pingdom monitored sites on xo circuits in Atlanta. I see bgp sessions down but phy showing up/up. On Jul 26, 2015 1:48 AM, "N M via Outages" <outages@outages.org> wrote:
Is there anyone currently experiencing latency to XO communications? I have been getting alarms since 11:45p CDT for traffic heading towards XOs network -- Can anyone else confirm ?
3. v209.core1.atl1.he.net 0.0% 280 5.5 6.5 3.7 19.5 3.7 4. 10ge16-5.core1.ash1.he.net 0.0% 280 16.2 19.7 16.2 31.9 4.2 5. 206.111.7.93.ptr.us.xo.net 0.0% 280 16.3 16.8 16.2 45.6 3.5 6. 207.88.14.162.ptr.us.xo.net 0.0% 280 76.4 83.6 74.4 104.5 10.9 7. vb6.rar3.chicago-il.us.xo.net 0.0% 280 73.7 80.2 69.6 107.7 12.9 8. te-4-1-0.rar3.denver-co.us.xo.net 0.0% 280 76.0 83.7 74.5 104.4 10.8 9. te0-13-0-0.rar3.la-ca.us.xo.net 0.0% 280 75.8 88.9 74.7 164.6 15.7 10. ae0d0.mcr1.la-ca.us.xo.net 0.0% 280 76.3 116.1 73.7 351.9 62.0 11. 216.2.226.58 0.0% 280 74.2 98.8 73.9 324.2 43.1 12. 208.69.81.158 0.0% 279 74.0 81.0 73.8 101.1 10.9
Thanks in advance
Nathan
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages