Discussion · bonfire.cafe

Discussion

Log in

Stéphane Bortzmeyer

@bortzmeyer@mastodon.gougere.fr · 4 months ago

"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

https://null/health/status

View the overall status and health of AWS services using the AWS Health Dashboard.

Stéphane Bortzmeyer

@bortzmeyer@mastodon.gougere.fr · 4 months ago

@jpmens The root cause? https://x.com/ndbroadbent/status/1980172049147658445

X (formerly Twitter)

Stéphane Bortzmeyer

@bortzmeyer@mastodon.gougere.fr · 4 months ago

@jpmens See also https://dnsviz.net/d/dynamodb.us-east-1.amazonaws.com/aPXixQ/dnssec/ (no IP address, there is now one)

dynamodb.us-east-1.amazonaws.com | DNSViz

Mathieu - Heureux et Perchés

@mate@bzh.social · 4 months ago

@bortzmeyer @jpmens

#DNSLivesMatter

@nicolasvivant@colter.social · 4 months ago

@mate @bortzmeyer @jpmens

Le DNS a sa propre vie, parfois il tombe malade on peut pas savoir.

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.34 no JS en

Automatic federation enabled

Log in