Apple outage history

Apple's status page indicated a partial disruption to Apple Cash, impacting purchases. Users reported declines, pending transactions, or funds deducted without completing the purchase. The issue began at Sep 16, 2026 10:52 PM UTC and affected multiple regions through the night as activity and complaints grew. The official update described the problem as: 'Some users may be experiencing issues making purchases using Apple Cash.'

Apple Cash moved from warn back to up at Sep 17, 2026 12:57 AM UTC, signaling recovery. The disruption appeared isolated to Apple Cash payments, with other Apple Pay functionality returning to normal after the fix.

Apple's Subscription Purchase component faced a brief outage affecting purchase and sign-up flows for a short window. The official status changes show it moved from up to down at 1:12 PM UTC and returned to up at 1:27 PM UTC, with the page indicating the service may be slow or unavailable during the incident. The disruption lasted roughly fifteen minutes, and user reports—including a note from Barcelona at 1:14 PM UTC—suggest customers experienced errors or delays when attempting subscriptions within that window.

Users attempting to purchase or manage subscriptions on Apple may have encountered intermittent issues during a short window. Apple’s status page indicated a problem with the Subscription Purchase component, moving from up to warn at 9:27 PM UTC with the message 'Users may be experiencing intermittent issues with this service.' The issue appeared to be brief and was resolved by 10:22 PM UTC. This suggests sporadic failures or delays in the subscription workflow, before service returned to normal.

Apple Maps faced a brief disruption as the Maps Display component entered a degraded state. The issue began around 1:32 AM UTC after Apple indicated an investigation into problems with Maps. Users likely experienced map rendering issues and related features during this period, before updates confirmed the investigation and remediation.

The incident was resolved around 2:07 AM UTC when the Maps Display component returned to normal. The reports were limited, and Apple’s status page described the investigation and subsequent restoration as services returned to normal.

Apple experienced a brief outage that affected all services, with the Volume Purchase Program listed as the impacted component. Users faced service interruptions during the outage window while Apple investigated the issue. The outage began at 9:07 PM UTC and was resolved by 9:32 PM UTC.

According to Apple's System Status page, the Volume Purchase Program transitioned from down to up at 9:32 PM UTC as services returned to normal. The incident appeared to be short in duration but impacted a broad set of Apple services during the window, with a small number of user reports noting the disruption.

An outage affected Apple iWork Collaboration, limiting real-time co-authoring across iWork documents. The issue began at 12:57 AM UTC and disrupted collaboration for a subset of users until 2:02 AM UTC. During the incident, users reported difficulties with joint editing and occasional connectivity issues while working on shared documents. Apple’s System Status page indicated that some users were experiencing issues with iWork Collaboration, and the component moved from up to down before returning to normal later that day. A small number of user reports, including at least one from Hayward, California, reflected these symptoms.

Globally, users experienced iCloud issues beginning around Aug 18, 2026 7:40 PM UTC with iCloud Mail not loading or showing errors. StatusGator detected the Early Warning Signal roughly 41 minutes before Apple acknowledged the problem, which started at 8:22 PM UTC. Apple’s status page listed a degraded experience for multiple components, including Game Center, Photos, iWork for iCloud, iCloud Mail, iCloud Calendar, iCloud Contacts, iCloud Web Apps (iCloud.com), and iCloud Account & Sign In; later the Find My service was also noted as degraded. The issue affected users globally across these services.

Over the next several hours, most services returned to normal; by 9:57 PM UTC the majority of components were up again, with Find My fully recovered by 10:32 PM UTC. The incident lasted several hours and a broad set of iCloud features experienced degraded performance during the window.

Users experienced degraded Apple Music features beginning around 5:30 AM UTC, with library sync failures, playback problems, and unresponsive Apple Music apps reported across several regions. The issue was acknowledged on Aug 11, 2026 6:17 AM UTC as a music service issue affecting Apple Music, and the service gradually improved through the day, returning to normal by Aug 11, 2026 5:07 PM UTC.

Status page updates described the progression of the incident: the Apple Music component moved to a degraded state at Aug 11, 2026 6:17 AM UTC and then recovered by Aug 11, 2026 5:07 PM UTC. The impact was felt by users across multiple regions, including the United States, the United Kingdom, Greece, and Venezuela, with experiences ranging from library sync failures and playback errors to unresponsive Apple Music apps.

An Apple App Store outage affected a subset of users starting at 5:17 PM UTC. The Apple status page indicated that some users may be experiencing issues with this service, likely causing errors when launching, browsing, or downloading apps. The disruption appeared to be limited in scope and short in duration, with many users experiencing normal access during the event.

The issue was resolved later the same day, as the App Store moved from down back to up by 6:02 PM UTC. Apple indicated the service had returned to normal after the outage, and no extended impact to other Apple services was reported.

Apple's Stocks app stopped updating price data and charts for several hours, leaving users with frozen prices and missing graphs. Impact began around 1:26 PM UTC when the Stocks data stopped updating, and Apple acknowledged a degraded Stocks service at 4:07 PM UTC. The issue was resolved with a return to normal operation by 5:52 PM UTC. StatusGator detected the issue about 1:26 PM UTC and noted an early warning lead time of roughly 2 hours and 41 minutes before the official acknowledgment.