nanog mailing list archives
routing issues to AWS via 2914(NTT)
From: Christopher Rogers <phiber () phiber org>
Date: Thu, 12 Jun 2014 09:55:42 -0700
Could an IP engineer from AWS (16509/14618) and one from NTT (2914) kindly contact me off-list? AS18888 is having some major reachability issues to you via 2914. Several of our applications and users are reporting problems trying to reach various aws hosted services such as netflix and twilio. I'm seeing almost 50% packet loss when transiting to you via 2914. Forcing traffic onto 3356 clears the issue right up. I've had to effectively shift all my ingress traffic off 2914 and de-pref aws as-path to force egress to other transit. We're a customer of 2914, but not AWS. I've got a ticket open with 2914, and they've reached out to AWS, but it's been two days now and we haven't been getting any traction on this. thanks! -chris
Current thread:
- routing issues to AWS via 2914(NTT) Christopher Rogers (Jun 12)
- Re: routing issues to AWS via 2914(NTT) Bryan Socha (Jun 12)
- Re: routing issues to AWS via 2914(NTT) Paul WALL (Jun 13)
- Re: routing issues to AWS via 2914(NTT) Bryan Socha (Jun 13)
- Re: routing issues to AWS via 2914(NTT) Matt Palmer (Jun 13)
- Re: routing issues to AWS via 2914(NTT) joel jaeggli (Jun 13)
- Re: routing issues to AWS via 2914(NTT) Paul WALL (Jun 13)
- Re: routing issues to AWS via 2914(NTT) Bryan Socha (Jun 12)