429 Too Many Requests: what to do next
A 429 response asks a visitor or application to slow down because a request limit has been reached. Limits help protect a service, and a response may include a waiting period. The first useful step is to stop repeated attempts, not to find a way around the restriction.
Before you start
- Record whether the message appeared while browsing, signing in, submitting a form or running a tool.
- Save the visible waiting instruction and the time of your last attempt.
- If payment or a booking was involved, preserve the reference and check its status before trying again.
What to do
Pause the repeated activity
Close duplicate tabs and stop any automatic refresh or checker you started. Follow the displayed wait time if one is provided. If the page gives no guidance, contact the service owner rather than inventing a rapid retry schedule. Repeated clicking is not a useful test.
Check whether an action already completed
For a form, order or booking, look for the expected confirmation through the normal account or contact route. Ask the owner to check uncertain submissions before repeating them. An error page does not give enough information to conclude that no business record was created.
Report normal use that triggers the limit
If ordinary customer browsing repeatedly hits the restriction, describe the shortest sequence that led to it. Include the page, device, approximate request frequency and displayed reference. The administrator can compare legitimate use with the configured limit without removing protection for the entire site.
Retest the agreed correction once
After the owner confirms a safe time or a configuration change, carry out one normal customer journey. A useful result is ordinary use succeeding while excessive automated activity remains limited. Ask for a clear customer-facing message and an alternative contact route if waiting is unavoidable.
What to check
- Repeated or automated requests have stopped.
- An uncertain order or enquiry has been checked before resubmission.
- The service owner has enough evidence to review legitimate access without disabling protection.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.