Discord error 130000: API resource overloaded
Last verified against Discord Developer Docs - Opcodes and status codes
API resource is currently overloaded. Try again a little laterWhat error 130000 means
Discord could not serve the request because the resource behind it is overloaded. This is a capacity problem on Discord's side, and the literal message tells you what to do: try again later.
It can affect any endpoint, and it usually appears during wider incidents or heavy load on a particular resource. A bot that starts returning 130000 on many unrelated calls at once is seeing a platform issue, not a bug in its own code.
Retrying immediately makes the overload worse for everyone, including your bot. Space retries out with exponential backoff and jitter, cap the number of attempts, and keep track of failures so you can tell users the delay is on Discord's side.
Log the full response, headers and timestamp; that record is more useful for diagnosing an overload than changing code.
What it looks like
{
"message": "API resource is currently overloaded. Try again a little later",
"code": 130000
}Why it happens
- Discord incident or degraded service
- Heavy load on a specific resource your bot is calling
- Many workers retrying in sync and adding to the load
- Large bulk operation (mass role edits, member fetches) running during a busy period
How to fix Discord error 130000
- 1Check Discord's status page for an incident
- 2Retry with exponential backoff and jitter, with a cap on attempts
- 3Queue non-urgent work until errors stop
- 4Tell users the action will be retried rather than reporting a failure
- 5Log the endpoint and time of each failure to correlate them with incidents
How to stop it recurring
Build retries into a central request layer so every call gets the same backoff policy, and make background jobs resumable. Keep user-facing commands responsive by deferring and finishing later. Rate-limit behavior is on the Discord limits page. Pause background jobs while failures continue.
Official reference: Discord Developer Docs - Opcodes and status codes. See all Discord error codes or the Discord limits and quotas.
Related codes
- 40062: Service resource is being rate limitedService resource is being rate limited
- 429: HTTP 429 Too Many Requests (rate limited)You are being rate limited.
- 40006: Feature temporarily disabled server-sideThis feature has been temporarily disabled server-side
- 0: General errorGeneral error (such as a malformed request body, amongst other things)
Error 130000 - quick answers
What does Discord error 130000 mean?
Discord could not serve the request because the resource behind it is overloaded. This is a capacity problem on Discord's side, and the literal message tells you what to do: try again later. It can affect any endpoint, and it usually appears during wider incidents or heavy load on a particular resource.
How do I fix Discord error 130000?
1. Check Discord's status page for an incident 2. Retry with exponential backoff and jitter, with a cap on attempts 3. Queue non-urgent work until errors stop 4. Tell users the action will be retried rather than reporting a failure 5. Log the endpoint and time of each failure to correlate them with incidents
Can I retry after error 130000?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging Discord by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.