AWS explains Route 53’s higher API rate and separate DNS change budget

November 4, 2026

AWS detailed Route 53’s revised API throttling model in a November 3, 2026 post. The limits have applied since July 30; the publication explains an existing change rather than announcing a new November rollout.

Two independent limits

The default request rate increased from five to ten API calls per second per account. A separate change-throughput budget refills at 100 tokens per second, regardless of how modifications are grouped into requests.

A record CREATE or DELETE consumes one change token, while an UPSERT consumes two. Consequently, the budget should not be interpreted as allowing 100 sustained UPSERT operations per second.

Scope matters for automation

Either limit can throttle a request, and some operations have lower request-rate allowances. More capacity for API calls does not remove the separate limit on the work those calls submit.

The model covers Route 53 DNS APIs for hosted zones, records and health checks. Resolver, Profiles and domain-registration APIs use separate limits.

Source: AWS Route 53 throttling explanation, November 3, 2026.

Feature image: AI-generated editorial illustration for Guava Insights. Conceptual artwork, not an actual product photograph, interface or facility.

Topics:
Read next
November 20, 2026

U.S. Expands AI-Chip Controls to Remote Cloud Access as China Pushes Domestic Alternatives

A new U.S. interim rule extends advanced AI-computing controls to remote access through overseas data centres, raising compliance and infrastructure questions for cloud providers and Chinese technology companies.
November 19, 2026

AI’s Next Infrastructure Bottleneck Is Not Chips. It Is Coordination.

The AI buildout is no longer constrained by one missing component. Chips, packaging, data-centre shells, electricity, grid connections, and financing now have to arrive together—and the cost of that coordination is becoming a public policy issue.
November 13, 2026

Microsoft 365 Outage Exposes the Operational Cost of Cloud Dependence

A global Microsoft 365 outage disrupted Outlook, Teams and Copilot for more than 12 hours. The incident shows why cloud concentration must be treated as an operational resilience risk.