Re: routing issues to AWS via 2914(NTT)

2014-06-13 Thread joel jaeggli
On 6/13/14, 2:28 PM, Matt Palmer wrote: > On Fri, Jun 13, 2014 at 11:44:51AM +, Paul WALL wrote: >> Amazon peers at many key exchanges, with dozens of hosting shops >> (where customers might share mutual infrastructure) like yours: >> >> https://www.peeringdb.com/view.php?asn=16509 >> >> Rather

Re: routing issues to AWS via 2914(NTT)

2014-06-13 Thread Matt Palmer
On Fri, Jun 13, 2014 at 11:44:51AM +, Paul WALL wrote: > Amazon peers at many key exchanges, with dozens of hosting shops > (where customers might share mutual infrastructure) like yours: > > https://www.peeringdb.com/view.php?asn=16509 > > Rather than play the blame game with third-party tra

Re: routing issues to AWS via 2914(NTT)

2014-06-13 Thread Bryan Socha
I don't think anyone is blaming anyone, just trying to pass on information where we see a problem.We routed around it no problem. Bryan Socha On Fri, Jun 13, 2014 at 7:44 AM, Paul WALL wrote: > Amazon peers at many key exchanges, with dozens of hosting shops > (where customers might share

Re: routing issues to AWS via 2914(NTT)

2014-06-13 Thread Paul WALL
Amazon peers at many key exchanges, with dozens of hosting shops (where customers might share mutual infrastructure) like yours: https://www.peeringdb.com/view.php?asn=16509 Rather than play the blame game with third-party transit providers, why not hit them up for some sessions? Drive Slow, Pau

Re: routing issues to AWS via 2914(NTT)

2014-06-12 Thread Bryan Socha
Amazon hasn't reached out to us either... If you have other providers, use a combination of local-preference and the customer communitiy strings with ntt to prepend around the circuit(s) in nyc with the issue. Just check your routing table, we found many going through ntt to amazon and took awhil