Is TuneIn Down?

No — TuneIn is up

Reachable from all 8 checked regions

Average response time: 452ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.tunein.com

TuneIn uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

324ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 58 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

58-day clean streak

Sep 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax

166ms

DNS 105ms TCP 2ms TLS 8ms TTFB 166ms

lhr

334ms

DNS 153ms TCP 2ms TLS 11ms TTFB 334ms

nrt

470ms

DNS 350ms TCP 1ms TLS 6ms TTFB 470ms

ord

174ms

DNS 76ms TCP 2ms TLS 10ms TTFB 174ms

sin

1525ms

DNS 331ms TCP 1ms TLS 7ms TTFB 1525ms

sjc

174ms

DNS 98ms TCP 1ms TLS 6ms TTFB 174ms

syd

259ms

DNS 90ms TCP 1ms TLS 7ms TTFB 259ms

yyz

521ms

DNS 432ms TCP 1ms TLS 8ms TTFB 521ms

What TuneIn does

TuneIn streams live radio stations, sports commentary and podcasts through its website, mobile apps, an embeddable player and a long list of smart devices, from speakers and televisions to car head units. Much of its reach is through those integrations rather than its own app, so an outage is often noticed first as a speaker or dashboard radio that has stopped working.

What an outage looks like

Stations fail to start and the player sits buffering without ever playing. Smart speakers and car head units report that the station is unavailable while other audio sources on the same device work normally. The station directory will not load, so nothing can be browsed or searched even though a favourite may still play. Embedded players on third-party sites fail while the host page renders.

What to do about it

Check status.tunein.com, which separates the website, mobile, the embedded player, smart devices, content and the Core, OPML and Feed APIs. Its status page also lists third-party dependencies including AWS and Cloudflare, so check those entries before assuming the fault is TuneIn's own. If a single station fails while others play, that is the broadcaster's stream rather than TuneIn, and no amount of app troubleshooting will fix it.

Is it down for everyone, or just you?

If this page says TuneIn is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Plex

PBS

Dailymotion

Vimeo

TuneIn outage FAQ

Is TuneIn down or is it just one station?

Try two or three unrelated stations. TuneIn aggregates streams that broadcasters host themselves, so a single dead station is usually the broadcaster's own encoder or bandwidth rather than TuneIn, and it will fail on every app and device while everything else plays. A platform outage looks different: the directory will not load and nothing starts.

Why does TuneIn work in the app but not on my smart speaker?

TuneIn tracks smart devices as a separate status component from mobile and the website, so the split is expected rather than strange. Devices reach TuneIn through different integrations and often through the OPML API, which is listed on its own. If the app works and a speaker does not, the fault is in that integration path or in the speaker's own network setup.

Does a TuneIn outage affect the premium subscription I paid for?

Billing runs through a separate dependency: TuneIn lists the Recurly API among the third-party services on its status page. That means a payment or subscription problem can occur without any streaming fault, and streaming can fail while billing is fine. An outage does not consume subscription time in any meaningful sense, but a persistent entitlement failure is worth raising with support rather than waiting out.

Is the problem TuneIn or its upstream providers?

TuneIn's status page answers this directly by listing AWS, Cloudflare DNS Root Servers and Cloudflare CDN and Cache as tracked third-party dependencies. A broad Cloudflare or AWS incident will show there and will also be affecting many unrelated services at the same time. Checking whether other sites are struggling is a fast way to tell an upstream event from a TuneIn-specific one.

How we measure this

We request TuneIn's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where TuneIn publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when TuneIn goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required