Spotify went down for a large number of users starting around 9:30 AM ET on September 29, Android Authority reported, in one of the service’s broader outages this year.
What broke for users
Reports on Downdetector started around 3,500 and climbed past 19,000 at the outage’s peak. Affected users described slow performance, an inability to access their profiles or play music, unexpected logouts on both web and mobile, broken search, and a generic error message reading “Something went wrong. Have another go?” That combination, logins failing alongside playback and search, pointed to a problem somewhere in Spotify’s core backend rather than a glitch in one specific feature.
A recovery that took a few hours, not days
By 1:07 PM ET, roughly three and a half hours after the first reports, Spotify was working again for most users, though more than 1,000 reports were still coming in even after the broader recovery. That timeline puts this outage on the longer end for a major streaming service, long enough to be genuinely disruptive during a weekday morning, but short enough that it was resolved well within the same day.
What’s still unknown
Spotify hasn’t published any statement explaining what caused the outage or detailing what its engineers did to fix it, and no official cause has surfaced through other reporting either. That silence isn’t unusual immediately after an outage, but it does mean the only information available right now comes from user reports on Downdetector and social media rather than anything confirmed by the company itself.
Why a few hours of downtime still matters
Spotify’s scale is exactly why a three and a half hour outage gets attention that a smaller app’s downtime wouldn’t. With hundreds of millions of users relying on it daily for music, podcasts, and increasingly audiobooks, even a morning-long disruption affects a meaningful slice of people trying to work, commute, or just get through their day with sound in their ears, which is likely why the story spread quickly across tech outlets while the outage was still ongoing.
Source: Android Authority