Spotify outage July 27, 2026: Two-wave disruption hit 4,000+ users across US, Europe, and Latin America

How users were affected across regions and platforms

The outage was global in scope, striking in two distinct waves on Monday, July 27 .

First wave (early morning):

• Reports began around 5 AM ET, with over 700 Downdetector complaints by 9 AM ET .
• Affected regions included the United States, Colombia, Spain, and North Macedonia .
• Users saw the error message "Can't play this right now" on both the web player and desktop app, and experienced login failures and audio streaming glitches .

Second wave (afternoon):

• A new batch of issues hit shortly after 3 PM ET, after the first wave appeared to be resolved .
• Downdetector logged over 4,000 reports during this afternoon surge .
• 36% of reports cited problems with audio streaming, 43% with the Spotify app itself, 22% with the website, and 20% with the server connection .
• The term "Spotify can't play this right now PC" trended on Google .

Both the mobile app and web/desktop versions were affected , and the issue impacted free and paid users alike.

Pattern of disruptions via outage trackers

Downdetector recorded two clear spikes: a morning spike peaking at over 700 reports around 9 AM ET , and a much larger afternoon spike exceeding 4,000 reports . Users in New York, Los Angeles, Chicago, and Houston were among the heaviest-reporting U.S. cities . The pattern strongly suggests that an initial fix was deployed for the morning wave but either failed or was incomplete, allowing the same underlying issue to resurface by mid-afternoon .

Recent history of disruptions (May–July 2026)

This outage is the third major service interruption in roughly ten weeks:

The "fix that resurfaced"

The July 27 outage is the clearest example of a deployed fix that later appeared to fail. Spotify initially resolved the morning wave of issues, but users reported identical symptoms — playback failures, login problems, app glitches — hours later in the afternoon . This pattern suggests either:

• The original fix was incomplete or addressed only a symptom, not the root cause, or
• A separate but related backend issue triggered a second failure.

This recurring pattern stands in contrast to the May outage, which was a single continuous disruption lasting hours . The July 14 outage resolved very quickly (~20 minutes), while July 27's two-wave structure indicates a more stubborn or recurring problem .