Spotify Outages in May 2026: May 18 Disruption vs. the Major May 12 Incident

• The mobile app
• The web player
• User logins and account access
• Library and playback functions

Users in the United States, the United Kingdom, and parts of Europe were among those most visibly affected, though the outage appeared to have global reach based on the distribution of complaints.

Hacker Group Claims Responsibility for the Earlier Incident

After the May 12 outage ended, a pro‑Iran hacker collective calling itself Islamic Cyber Resistance in Iraq – 313 Team claimed responsibility for the disruption. The group said it had carried out a distributed denial‑of‑service (DDoS) attack targeting Spotify’s servers.

DDoS attacks work by overwhelming servers with large volumes of traffic, preventing legitimate users from accessing services. According to reports citing the McCrary Institute for Cyber and Critical Infrastructure Security, the group described the operation as retaliation related to geopolitical tensions involving Iran.

However, the claim has not been independently confirmed by Spotify, and the company has not publicly attributed the outage to a cyberattack. Without confirmation from the platform or technical investigators, the hacker group’s statement remains an unverified claim.

What Happened During the May 18 Disruption

Less than a week later, users again reported problems accessing Spotify. On May 18, 2026, outage trackers recorded thousands of complaints, many tied to the mobile application.

Compared with the earlier outage, however, available metrics suggest the disruption was smaller:

• One monitoring site recorded 452 user reports in the previous 24 hours.
• Reports were concentrated primarily in North America, especially the United States and Canada.
• The problems appeared shorter‑lived and less globally widespread than the May 12 outage.

Users described familiar symptoms such as login issues, playback failures, or the app refusing to load content.

Spotify’s Silence and What It Means

Unlike the May 12 outage—where Spotify acknowledged the issue publicly while investigating—the company did not clearly explain the cause of the later May 18 disruption in the sources available.

That lack of explanation leaves several possibilities open:

• A routine infrastructure or software reliability issue
• A localized service failure affecting certain regions or systems
• A problem unrelated to the earlier incident

Importantly, there is no confirmed evidence linking the May 18 disruption to a cyberattack. While the earlier outage drew a DDoS claim from a hacker group, multiple outages close together do not automatically indicate coordinated attacks.

What the Two Incidents Reveal About Platform Reliability

The back‑to‑back disruptions highlight how even large streaming platforms can experience cascading service problems. When outages occur within days of each other, they can amplify user frustration and spark speculation about underlying causes.

Based on available reporting:

• May 12: A global outage lasting several hours with tens of thousands of user reports.
• May 18: A smaller disruption with hundreds to thousands of reports, mostly in North America.

Whether the earlier incident was truly a cyberattack—or simply a technical failure coincidentally claimed by hackers—remains unresolved. Without confirmation from Spotify or independent investigators, the most reliable conclusion is that the May 18 disruption was smaller, less widespread, and unexplained compared with the major outage six days earlier.

For users, the events underscore a simple reality of modern internet services: even globally distributed platforms can experience unexpected downtime, and the true cause is not always immediately visible from the outside.