Apple suffered a widespread outage on November 17, 2026, that disrupted iCloud sign-ins, the App Store, Apple Music and AppleCare on Device for users worldwide. Apple said an internal update, not a cyberattack, caused the disruption, and said most systems were restored while it continued fixing the rest.
What went down, and when
The disruption began in the early hours of November 17 and first showed up on Apple’s own System Status page as an “iCloud Account & Sign In” problem affecting all users. TechCrunch reported that users saw repeated sign-in prompts, failed login attempts, and in some cases could not activate new iPhones.
As the morning went on, Apple’s status page added more affected services: the App Store, AppleCare on Device, Apple Music, Apple School Manager, iCloud Mail, iCloud.com’s web apps, Schoolwork, and the Volume Purchase Program. The spread across so many services, rather than a single app, pointed to a shared account and authentication layer rather than one product failing on its own.
What Apple said caused it
Apple told TechCrunch that “an internal update caused some outages this morning,” ruling out a security breach or external attack. The company said many of the affected systems had already been restored and that it was working to bring the remaining ones back online through the day.
Apple did not say which internal system the update touched, or whether the fix required a rollback rather than a forward patch. For a company that routes almost every consumer-facing service, from app downloads to music streaming, through the same Apple ID sign-in layer, a single faulty update to that layer is enough to ripple across unrelated products at once.
Apple’s second sign-in failure this month
This is not Apple’s first Apple ID disruption in November. On November 10, Apple ID sign-in failed for users worldwide for roughly one hour and 46 minutes, blocking logins to iCloud, Game Center, Mail and App Store or iTunes purchases, according to outage-tracking service StatusGator. Apple acknowledged that incident on its status page about 19 minutes after the first user reports came in, and sign-in recovered within the hour that followed, though Apple never published a root-cause explanation for it.
Two Apple ID or sign-in-layer failures inside the same week raises the obvious question of whether the two incidents share a cause, something neither Apple’s status page nor its statement to TechCrunch has addressed directly. Apple has described the November 17 incident only as stemming from an unspecified internal update.
Why this outage is getting extra scrutiny
Beyond Apple’s own repeat incident, the outage lands in a short run of major cloud failures across the industry. It follows a roughly 18-hour Microsoft cloud outage on November 12 that spread from Outlook and Teams into Copilot, Defender and Intune, a brief Chase banking app outage, and a partial NSA classified network outage, all in the same two-week stretch. None of the recent incidents, including this one, has been publicly attributed to a cyberattack.
Taken together, the cluster of outages has renewed questions about how much of daily digital life, banking, work software, entertainment and even national-security infrastructure, now depends on a handful of large cloud and identity systems, where one bad internal change can cascade across products that otherwise have nothing to do with each other.
What to watch next
Apple has not said whether it will publish a fuller post-incident explanation once all services are confirmed stable, something it has done after past multi-service outages. Users who could not sign in or activate devices during the window should expect normal service once their region’s status entries clear on Apple’s System Status page.



Leave a Reply