Mastodon Federated Timeline Not Updating: Diagnostic Steps

When your Mastodon federated timeline stops showing new posts from other instances, the experience feels like the network has gone silent. This problem usually stems from a connectivity disruption between your home server and remote instances, a stalled background refresh process, or a local caching issue. This article explains the root causes of a frozen federated timeline and provides a clear set of diagnostic steps to restore normal activity.

Why the Federated Timeline Stops Receiving New Posts

The federated timeline displays public posts from all instances that your home server knows about. Your server receives these posts through a background job system called Sidekiq. When Sidekiq stalls or runs out of memory, new remote posts cannot be processed and the timeline appears frozen.

Another common cause is a network-level block. If your server’s IP address has been rate-limited by a large remote instance, or if your server is running a firewall rule that restricts outbound connections to ActivityPub endpoints, the federation handshake fails silently. The timeline then shows only older cached content.

A third cause is a corrupted local cache of remote instances. Mastodon stores instance metadata and public keys locally. If this cache becomes stale or corrupted, your server may reject new posts from previously trusted instances. Clearing the cache forces your server to re-fetch instance information.

Diagnostic Steps to Restore the Federated Timeline

Follow these steps in order. Each step isolates a specific layer of the problem. Stop when the timeline begins updating again.

1. Force a hard page reload
   Press Ctrl+F5 on Windows or Cmd+Shift+R on Mac. This bypasses your browser cache and fetches the latest page data from the server. If the timeline updates after this step, the issue was a stale local cache.
2. Check the home timeline for recent posts
   Click the house icon to view your home timeline. If you see new posts from people you follow, your account and server connection are working. The problem is limited to the federated timeline and is likely server-side.
3. Test with a different Mastodon client
   Open the same federated timeline in a different app, such as Tusky on Android or Ivory on iOS. If the timeline updates there but not in the web interface, the issue is browser-specific. Clear cookies and site data for your instance domain.
4. Verify server connectivity from an external tool
   Use a service like Mastodon Instance Checker (mastodon-checker.glitch.me) to see if your instance is reachable from the public internet. Enter your instance domain. If the check fails, your server may be behind a firewall or experiencing a DNS outage.
5. Inspect Sidekiq queue health
   Navigate to Preferences > Administration > Sidekiq (or go directly to /admin/sidekiq on your instance). Look at the Busy and Enqueued numbers. If the Busy count is at the maximum allowed workers, or if the Enqueued count for the pull queue is above 1000, the server is overloaded. Restart Sidekiq from the server terminal: sudo systemctl restart mastodon-sidekiq.
6. Clear the instance cache
   If Sidekiq is healthy but the timeline still shows no new posts, clear the remote instance cache. Run this command on your server: RAILS_ENV=production bin/tootctl cache clear. This removes cached instance metadata and forces Mastodon to re-fetch remote data. After the command completes, wait 5 minutes and refresh the federated timeline.
7. Check for outbound connection blocks
   If your server is behind a corporate firewall or a VPN, outbound connections to ports 80 and 443 on remote servers may be restricted. Run a test from the server terminal: curl -I https://mastodon.social. If the command returns no response, your network is blocking outbound HTTPS. Contact your hosting provider or network administrator.

If Mastodon Still Shows a Frozen Federated Timeline

The timeline shows only posts from one or two instances

This indicates that your server has been partially blocked by other instances. Check if your instance appears on any community blocklists, such as the oliphant.social blocklist or spam.blocklist. If your instance is listed, the admin must contact the list maintainer to request removal.

The timeline updates after a server restart but stops again within an hour

This pattern points to a memory leak in Sidekiq or the web process. Check memory usage from the server terminal with htop. If the mastodon-web or mastodon-sidekiq processes consume more than 1 GB of RAM each, increase the server memory or reduce the number of Sidekiq workers. Edit .env.production and lower the SIDEKIQ_CONCURRENCY value to 5.

The federated timeline works on mobile data but not on Wi-Fi

Your Wi-Fi network may be blocking ActivityPub traffic. Some public Wi-Fi networks block peer-to-peer protocols. Use a VPN on your device to bypass the restriction. If the timeline updates with the VPN active, the Wi-Fi network is the cause.

Mastodon Timeline Diagnostic Tools Comparison

Item	Browser Cache Refresh	Sidekiq Dashboard	Server Terminal Commands
Best for	Quick client-side check	Server-side job queue analysis	Deep cache and network diagnostics
Time to complete	10 seconds	2 minutes	10 to 30 minutes
Requires server access	No	No (admin panel)	Yes
Fixes stale cache	Yes	No	Yes
Fixes overloaded Sidekiq	No	Yes (identifies the issue)	Yes (restart or reconfigure)

Use the browser cache refresh as your first step. If that does not help, move to the Sidekiq dashboard. Only use server terminal commands when the first two methods show no problem.

You can now diagnose a frozen federated timeline by checking browser cache, Sidekiq queue health, and server connectivity in that order. Start with the hard reload and the home timeline test. If those pass, move to the Sidekiq dashboard at /admin/sidekiq. An advanced tip: set up a monitoring alert on the Sidekiq pull queue using a tool like Uptime Kuma so you are notified before the timeline stops updating again.