3 ms·
Looks like maybe a DNS issue? https://www.whatsmydns.net/#A/dynamodb.us-east-1.amazonaws.com https://www.whatsmydns.net/#A/dynamodb.us-east-1.amazonaws.c...
by atymic 1y ago
Looks like maybe a DNS issue?
https://www.whatsmydns.net/#A/dynamodb.us-east-1.amazonaws.com https://www.whatsmydns.net/#A/dynamodb.us-east-1.amazonaws.c...
Resolves to nothing.
- immibis 1y agoIt's plausible that Amazon removes unhealthy servers from all round-robins including DNS. If all servers are unhealthy, no DNS. Alternatively, perhaps their DNS service stopped responding to queries or even removed itself from BGP. It's possible for us mere mortals to tell which of these is the case.
- Nextgrid 1y agoChances are there's some cyclical dependencies. These can creep up unnoticed without regular testing, which is not really possible at AWS scale unless they want to have regular planned outages to guard against that.
- theshrike79 1y agoIt's always DNS.
- Sparkyte 1y agoMaybe they forgot to pay the bills.