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
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
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
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
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
Could an IP engineer from AWS (16509/14618) and one from NTT (2914) kindly
contact me off-list? AS1 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
6 matches
Mail list logo
