Why Is My Scanner Feed Offline, Silent, or Delayed?

Updated July 24, 2026 · 5 min read

Feeds fail in a small number of recognisable ways. Working through them in order will usually identify the cause in under a minute.

1. The traffic is genuinely quiet

This is by far the most common explanation, and it is not a fault.

Radio traffic is bursty. A busy urban dispatch channel talks almost continuously; a rural county at 2am may go twenty minutes without a transmission. New listeners frequently assume silence means the app is broken.

How to check: open a large metropolitan feed. If that has traffic within a minute, your connection and the app are fine, and your local channel is simply quiet.

2. The volunteer's receiver is down

Every feed is one person's equipment in one physical location. Power cuts, internet outages, hardware failures, and holidays all take feeds offline. Some come back in minutes; some never do.

How to check: feed listings show listener counts. A feed with zero listeners where similar feeds have dozens is usually offline. Try a neighbouring county — coverage areas overlap more than you would expect, and an adjacent county's feed often carries the same regional and mutual-aid channels.

3. The agency encrypted its system

If a feed you followed for years went permanently silent or vanished, this is the likely reason. Encrypted transmissions cannot be received by any scanner, app, or software.

How to check: look for whether the location still has fire and EMS feeds while law enforcement has disappeared. That pattern is the signature of encryption, since agencies encrypt police traffic far more often than fire or EMS.

There is no workaround. See why police channels are encrypted for what remains available.

4. Buffering and delay

Some delay is inherent. The chain is: radio → receiver → encoder → streaming server → your device's buffer. A few seconds to about a minute is normal.

That buffer exists on purpose. Without it, every fluctuation in your connection would cause a dropout. Trading a few seconds of delay for uninterrupted audio is the right trade for a scanner.

When delay is a problem: if audio stutters repeatedly rather than staying consistently behind, that is a connection issue. Switching between Wi-Fi and cellular, or moving closer to your router, usually resolves it.

5. Your own connection

Worth ruling out early. Scanner streams are low bitrate and tolerate poor connections well, but they do not survive a captive portal — hotel and airport Wi-Fi that requires sign-in will silently block the stream while other apps appear to work.

How to check: load any web page. If that requires a sign-in, that is your answer.

6. Background playback stopped

If audio stops the moment you leave the app, this is a device setting rather than a feed problem. Check that Background App Refresh is enabled and that Low Power Mode is not suspending the app. Some battery-optimisation settings on Android are aggressive about stopping background audio.

A quick decision tree

1. Is a large metropolitan feed also silent? → your connection.
2. Does your feed show zero listeners while similar ones show many? → the feed is down; try a neighbouring county.
3. Have police feeds vanished while fire and EMS remain? → encryption; they are not coming back.
4. Does audio stutter rather than lag consistently? → connection quality.
5. Does audio stop only when you leave the app? → background settings.
6. None of the above, and it is a quiet hour in a small county? → nothing is wrong. Wait.

When to report it

If a feed is consistently dead for days while its neighbours are fine, it is worth reporting so it can be checked or delisted. A feed that is quiet at 3am on a Tuesday is working exactly as intended.

For choosing a feed likely to stay up, see how to listen on iPhone — county-level feeds carrying several agencies are both busier and more reliably maintained than single-department feeds.