Apple Music outage confirmed in multiple countries

Apple’s System Status pages for a dozen countries now list Apple Music as outage rather than the less severe “issue” label. The status reads:

• Some users are affected
• Intermittent issues may be experienced

In practice this means the service is still reachable for a subset of listeners, but a significant portion of the global user base is unable to stream or load their library.

Timeline and scope

• Start time: 11:40 a.m. ET (2026‑05‑29)
• Affected regions: Australia, Brazil, France, India, Italy, Japan, South Korea, Spain, United States, plus additional locales reported via Downdetector.
• Duration so far: Over an hour, with reports slowly declining on Downdetector as fixes are applied.
• History: This is the third Apple Music disruption in the last two months; a previous incident lasted more than a day and required a backend database migration.

What developers should watch

If your iOS or Android app integrates Apple Music APIs (e.g., MusicKit, StoreKit, or the Apple Music SDK), you may see:

1. Authentication failures – Users whose tokens are refreshed during the outage might receive HTTP 503 responses.
2. Playback errors – Calls to MPMusicPlayerController can return MPMusicPlaybackError with a network domain.
3. Catalog fetch problems – Requests to the Apple Music catalog endpoint (/v1/catalog/{storefront}/songs) may time out or return empty results.

For cross‑platform frameworks like React Native, Flutter, or Xamarin, the same HTTP status codes will surface through the respective networking layers. Consider adding a fallback UI that informs users of a temporary service disruption rather than showing a generic error.

Mitigation steps for app owners

1. Graceful degradation – Detect a 503/504 response and display a banner such as “Apple Music is currently experiencing issues. Your playback may be interrupted.”
2. Cache recent data – If you store recently fetched playlists or track metadata locally, serve that cache while the network is unstable.
3. Retry logic – Implement exponential back‑off for API calls instead of immediate retries, which can exacerbate load on Apple’s servers.
4. Monitor status pages – Apple provides a JSON endpoint for system status (https://www.apple.com/support/systemstatus/). Polling this endpoint lets you programmatically adjust UI elements.
5. Alternative sources – If your app offers multiple music providers (e.g., Spotify, YouTube Music), switch to a secondary source when Apple Music is down, assuming licensing permits.

When the outage resolves

• Check the status page – The “outage” label will change to “operational” and the description will be cleared.
• Validate API health – Run a quick health‑check request to the MusicKit endpoint and confirm a 200 response.
• Clear error states – Reset any UI flags you set during the incident so users return to the normal experience.

Community response

Users have reported the problem on platforms like Reddit, Twitter, and Downdetector. The volume of reports peaked within the first 30 minutes and is now tapering, suggesting Apple’s engineering team is actively addressing the root cause.

---

If you’re experiencing the issue, you can confirm it by visiting Apple’s System Status page for your region. Keep an eye on updates here, and consider adding the status‑check logic described above to future‑proof your app against similar incidents.