After migrating your Bluesky account to a new server or changing your hosting provider, you may notice that your Followers feed stops updating or shows stale data. This happens because your account's index on the relay server is tied to the old DNS records and AT Protocol identifiers. The relay does not automatically rebuild the index after a migration. This article explains why the Followers feed breaks during migration and provides the exact steps to trigger a reindex so your feed returns to normal.
Key Takeaways: Reindexing Your Bluesky Account After Migration
- Settings > Account > Reindex: Manually triggers a full rebuild of your account's index on the relay server, fixing the Followers feed.
- Wait 10–15 minutes after reindex: The relay needs time to process the rebuild; the feed will not update instantly.
- Check DNS TXT records for your custom domain: Incorrect or missing records cause the migration to fail and the feed to stay broken.
Why Migrating Your Bluesky Account Breaks the Followers Feed
Bluesky uses the AT Protocol to distribute user data across relays. Each account has a unique DID (Decentralized Identifier). When you migrate your account to a new PDS (Personal Data Server) or change your custom domain, the DID stays the same, but the relay that indexes your posts and follows must update its reference to the new hosting location. If the relay does not receive a fresh index request, it continues to point to the old server. The Followers feed then shows no new followers or fails to load because the relay cannot find the updated data.
The migration process involves updating your DNS TXT records to verify domain ownership and then telling Bluesky to switch the hosting endpoint. Even after these steps succeed, the relay holds a cached version of your account data. The only way to force the relay to fetch the latest data is to initiate a reindex from the account settings. Without this step, the Followers feed remains stuck on the pre-migration state.
Steps to Reindex Your Account After a Bluesky Migration
The reindex operation is a manual button inside the Bluesky app or web client. It sends a request to the relay to rebuild your account index from scratch. Follow these steps exactly.
- Open Bluesky Settings
On the web or mobile app, click your profile picture in the top right corner. Select Settings from the dropdown menu. - Navigate to Account Settings
In the Settings panel, click Account from the left sidebar or scroll to the Account section on mobile. - Scroll to the Advanced Section
Scroll down until you see the heading Advanced. It is located below the Handle and Password sections. - Click the Reindex Button
Under Advanced, click the button labeled Reindex. A confirmation dialog appears. Read the warning that this action may temporarily affect your feed. Click Reindex again to confirm. - Wait 10 to 15 Minutes
Do not close the app or browser tab during this time. The relay processes the rebuild in the background. Your Followers feed will show a loading state or appear empty until the reindex completes. - Refresh the Followers Feed
After 15 minutes, pull down to refresh the feed on mobile or press F5 on the web. The feed should now display your current followers in real time.
If the feed still shows old data after refreshing, repeat the reindex once more. In rare cases, the relay may need two cycles to fully update.
If the Followers Feed Still Has Issues After Reindex
DNS Records Are Missing or Incorrect
The most common cause of a failed reindex is a misconfigured DNS TXT record for your custom domain. Bluesky requires a TXT record with the value did=did:plc:YOURDID. If this record is missing, the relay cannot verify your domain and will not reindex your account. Use a DNS checker tool to confirm the record exists and matches your DID exactly. After fixing the DNS record, wait for propagation and then reindex again.
The Migration Did Not Complete on the PDS Side
If you are self-hosting your PDS, ensure the migration command finished without errors. Check your PDS logs for lines containing migration complete or reindex requested. If the migration script failed, the relay never receives the updated endpoint. Rerun the migration steps from the Bluesky documentation for self-hosted PDS.
Your Account Is Still Cached on an Old Relay
Some relays may cache your account data for up to 24 hours. If the reindex button does not resolve the issue, wait a full day and check again. You can also try accessing your account from a different relay by using a different Bluesky client or app that connects to an alternative relay endpoint.
Bluesky Reindex vs DNS Update vs PDS Migration: Key Differences
| Item | Reindex | DNS Update | PDS Migration |
|---|---|---|---|
| Purpose | Forces the relay to rebuild the account index | Verifies domain ownership to Bluesky | Moves the account data to a new server |
| When to perform | After migration or when feed shows stale data | Before migration or when changing custom domain | When switching hosting providers or servers |
| Time to take effect | 10–15 minutes | Up to 24 hours for propagation | Immediate after command completion |
| User action required | Click Reindex button in Settings | Edit DNS records at domain registrar | Run migration command on PDS |
After a migration, you must complete all three steps in sequence: update DNS, run the PDS migration, then reindex in Bluesky settings. Skipping the reindex leaves the relay with outdated data, which is why the Followers feed fails to update.
You now know how to fix a broken Followers feed after a Bluesky migration by using the Reindex button in Settings > Account > Advanced. If the problem persists, verify your DNS TXT record and confirm the PDS migration completed. For future migrations, set a calendar reminder to perform the reindex immediately after the migration command finishes. This ensures your followers see the correct data without waiting for the relay to refresh on its own.