Bluesky ‘Rate Limit Exceeded’ Message: How Long to Wait

If you use Bluesky heavily, you have probably seen the Rate Limit Exceeded error message. This message appears when you send too many requests to Bluesky servers in a short time. The limit exists to prevent spam and server overload. This article explains exactly how long the cooldown lasts, what actions trigger the limit, and how to avoid hitting it again.

Why Bluesky Shows the Rate Limit Exceeded Error

Bluesky uses rate limiting to protect its servers from abuse. Each action you take on the platform sends a request to the server. If you send too many requests within a sliding window of time, the server returns a 429 HTTP status code and the Rate Limit Exceeded message. The rate limit applies per user account, per IP address, and per API endpoint. Common actions that trigger the limit include:

• Posting multiple times in under 10 seconds
• Liking or reposting many posts in rapid succession
• Following or unfollowing many accounts in a short burst
• Using third-party apps that poll the API too frequently
• Scraping feeds or user data with automated scripts

Bluesky does not publish exact rate limit numbers for every action, but community testing and the official API documentation reveal the following general limits:

• Posting: 100 requests per 5 minutes per user
• Reading feeds: 300 requests per 5 minutes per IP
• Searching: 30 requests per minute per IP
• Authentication: 10 requests per minute per IP

These limits are enforced using a sliding window, not a fixed clock. This means the cooldown does not reset at the start of every minute. Instead, the server checks the number of requests you made in the last 60 seconds or 5 minutes, depending on the endpoint. If you exceed the limit, you must wait until the oldest request in the window expires.

How Long the Cooldown Lasts and How to Check

The cooldown duration depends on which limit you exceeded. For most actions, the limit resets after 60 seconds. For posting and other write-heavy actions, the limit resets after 5 minutes. You can see the exact cooldown remaining by checking the HTTP response headers. Here is how to find that information:

Using a Browser

1. Open Developer Tools
   Press F12 or right-click anywhere on the page and select Inspect. Go to the Network tab.
2. Reproduce the Rate Limit Error
   Perform the action that caused the error, such as posting or liking. A network request will appear in the list with a red 429 status.
3. View Response Headers
   Click the 429 request. Look for the Headers section. Find the retry-after header. Its value is the number of seconds you must wait.

Using a Third-Party Tool

1. Install a REST Client
   Use a tool like Postman or curl to send a request to the Bluesky API endpoint that returned the error.
2. Read the Retry-After Header
   The response will include a retry-after header. For example, a value of 120 means wait 120 seconds before trying again.

If you are using the official Bluesky app or website, the error message itself does not show the cooldown time. In most cases, waiting 60 seconds resolves the issue. If you hit the posting limit, wait 5 minutes. The server automatically resumes processing your requests once the window clears.

If Bluesky Still Shows Rate Limit Exceeded After Waiting

Sometimes the error persists even after waiting the recommended time. This usually happens for one of three reasons: you are using a shared IP address, a third-party app is sending requests in the background, or you are still within the sliding window. Here is how to diagnose and fix each scenario.

Shared IP Address from a VPN or Proxy

If you use a VPN or corporate proxy, your IP address may be shared with many other users. If one of those users triggers the IP-based rate limit, you may see the error even if your own activity is normal. The fix is to disconnect from the VPN or proxy and use your direct internet connection. Alternatively, switch to a different VPN server location. After changing your IP, wait 5 minutes before continuing.

Third-Party App Running in the Background

Some third-party Bluesky clients or browser extensions poll the API every few seconds. Even if you are not actively using the app, it may be consuming your rate limit. To check, close all browser tabs that have Bluesky open. Quit any third-party Bluesky apps on your phone or desktop. Then wait 60 seconds and try again. If the error disappears, you have identified the culprit. Consider adjusting the app’s refresh interval in its settings if available.

Sliding Window Not Yet Expired

Because Bluesky uses a sliding window, the cooldown does not reset at a fixed time. If you made 100 posts in the last 4 minutes and 30 seconds, you must wait until the first post in that burst is more than 5 minutes old. This means the wait time can be longer than 5 minutes if your activity was spread out. To avoid this, wait 5 minutes plus an extra 30 seconds to be safe. The error should clear once the oldest request in the window expires.

Comparison of Bluesky Rate Limit Scenarios

Scenario	Typical Wait Time	Recovery Action
Posting too fast	5 minutes	Wait 5 minutes, then reduce posting frequency to 1 post per 3 seconds
Liking or reposting rapidly	60 seconds	Wait 60 seconds, then limit likes to 1 per second
Using a third-party app	60 seconds	Close the app or reduce its polling interval to 30 seconds or more
Shared IP via VPN	5 minutes after IP change	Disconnect VPN or switch to a different server
Automated scraping	Varies by endpoint	Stop the script and add delays of at least 1 second between requests

You can now identify the cause of the Rate Limit Exceeded error and know exactly how long to wait. To prevent future errors, slow down your actions and avoid using multiple apps simultaneously. For heavy automation, use the official Bluesky API and respect the documented limits by adding delays. If you use third-party clients, check their settings for a rate limit control or polling interval option.