Incident sheet · /infrastructure

Filed
Read
3 min · 583 words
Severity
Routine

Apple Outage Hit iCloud, App Store and Retail for Six Hours

An internal update, not a hack, took down iCloud, Apple Pay, the App Store and Apple retail for six hours, capping a week that also hit Microsoft 365, US flights and JPMorgan Chase.

Security, security, security: What a week of outages means to IT (and you)
FeedSecurity, security, security: What a week of outages means to IT (and you) — Zulfugar Karimov / unsplash

Event log

  1. Apple services failed from about 11:45 a.m. ET to about 6 p.m. ET on November 17.
  2. Apple attributed the outage to an internal update and ruled out a cyberattack.
  3. Microsoft 365 was down for 24 hours on November 12-13.
  4. The FAA grounded US flights for more than four hours on November 13.
  5. Attackers launched credential phishing campaigns exploiting the Microsoft 365 outage.

Apple restored its services in roughly six hours on November 17 after an internal update knocked out iCloud sign-in and backups, Apple Pay, the App Store, Apple Support, App Store Connect, Xcode Cloud and internal corporate tools including AppleWeb. The company said the disruption was not a cyberattack and gave no indication that personal data was at risk. First reports arrived at about 11:45 a.m. ET; full restoration came at about 6 p.m. ET.

The failure closed out a week of severe availability problems across major platforms. Microsoft 365 services were down for what many administrators called an unacceptable 24 hours on November 12-13. The FAA grounded US flights for more than four hours on November 13 because of network equipment outages. A JPMorgan Chase outage rippled through the financial system, United Airlines suffered a widespread system outage, and the US National Security Agency's classified internal network went down. Officials say the incidents were not connected beyond temporal proximity.

What did the Apple outage actually hit?

The incident spanned consumer, enterprise and developer services.

  • iCloud sign-in and backups failed.
  • Apple Pay and the App Store went down.
  • App Store Connect and Xcode Cloud broke, blocking developer workflows.
  • Internal tools including AppleWeb failed.
  • Physical Apple Store retail operations were hobbled, disrupting sales, customer pickups and device repairs.
  • Users reported device management onboarding was briefly out of action and errors setting up new iPhones.

As of the following morning, DownDetector showed Apple's services working normally, though the developer services page still listed an App Store Connect outage.

Was it a hack?

Apple told NBC News an internal update caused the disruption. The company said nothing beyond that. "Many of our systems are back up and running after an internal update caused some outages this morning," Apple said. "We're working to get the remaining systems online as soon as possible."

Nobody outside Apple knows what failed, why the update generated what could be multiple failures across systems with their own infrastructure, or why the problem was not caught in staging or contained within a staged rollout. Apple has not said whether it will publish a post-incident report (a formal root-cause disclosure issued after a failure), which is the only route to answers.

Why does a shared layer matter?

The pattern points to a shared dependency. Sign-in, payments, developer authentication and internal staff tools all rely on authorization, so a fault at that layer could take down services with otherwise unrelated back ends. A fix applied to a shared layer would fit recovery by close of business, but so would a rollback of the update. The cascading failure shows how much businesses and end users depend on digital infrastructure and how any single-layer failure threatens both.

What should IT leaders do now?

Two of the world's leading platform providers took serious outages within one week. The practical response for IT departments is concrete.

  • Identify which critical processes depend on a single provider.
  • Maintain a recovery path that does not run through that provider.
  • Distrust unexpected "fix it" messages; attackers exploited the Microsoft 365 outage with credential phishing campaigns.
  • Instruct staff locked out of services not to use unsanctioned tools or share credentials.
  • Direct staff to wait for resolution or use a sanctioned fallback where one exists.

The safe conclusions are these: an internal change broke something shared, personal data appears unaffected, and the rest remains unknown unless Apple publishes a post-incident report.

via techcrunch.com (Original)

Filed under

  • apple-outage
  • cloud-resilience
  • shared-dependencies
  • service-availability
  • post-incident-review
Share this article:

More from Rebecca Stone

Rebecca Stone

Show full bio

Senior reporter covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

199 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›