AWS explains Route 53's higher API limits and change throttling

Amazon Web Services has published new guidance explaining Route 53's updated API throttling model. The November 3 post describes a default rate of 10 requests per second, increased from five, alongside a separate limit that measures how much DNS-changing work an account submits.

The timing matters: AWS says these changes have applied since July 30, 2026. The new publication is an explanation of existing behaviour, rather than a feature that first became available this week. It is aimed at engineers using infrastructure automation and scripts to manage DNS.

The two limits operate independently. Staying within the permitted number of API calls does not necessarily mean a large collection of record changes will avoid throttling. AWS distinguishes between how often an application sends requests and the total work represented by those requests. The guidance covers DNS APIs and does not extend the same limits to Resolver, Profiles or domain registration operations.

JetherVerse's assessment is that deployment teams should review their automation at the shared-account level. A pipeline that behaves well in isolation may run alongside another deployment or a migration. Our recommendation is to include that overlap in testing before increasing concurrency simply because the advertised request allowance is higher.

A useful internal review could identify every process that changes records, assign ownership and document how failures are reported. For larger moves, we suggest defining a recovery plan before running the migration. Engineers should be able to distinguish an incomplete batch from a completed one without relying on memory or manually comparing a long terminal history.

Our practical takeaway is to measure successful work and operational reliability together. Faster API submission is only useful when automation can track the outcome, handle interruption and resume cleanly. Teams maintaining older deployment notes should compare those notes with the current Route 53 documentation, then test any revised workflow against a small, reversible set of records before applying it more widely.