Skip to content

HTTP status codesUpdated 2 Nov 2026

429 Error Code: Slow Down, Too Many Requests

Quick answer A 429 means too many requests came from you or your network in a short time. Stop refreshing, wait a few minutes, and the block usually lifts by itself.

HTTP status429
Impact
Low impact
Typical fix time
Minutes to an hour
Who fixes it
You, by waiting

The 429 error code is the server's polite way of saying you are going too fast. Websites and apps count how often one person or network asks for something. When the count passes the allowed limit, the server stops answering for a while and shows "429 Too Many Requests". This protects the service from overload and from automated abuse.

It is one of the few errors where the reader's own behaviour often matters. Pressing refresh again and again, a broken login loop or a busy shared network can all trigger it. The cure is usually patience, and below are the steps in order.

Common causes

  • 1Refreshing or retrying too fast

    How to tellError began after many quick reloads or taps

    What fixes itStop for 5 to 10 minutes, then try once

  • 2Several wrong password attempts

    How to tellAppears on a login page after repeated tries

    What fixes itWait, then use the Forgot password link instead of guessing

  • 3Many people on one shared network

    How to tellOffice, hostel or public Wi-Fi users all see it

    What fixes itSwitch to mobile data for a test

  • 4An app or browser add on sending background requests

    How to tellError with no action from you; another device is fine

    What fixes itClose extra tabs, turn off the add on, update the app

  • 5API or script calling too often

    How to tellDeveloper sees 429 with a Retry-After value

    What fixes itSlow the calls and follow the retry time

  • 6Plan or quota reached

    How to tellMessage mentions a limit for the hour or day

    What fixes itWait for the reset or ask the provider for a higher limit

How to fix it, step by step

  1. Stop reloading and wait

    Every extra try can lengthen the block. Leave the page alone for 5 to 10 minutes. Many limits reset in about a minute, but some last an hour.

  2. Read the message for a time

    Some pages say "try again in 60 seconds" or show a countdown. Servers can also send a Retry-After hint. If you see a time, follow it exactly.

  3. Close extra tabs and background apps

    Ten open tabs of the same site can each send requests. Close them, keep one, and check that no app is syncing the same account in the background.

  4. Test on mobile data

    If the page loads on mobile data, the limit was applied to your Wi-Fi network address, perhaps because many people share it. Use mobile data for now or ask the network admin.

  5. Turn off VPN and unneeded add ons

    Many people share a VPN server, so the combined requests hit the limit. Disconnect, and disable any browser add on that refreshes or fetches pages in the background.

  6. Use password reset, not repeated guesses

    On a login screen, a block after wrong attempts is a safety feature. Reset the password with the official link rather than trying again.

  7. Contact support if it never clears

    If you are blocked for hours with little use, send the support team your time, page and device. Never give out your passwords or one time codes in that message.

429 error code meaning in plain words

Think of a queue at a ticket window where the clerk says only a few requests per minute can be handled for each person. If you keep pushing in, she asks you to step aside and wait. The 429 status does the same. It is a client side code, so the server says the request was valid in form but arrived too often. The counter is normally based on your account, your device or your network address.

After tapping Send OTP five times you see 429 Too Many Requests. Please try again later. Do not tap again. Wait the stated time, then request one code only.

For developers: handling the too many requests error code

  • Read the Retry-After header and pause for that long.
  • Use exponential backoff: wait a little, then double the wait after each failure.
  • Cache responses so the same data is not fetched again and again.
  • Batch calls where the API allows it.
  • Look at the provider's documented limits per minute and per day.

Do not try to dodge a rate limit by rotating addresses. It can lead to a permanent ban.

For site owners

Set limits that suit real users. A limit that is too tight hurts shared networks such as colleges, so allow reasonable bursts. Always send a clear message and a retry time, and log which address or key hit the limit so you can tell abuse from a bug in your own app.

Frequently asked questions

What does error code 429 mean?

It means too many requests were sent in a short time, so the server paused your access. Waiting is normally the fix.

How to fix error 429 too many requests on my phone?

Stop retrying, wait 10 minutes, close extra tabs or app copies and try once on mobile data. If the app is old, update it.

How long does a 429 block last?

Often a minute to an hour. Some services show a countdown or say when to retry. Login related blocks may last longer.

Is the 429 error code a sign of a virus?

Usually no. It is a rate limit. A rare cause is an infected device sending traffic on its own, but a normal case is just too many taps or a shared network.

Can a VPN cause a 429?

Yes, because many users share one VPN address and the combined requests pass the limit. Disconnect the VPN and test again.