This issue was on the remote side of one of our peering sessions, and has since been resolved. Have a look again and feel free to contact me off-list if you're still seeing any issues there. Thanks! On 1/6/15 2:46 PM, Andree Toonk via Outages wrote:
Seeing similar issues between a few US, Asia and EU sites. What I'm seeing is what appears to be a congested peering connection between GTT and NTT in Seattle as that is what all traceroutes have in common.
Our graphs indicate this started Jan 1st, around ~ 15:00 utc.
Example traceroute from Seattle (ntt) to Vancouver (gtt):
HOST: rtr1-re0.sea Loss% Snt Last Avg Best Wrst StDev 1. xe-0-0-0-34.r04.sttlwa01.us. 0.0% 60 4.1 8.3 0.8 23.9 6.5 2. ae3.sea22.ip4.gtt.net 20.0% 60 44.6 41.9 33.6 60.3 6.0 3. xe-1-2-0.van10.ip4.gtt.net 18.3% 60 48.9 51.6 38.0 129.1 17.3 4. opendns-gw.ip4.gtt.net 20.0% 60 46.6 46.6 38.3 65.1 6.9 5. rtr1.yvr.opendns.com 28.3% 60 44.8 47.5 38.6 74.2 8.9
Cheers, Andree
.-- My secret spy satellite informs me that at 2015-01-05 3:04 PM Hugh Smallwood via Outages wrote:
Seeing awful peering issues with GTT today. Specifically between Level3 in LA and their own network between Washington and Phoenix.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages