...and hopefully this closes it out. Looks like it was specific to a single AZ (now folks know why I said what I did): https://status.aws.amazon.com/ Amazon Elastic Compute Cloud (N. Virginia) [RESOLVED] Instance launch errors and connectivity issues 1:49 PM PDT Between 1:06 PM and 1:33 PM PDT we experienced increased error rates for new instance launches and intermittent network connectivity issues for some running instances in a single Availability Zone in the US-EAST-1 Region. The issue has been resolved and the service is operating normally -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator PGP 4BD6C0CB | | Making life hard for others since 1977. | On Tue, Aug 07, 2018 at 01:47:53PM -0700, Jeremy Chadwick via Outages wrote:
Once again: us-east-1 or us-east-2? It matters. (I will also take a moment to state the same for us-west-1 vs. us-west-2)
If you're talking about us-east-1: I've seen a couple strange internal networking events where classic ELBs were briefly reporting TCP socket timeouts (clients in us-east-1, ELBs in us-east-1), but they were short-lived (read: less than 60 seconds). I didn't check to see if it was isolated to a single AZ.
If you're talking about us-east-2: I lack insights there.
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator PGP 4BD6C0CB | | Making life hard for others since 1977. |
On Tue, Aug 07, 2018 at 04:32:16PM -0400, James Milko via Outages wrote:
Is anyone else seeing issues with AWS again? We're seeing connectivity issues to Amazon services with in US-East, between US-East and US-West and US-East to outside of AWS locations.
JM
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages