Post AzOb2E451DcY6PfvbU by mate@bzh.social
 (DIR) More posts by mate@bzh.social
 (DIR) Post #AzOavOtqKv5pgAdHQ8 by bortzmeyer@mastodon.gougere.fr
       2025-10-20T09:07:42Z
       
       0 likes, 0 repeats
       
       "Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. "https://health.aws.amazon.com/health/status#DNSisGuilty @jpmens
       
 (DIR) Post #AzOb2E451DcY6PfvbU by mate@bzh.social
       2025-10-20T09:08:53Z
       
       0 likes, 0 repeats
       
       @bortzmeyer @jpmens #DNSLivesMatter
       
 (DIR) Post #AzOfDDf9Fn3nrDVl9U by bortzmeyer@mastodon.gougere.fr
       2025-10-20T09:55:43Z
       
       0 likes, 0 repeats
       
       @jpmens The root cause? https://x.com/ndbroadbent/status/1980172049147658445#itsAlwaysDNS
       
 (DIR) Post #AzOfJiI2IN1oaEnUZs by bortzmeyer@mastodon.gougere.fr
       2025-10-20T09:56:55Z
       
       0 likes, 0 repeats
       
       @jpmens See also https://dnsviz.net/d/dynamodb.us-east-1.amazonaws.com/aPXixQ/dnssec/ (no IP address, there is now one)
       
 (DIR) Post #AzOgC1o1x2EWkUf5P6 by nicolasvivant@colter.social
       2025-10-20T10:00:55Z
       
       0 likes, 0 repeats
       
       @mate @bortzmeyer @jpmens Le DNS a sa propre vie, parfois il tombe malade on peut pas savoir.
       
 (DIR) Post #AzOgC2oQD48lrzqueW by bortzmeyer@mastodon.gougere.fr
       2025-10-20T10:06:42Z
       
       0 likes, 0 repeats
       
       @nicolasvivant @mate @jpmens "We are seeing significant signs of recovery" https://health.aws.amazon.com/health/status