Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
1–10 of 35 posts
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#2"I want to have an AWS region where everything breaks with high frequency" https://news.ycombinator.com/item?id=24103746
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#3Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#4Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#5You should take some tcpdumps and open a support case.
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#6Maybe 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
> 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?
#7It 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.
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#8Maybe 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
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#9In any specific AZ or across the board?
Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?
#10In 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.