When you pin a custom feed to your Bluesky home tab, you may see a ‘Feed Offline’ error instead of fresh posts. This error means the feed’s server cannot be reached or the feed algorithm has stopped updating. The problem is almost always on the feed creator’s side, not your account. This article explains the technical reasons behind the error and shows you what to do when it happens.
Key Takeaways: Fixing the ‘Feed Offline’ Error on Bluesky
- Feeds tab > Pinned feed > Refresh: Pull down to force a reconnection attempt from your client.
- Feed creator’s server downtime: The feed’s hosting service or AT Protocol relay may be unreachable.
- Feed algorithm update failure: The feed’s code stopped running due to errors or rate limits on the hosting platform.
Why a Pinned Custom Feed Shows ‘Feed Offline’
A custom feed on Bluesky is not a static list of posts. It is a live algorithm that runs on a separate server, often hosted on a free or low-cost platform like Fly.io, Railway, or a personal VPS. The feed server connects to Bluesky’s AT Protocol relay to fetch new posts, applies its filtering logic, and returns a list of post URIs. When the feed server cannot respond to Bluesky’s request, the client displays ‘Feed Offline’.
There are three main technical causes for this error:
1. Feed Server Is Down or Unreachable
The server hosting the feed algorithm may have crashed, been stopped by the hosting provider, or exceeded its resource limits. Free-tier hosting services often put idle servers to sleep after a period of inactivity. If the feed creator has not configured a keep-alive ping, the server goes to sleep and Bluesky cannot reach it.
2. AT Protocol Relay Connection Lost
The feed server relies on a connection to one of Bluesky’s AT Protocol relays to subscribe to firehose events. If the relay experiences a temporary outage or the feed server’s subscription token expires, the feed stops receiving new data. The feed server may still be running, but it has no new posts to serve.
3. Feed Algorithm Code Error
The feed algorithm itself may contain a bug that causes it to crash when processing certain posts. For example, if the code cannot handle a malformed post record or a missing field, the entire feed process stops. The feed server stays online, but the algorithm returns an empty or error response to Bluesky.
Steps to Diagnose and Resolve the ‘Feed Offline’ Error
You cannot fix the feed server yourself unless you are the feed creator. However, you can check if the problem is temporary or permanent and decide whether to unpin the feed.
- Refresh the feed manually
Open the Bluesky app or web client. Tap or click the pinned feed showing the error. Pull down on the feed to force a refresh. If the feed loads after one or two refreshes, the server was briefly unreachable. This often happens when a sleeping server wakes up. - Check the feed’s status on Bluesky directory
Go to the Bluesky Feed Directory at feeds.bsky.app. Search for the feed’s name. If the feed appears in the directory with a green status indicator, the problem is likely a temporary network issue. If the feed is missing or shows a red status, the feed creator has removed or broken the feed. - Test the feed on a different client
Open Bluesky in a web browser on a different device or network. Pin the same feed. If the error appears there too, the feed server is definitely down. If the feed works on another client, the problem is with your original client’s cache or network. - Contact the feed creator
Find the feed creator’s Bluesky profile. Send a direct message or mention them in a post. Ask if the feed server is down or if the algorithm needs an update. Most feed creators appreciate knowing about the issue. - Unpin and repin the feed
Remove the feed from your pinned list. Go to the feed’s page and tap the pin icon again. This forces Bluesky to re-request the feed’s metadata and endpoint URL. Sometimes a stale cache causes the error even when the feed is working.
If the ‘Feed Offline’ Error Persists After Troubleshooting
The feed creator has stopped maintaining the feed
Many custom feeds are hobby projects. The creator may have lost interest, run out of free hosting credits, or moved to a different platform. If the feed has been offline for more than a week, it is likely abandoned. Unpin the feed and look for an alternative feed with a similar purpose.
The hosting provider suspended the feed’s server
Free-tier hosting services like Fly.io or Railway impose CPU and memory limits. If the feed algorithm uses too many resources, the provider suspends the server. The feed creator must upgrade to a paid plan or optimize the code. You cannot do anything about this except wait for the creator to fix it.
The feed uses a deprecated API endpoint
Bluesky’s AT Protocol is still evolving. The feed may rely on an API endpoint that Bluesky has deprecated or changed. The feed creator must update the code to use the current endpoint. Check the feed’s GitHub repository or documentation for any notices about the API change.
| Cause | What You Can Do | What the Feed Creator Must Do |
|---|---|---|
| Server sleep | Refresh the feed multiple times | Add a keep-alive ping or upgrade to a paid plan |
| Relay connection lost | Wait and retry later | Restart the feed server and renew the subscription token |
| Code error | Report the issue to the creator | Debug and redeploy the algorithm |
| Feed abandoned | Unpin and find a replacement feed | None |
Common Misconceptions About the ‘Feed Offline’ Error
It is not a Bluesky server outage
When Bluesky’s own servers are down, you cannot load any feeds, including the default ‘Following’ feed. If only one pinned feed shows the error while other feeds work, the problem is specific to that feed’s server.
It is not caused by your account being blocked
The ‘Feed Offline’ message is a technical error, not a moderation action. If a feed creator blocks you, the feed simply does not appear in your search results. You never see the offline error for a feed that has blocked you.
It is not a network issue on your side
A slow or unstable internet connection can cause feeds to load slowly, but it does not produce the ‘Feed Offline’ error. That error comes from Bluesky’s client after it fails to get a valid response from the feed server.
The ‘Feed Offline’ error on a pinned Bluesky feed is almost always a server-side problem. You can refresh the feed, check the directory, and contact the creator. If the feed remains offline for an extended period, unpin it and explore other custom feeds. To avoid this issue in the future, pin feeds from creators who actively maintain their code and use reliable hosting services such as Fly.io with a paid plan or a self-hosted VPS.