Skip to main content
AWS

ROUTE53 (global): Increased API Error Rates

Degraded Lasted 35m · started · AWS's page

Level
confirmed
Worst impact
Degraded
Components
ROUTE53
Regions
global
Down Index
46of 100

What to do

  • Check whether you use AWS ROUTE53 in global. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 35m it lasted.

    Anything that failed between 2026-05-22 23:38 UTC and 2026-05-23 00:13 UTC may need a replay.
  • Subscribe to AWS's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from AWS 2

  1. investigating

    We are investigating increased error rates for Route53 API calls.

    provider

  2. investigating

    Between 4:00 PM and 4:46 PM, we experienced increased error rates for the Route53 APIs. This issue did not impact resolution of existing DNS records. Engineers were automatically engaged and immediately began investigating the issue. During this time, customers may have received 500s for Route53 APIs and the Route53 Management Console. We have identified the root cause and have mitigated this issue. Other AWS Services that call the Route53 APIs in their workflows may also have been impacted during this time. We recommend retrying any failed operations or stuck workflows. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-cc15031507

Is AWS still down?

No, this incident was resolved 2026-05-23 00:13 UTC. For AWS's live state, see https://down.guide/aws.

How long did it last?

35m, from 2026-05-22 23:38 UTC to 2026-05-23 00:13 UTC, by the times AWS posted.

What was affected?

AWS named ROUTE53 in global.

What caused it?

AWS hasn't published a root cause. If it does, it shows here.

Where does this come from?

AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.