Key Points
Spotify outage began 9:30 a.m. ET on September 29, peaking at 19,000 reports by 10:12 a.m.
Over 200,000 outage reports worldwide from 173 countries, with 46% from the US.
Search and login functions most impacted; playback of downloaded music largely unaffected.
Service recovered by 2 p.m. ET; Spotify cited no cause, hinting at app update issue.
Spotify went down for thousands of users on Tuesday morning, September 29, with more than 19,000 reporting problems by 10:12 a.m. ET. Users faced login errors, search failures, and “Something went wrong” messages across mobile and desktop. The service recovered within hours, though Spotify has not explained what caused the disruption. The outage also coincided with problems at Anthropic’s Claude AI platform.
What happened during the Spotify outage
The Spotify outage began around 9:30 a.m. ET on September 29, with reports spiking to 3,000 per minute at peak around 10:41 a.m., according to Downdetector. Over 200,000 reports came in worldwide, including more than 100,000 from the US alone by 11:15 a.m. ET. Reports came from 173 countries, with about 46% originating in the US across all major mobile and home broadband providers.
Users reported varied issues. About 58% of complaints involved app problems, while 21% reported audio streaming failures. Some users could play downloaded music but could not search for new tracks or access playlists. Others reported being logged out and unable to sign back in. Spotify acknowledged the issue on its status page, stating it was aware and investigating, but provided no details on the cause.
Which features were most affected
Search and login functions bore the brunt of the outage. Spotify’s support team advised users to try the web player as a workaround and to enable automatic app updates, suggesting a faulty app update may have triggered the problem. Spotify Connect, which lets users control playback across devices, was also impacted.
Playback of already-loaded music was least affected. Users who had songs or playlists downloaded to their device could often continue listening. The partial nature of the outage meant impact varied by user and device.
Timeline and recovery
Reports peaked at more than 19,000 around 10:12 a.m. ET before falling steadily. By 12:15 p.m. ET, Downdetector showed reports dropping below 1,000. By 2 p.m. ET, reports had fallen to 651, and by late afternoon most users reported service restored. Spotify’s main X account posted around 1 p.m. ET that it was “actively working to resolve” issues, but offered no estimated time for a full fix.
Anthropic’s Claude AI platform experienced a concurrent outage, with over 11,000 reports peaking around 10:25 a.m. ET before dropping to fewer than 100. Both services recovered without further incident by mid-afternoon.
What this means for Spotify investors
The outage lasted roughly 3 hours and affected a fraction of Spotify’s 600 million global users. No data breach or security incident was reported. Spotify stock (SPOT) showed no significant reaction to the disruption, as brief service outages are common in cloud-based platforms and typically do not move the needle for long-term investors. The lack of transparency on the root cause may draw scrutiny from enterprise customers, but recovery speed and absence of data loss limit reputational damage.
Final Thoughts
Spotify’s September 29 outage was brief and contained, with service restored within hours. While the company’s silence on the cause raises questions, the quick recovery and lack of security concerns limit investor risk. Monitor for any pattern of recurring outages.
FAQs
Over 19,000 users reported issues to Downdetector in the US by 10:12 a.m. ET. Over 200,000 reports came in worldwide from 173 countries.
Spotify did not disclose the root cause. Support staff hinted at a faulty app update, advising users to enable automatic updates. The exact trigger remains unconfirmed.
Some users could play downloaded songs or playlists but could not search for new music or log in. Search and login functions were most affected.
Service began recovering around 12:15 p.m. ET, with most users reporting normal operation by 2 p.m. ET. The outage lasted approximately 3 hours.
Disclaimer:
The content shared by Meyka AI PTY LTD is solely for research and informational purposes. Meyka is not a financial advisory service, and the information provided should not be considered investment or trading advice.
About Author

Danny Kontos
Co FounderDanny Kontos has been a stock investor since 2007 and co-founded Meyka in 2023. He keeps a small, focused portfolio and only moves when the numbers are hard to argue with. He has waited years on a single position before. Before Meyka, he ran a web hosting company and a mortgage lending platform, so he knows what a well-run business actually looks like under the hood. This article did not come from a news cycle. It came from someone who has been watching this space for a long time.
What brings you to Meyka?
Pick what interests you most and we will get you started.
I'm here to read news
Find more articles like this one
I'm here to research stocks
Ask Meyka Analyst about any stock
I'm here to track my Portfolio
Get daily updates and alerts (coming March 2026)