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.


