Is TuneIn Down?

No — TuneIn is up

TuneIn's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 318 ms

Right now

The verdict is the worse of these two. How we decide

TuneIn's status page

status.tunein.com · read 2 minutes ago · checked every 3 minutes

Operational

TuneIn's components, as its status page reports them
Component	Status
Core	Operational
OPML	Operational
Feed	Operational
TuneIn Website	Operational
TuneIn Mobile	Operational
TuneIn Embedded Player	Operational
TuneIn on Smart Devices	Operational
TuneIn Content	Operational
Recurly API	Operational
AWS	Operational
Cloudflare DNS Root Servers	Operational
Cloudflare CDN/Cache	Operational

Open their status page

FlareWarden checks

api.tunein.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 318 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 273 ms
Chicago reachable, 236 ms
London reachable, 232 ms
San Jose reachable, 256 ms
Singapore reachable, 763 ms
Sydney reachable, 292 ms
Tokyo reachable, 319 ms
Toronto reachable, 175 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	70 ms	3 ms	9 ms	273 ms
Chicago	154 ms	4 ms	8 ms	236 ms
London	67 ms	3 ms	8 ms	231 ms
San Jose	185 ms	1 ms	11 ms	256 ms
Singapore	178 ms	1 ms	8 ms	763 ms
Sydney	115 ms	1 ms	5 ms	292 ms
Tokyo	195 ms	1 ms	6 ms	319 ms
Toronto	86 ms	1 ms	8 ms	175 ms

We check that api.tunein.com loads, not every feature behind it. Test it yourself

History

Incidents TuneIn reported

Since Oct 22, 3 days · from status.tunein.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

TuneIn website availability

Measured by FlareWarden · api.tunein.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 316ms

Last 30 days

71-day clean streak

Sep 25 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of api.tunein.com from multiple regions every 6 hours. TuneIn's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of TuneIn itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when TuneIn goes down

We check TuneIn every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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