Mastodon Remote Timeline Stops Updating After Instance Change: Fix

After moving your account to a new Mastodon instance, the remote timeline may stop showing new posts. This often happens because the new instance has not fully connected to the same federated servers as your old instance. The remote timeline relies on active subscriptions to other servers, and these subscriptions do not transfer automatically during an account migration. This article explains why the remote timeline freezes after an instance change and provides step-by-step fixes to restore live federation.

Why the Remote Timeline Stops Updating After an Instance Change

When you move your Mastodon account to a new instance, you bring your profile, followers, and posts. But you do not bring the list of servers your old instance was federating with. The remote timeline, which shows public posts from other servers, only updates when your new instance actively subscribes to those servers. If the new instance has never connected to a particular server, it will not pull in posts from that server until someone on the new instance follows a user on that server or manually fetches a post from it.

Additionally, some Mastodon instances use domain blocks or silence servers to limit unwanted content. If your new instance has blocked or silenced a server you frequently followed on the old instance, posts from that server will not appear in the remote timeline at all. The migration process does not transfer instance-level federation settings, so you must check and adjust these on the new server.

Federation Handshake and Subscription Timeout

Mastodon uses a subscription model for federation. When your new instance wants to receive updates from a remote server, it sends a subscription request. The remote server must accept this request. If the remote server is overloaded, offline, or has a block on your new instance, the subscription fails silently. The remote timeline then shows no new posts from that server until the subscription is re-established.

Steps to Restore the Remote Timeline on Your New Instance

1. Verify the new instance federation status
   Go to Preferences > Administration > Server > Federation. Look for any domain blocks or limits. If a server you want to see is listed as blocked or silenced, remove the block or change the severity to “none”. This step is only available to instance administrators. If you are not an admin, contact your instance admin and ask them to unblock the servers you need.
2. Manually pull a post from a remote server
   Copy the URL of a public post from a server that is not federating. Paste this URL into the Mastodon search bar on your new instance. Press Enter. Mastodon will fetch the post and the associated user and server. This action triggers a subscription to that remote server. After a few seconds, new posts from that server should start appearing in the remote timeline.
3. Follow a user from the missing server
   Search for a user on the remote server by typing their full handle (for example, @username@example.com) in the search bar. Follow that user. This action also triggers a server subscription. Once you follow one user, the remote timeline will show public posts from that server.
4. Wait for organic federation
   If you do not manually trigger subscriptions, the new instance will eventually discover servers through other users on the instance who follow remote users. This can take hours or days. For immediate results, use the manual pull method in step 2.
5. Check the instance federation logs
   If you are an admin, go to Preferences > Administration > Federation > Log. Look for failed subscription requests. If a request failed with a timeout or reject error, the remote server may be temporarily unavailable or blocking your instance. Contact the remote server admin to resolve the block.

If Mastodon Still Has Issues After the Main Fix

Remote Timeline Shows Only Old Posts

If the remote timeline shows posts but they are all from before the instance change, the new instance has not yet received new updates from the remote server. This is a caching issue. Clear your browser cache and refresh the page. If the problem persists, use the manual pull method again with a very recent post URL.

New Instance Is Blocked by the Remote Server

Some remote servers block entire instances for moderation reasons. If you see no posts from a specific server at all, that server may have a domain block on your new instance. You can check this by visiting the remote server’s federation page (if public) or by asking a user on that server to check. If blocked, you cannot see posts from that server unless the block is removed. Consider using an alternative instance that is not blocked.

Federation Is Disabled on the New Instance

In rare cases, an instance admin may disable federation entirely. This stops all remote timeline updates. Check with your instance admin if federation is enabled. If it is disabled, the remote timeline will never update. You must move to another instance that allows federation.

Manual Trigger vs Automatic Subscription: Comparison

Item	Manual Trigger	Automatic Subscription
Method	Paste a remote post URL into search or follow a remote user	New instance discovers servers through other users’ follows over time
Speed	Immediate	Hours to days
Requires admin	No	No
Reliability	High	Low for specific servers

After your instance change, the remote timeline may appear frozen because server subscriptions do not transfer automatically. Using the manual pull method by pasting a remote post URL into the search bar triggers immediate federation. If you continue to see no updates, check for domain blocks on either side of the connection. For persistent issues, consider using the Preferences > Administration > Federation logs to diagnose failed subscriptions. This approach gives you control over which servers appear in your remote timeline without waiting for organic discovery.