How to Fix Discord Error 130000 API Resource Currently Overloaded

Discord Error 130000 appears when an API resource you are trying to access is temporarily overloaded. This happens most often when a server has a large number of members or high message volume, and the server’s API endpoints cannot keep up with the request rate. The error message reads “API resource currently overloaded. Try again later.” This article explains what causes the error and provides specific steps you can take to resolve it on your end.

Why Discord Error 130000 Occurs

Discord’s API has rate limits that protect the platform from excessive requests. When a client or bot sends too many requests in a short time, or when the server itself is under heavy load from many users, the API returns a 130000 error. The error is a 429 HTTP status code, meaning “Too Many Requests.” The server is telling you to slow down.

Common triggers for Error 130000 include:

• Running a custom bot that polls the API too frequently. Bots that check for new messages every few milliseconds can hit rate limits.
• Using a third-party Discord client or modification. Unofficial clients may send malformed requests or ignore rate limits.
• Joining a very large server during peak hours. The server’s API endpoints may be overwhelmed by thousands of users.
• Automated scripts or browser extensions. Tools that scrape Discord data can trigger the error.

The error is not caused by your internet connection, Discord account issues, or outdated app versions. It is purely a server-side overload signal.

Steps to Fix Discord Error 130000

The primary fix is to stop sending requests to the overloaded resource and wait. Below are the exact steps for different scenarios.

1. Wait 30 to 60 seconds and retry
   Discord’s API overload is temporary. Close the dialog or channel that showed the error. Wait at least 30 seconds, then refresh the page or reopen the channel. In most cases, the error disappears after a short pause.
2. Check Discord status page
   Go to discordstatus.com and look for any incidents labeled “API” or “General issues.” If a major outage is reported, wait for Discord to resolve it. You do not need to take any action on your end.
3. Restart the Discord app or web client
   Close Discord completely. On Windows, right-click the Discord icon in the system tray and select Quit Discord. Reopen the app and try again. This clears any cached API requests that may be queued.
4. Reduce bot request rate if you run a bot
   If you operate a Discord bot, check your code for loops or event handlers that call the API too frequently. Add a delay using time.sleep(1) or equivalent in your language. For example, in discord.py, use await asyncio.sleep(1) between API calls to stay within Discord’s rate limit of 50 requests per second for most endpoints.
5. Disable third-party Discord clients
   If you use an unofficial client like BetterDiscord or Powercord, switch back to the official Discord app. Unofficial clients often bypass rate limits and cause the 130000 error. Uninstall the modification and reinstall Discord from the official website.
6. Disable browser extensions that interact with Discord
   Extensions such as Discord Chat Exporter or Discord Theme Injectors can send extra API requests. Temporarily disable all extensions in your browser. In Chrome, go to More Tools > Extensions and toggle off each extension. Then reload Discord.

If Discord Still Shows Error 130000 After the Main Fix

Error appears only on one server

If the error only occurs when you access a specific server, that server may be experiencing an API overload due to high traffic. Leave the server and rejoin after a few minutes. If you are the server owner, consider enabling Slow Mode under Server Settings > Overview > Slow Mode to reduce message frequency.

Error appears when using a bot command

If a bot command triggers the 130000 error, the bot itself is likely hitting rate limits. The bot developer must fix this. As a user, you cannot resolve it. Try using the command again after 60 seconds. If the error persists, notify the bot developer.

Error appears on the Discord web client but not the app

Clear your browser cache and cookies. In Chrome, press Ctrl + Shift + Delete, check Cookies and other site data and Cached images and files, then click Clear data. Reload Discord. If the issue continues, use the desktop app instead.

Error appears repeatedly on the desktop app

Reset Discord’s voice and API settings. Close Discord, press Windows Key + R, type %appdata%/discord, and press Enter. Delete the Cache and Code Cache folders. Restart Discord. This clears stored API data that may be causing repeated requests.

Discord API Rate Limits: User vs Bot Limits

Item	User Account	Bot Account
Base rate limit	50 requests per second per endpoint	50 requests per second per endpoint
Global rate limit	Not enforced for normal usage	1000 requests per 5 seconds
Error returned on overload	130000	130000
Retry-After header value	1 to 10 seconds typically	1 to 60 seconds depending on severity
Recommended action	Wait and retry manually	Implement exponential backoff in code

Discord Error 130000 is a temporary condition that signals you or the server are sending too many API requests. The most effective fix is to wait a short time and reduce your request rate if you run automation. Check the official Discord status page to rule out a platform-wide issue. For bot developers, implementing proper rate limiting with exponential backoff prevents the error entirely. As a regular user, simply waiting and retrying is almost always enough.