AWS internal networking team contact?

Thu Aug 24 02:43:17 UTC 2017

Hey all,

We are seeing major packet loss and high latency at a Level3 node just
before the hop into AWS us-west-2. We had a go live planned for today which
has now been scrapped because T-Mobile customers (a significant chunk of
our customer base) nationwide are unable to login to our app. AWS Support
is dragging their feet waiting to hear back from their internal networking
team and didn't even believe they peered with Level3 at us-west-2 and we
just don't have the time. CEO is talking about pulling the plug entirely on
us-west-2 if not all of AWS and re-deploying to us-east-X or GCP.

If someone from AWS could reach out off list to help expedite my ticket and
get in contact with Level3 to fix their Seattle nodes i'd really appreciate
it. It's already 740 on the west coast and I don't think i'm going home
anytime soon. :(

For those interested, failing nodes i'm seeing are
ae-1-51.ear2.Seattle1.Level3.net <http://ae-1-51.ear2.seattle1.level3.net/>
 and ae-2-52.ear2.Seattle1.Level3.net
<http://ae-2-52.ear2.seattle1.level3.net/>. Confirmed that T-Mobile is
routing through those nodes from both SF and NYC. Apple also rejected our
app during review this morning because of network failures while on wifi
which I have to assume are the same ones we've been seeing for the last 96
hours.

Thanks