Live data from Hacker News

Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

news.ycombinator.com

1–10 of 35 posts

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#6
post #2

Maybe AWS US East is going to be the region with random failures? "I want to have an AWS region where everything breaks with high frequency" https://news.ycombinator.com/item?id=24103746

From the comments:

> Isn’t us-east-1 exactly that?

We've come full circle

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#7
post #5

It would help if you defined exactly what type of issues you experienced. Packet loss? Early RSTs? Latency? Single AZ or cross AZ? Same for VPCs or NAT'd internet traffic? You should take some tcpdumps and open a support case.

Connection issues between hosts, it appears to be across AZ. Internal traffic inside a VPC

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#8
post #2

Maybe AWS US East is going to be the region with random failures? "I want to have an AWS region where everything breaks with high frequency" https://news.ycombinator.com/item?id=24103746

It always has been - us-east-1 is the biggest region by far, so scale problems tend to arise there first.

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#10
post #9

In any specific AZ or across the board?

Each account's AZ codes point to a different AZ—it's a way of avoiding conversations like this where people think a particular AZ is better than others.

That's no longer the case, except in legacy regions (which IAD is); I think there's a reconciliation mechanism though in those cases.
Post reply on HN