Spotify down on May 12, 2026: 7 hours, 30,000 Downdetector reports, no upstream named
Spotify reported an incident at 16:54 UTC on May 12. The fix took just over six hours. Downdetector peaked above 30,000 reports across mobile, desktop, and consoles.
Around 12pm Eastern on Tuesday May 12, Spotify started failing for tens of thousands of users at once. The app wouldn't open, the web player threw errors, search hung. Spotify acknowledged the issue 54 minutes later. The fix landed just after 11pm UTC, about seven hours after the first user reports.
Downdetector reports peaked above 30,000 (per Foreign Policy Journal), with mobile users carrying the bulk of the complaints. The outage touched every Spotify surface we know of: Android, iOS, the desktop app, the web player, and even console clients on PS5 and Xbox (TechRadar coverage). Heaviest geographic concentration was the US and UK, but the breakdown was global.
The timeline, condensed
Reports started showing up on Downdetector around 16:00 UTC. By 16:54 UTC Spotify had posted on their community board:
Hey everyone!
We've received some reports mentioning that the app, support site and the Web Player are slow or not working properly. This is being investigated.
On X / Twitter, the official @SpotifyStatus account went with a shorter version of the same message, telling users the team was "checking them out." The community thread title at the time read "Downtime May 12th, 2026: Some services are down."
Reports kept climbing for the next half hour or so, peaking somewhere between 14,000 (TechRadar's count at 17:20 UTC) and 30,000 (a later peak per Foreign Policy Journal). At 23:01 UTC, just over six hours after Spotify first acknowledged the issue, the community thread flipped to:
We're happy to say that this should now be fixed for everyone! Just make sure your app is updated to the latest version.
The status badge changed from "Under investigation" to "Fixed." No technical detail about what broke, no root cause analysis, no engineering blog post. The 11pm UTC fix-it announcement was the entire public postmortem.
What broke, by Spotify's own account
Three named surfaces:
- The app (Android, iOS, desktop)
- The web player at open.spotify.com
- The support site
Spotify's resolution note also asked users to "make sure your app is updated to the latest version," which is interesting. It suggests at least part of the fix involved a client-side change shipped during the incident window, not just a server-side rollback. That said, Spotify didn't say more, so the rest is reading tea leaves.
One quirk worth noting: several users reported that while music streaming was broken, Spotify's advertising system kept serving ads normally. Open the app, no music, but the audio ad slot loaded fine. That points at a partial-stack failure rather than a full outage. The catalog and recommendation paths were broken; the ad-fetch path wasn't.
No upstream blamed
This is the part where Pingoru can usually point at the upstream. Spotify's infrastructure runs heavily on Google Cloud (well-documented in their public engineering blog), with some AWS, Akamai, and Fastly in the mix. We checked every cloud-infrastructure provider that had a concurrent incident on May 12: AWS, Google Cloud, Azure, Cloudflare, Fastly. None of them had a major-impact incident overlapping Spotify's 16:00 to 23:01 UTC window in our database.
AWS did have a major EC2 incident in us-east-1 starting at 00:25 UTC on May 8 (four days earlier) that took out Datadog, Convex, Vercel, Hightouch, and others. It had fully resolved by May 10. Not this.
The honest summary: Spotify didn't blame anyone, and we couldn't find anyone to blame for them. This looks like a Spotify-internal incident. Whether it was a bad deploy, a backend service failure, a config push, or something else is information Spotify hasn't published.
How this fits into Spotify's recent record
Spotify's public status surface is now their community board, where every incident is a thread (they moved off the old Atlassian Statuspage recently). In our database, that board currently has 20 tracked threads. Of those, 10 are still marked active by Spotify and 10 have been moved to "Fixed" status. The full-platform downtime on May 12 is the only one in that set we classify as critical impact. The rest are feature-specific issues like Google Cast device detection, Family Plan signup, the iPad Now Playing view, or playlist sync glitches.
The previous critical-impact full-platform Spotify outage in our database was, by our records, almost two months ago. So this is a rare event for Spotify, not a chronic pattern.
The status-page situation, briefly
Spotify's choice to use a community forum thread as the public face of an outage is unusual. There's no JSON API, no machine-readable incident feed in the standard Atlassian / Statuspage / Statuspal shape. We tracked May 12 by reading the community board's RSS feed and parsing the thread's status badge directly from the HTML. It works, but if you're a Spotify partner or vendor with an internal dashboard, getting structured outage signal out of this is more work than it should be.
That's all there is to say about a Spotify outage that Spotify didn't say much about. Seven hours, 30,000 reports, no upstream cause, and a one-line "should be fixed for everyone" sign-off. If a fuller postmortem ever lands, we'll update this page.
Sources: