
Photo: Chris Olszewski, 2025, via Wikimedia Commons (CC BY-SA 4.0)
Short answer: on Tuesday, November 17, 2026, an internal software update at Apple knocked out iCloud sign-in, the App Store, AppleCare purchases, school and business tools, developer services and the company’s own store and office systems for several hours. Apple says it was not a cyberattack, and consumer services were back by mid-afternoon Pacific time. One developer tool, App Store Connect, was still listed as down the next morning.
If your iPhone suddenly signed you out of iCloud, an app download spun forever or Apple Pay failed at a register on Tuesday, the problem was on Apple’s side. Apple’s own status pages, which log every incident with start and end times, show the trouble beginning shortly after 8 a.m. Pacific and spreading to 17 services across its consumer and developer pages before it was contained. It came a week after a separate iCloud outage that also hit sign-in, and it landed in a week when several other big U.S. systems had already gone down.
Here is what broke and for how long, what Apple has and has not said, why a single update can reach so much, and what to check on your own devices now.
What broke, and for how long
All times below are from Apple’s System Status and Developer System Status pages, converted to Pacific time. Apple’s page records when its engineers flagged and cleared each problem, which can trail what users see. 9to5Mac reported that the status page still showed services as available while Downdetector complaints were climbing.
On your iPhone, iPad and Mac
AppleCare on Device: the first entry, from 8:15 a.m. to 12:39 p.m. Apple listed it as an outage for all users and said "AppleCare purchase was temporarily unavailable."
iCloud Account and Sign In: slow or unavailable for some users from 8:45 a.m. to 1:15 p.m. This was the failure most people felt. 9to5Mac relayed reports of iPhones and Macs unexpectedly signing out of iCloud, then failing verification or showing unknown errors when owners tried to sign back in.
App Store: an outage for some users from 8:45 a.m. to noon. People reported apps that would not load or download. iCloud Mail and iCloud.com were also flagged as slow or unavailable starting at 8:45 a.m.
Apple Pay, Apple Music and activation: these were not logged as incidents on Apple’s page, but user reports were heavy. Reuters counted about 2,300 Downdetector reports for Apple Pay in the U.S. around 9:20 a.m. Pacific, more than the roughly 1,800 at the peak for iCloud. MacRumors reported that people setting up a new iPhone could see an "Unable to Activate" error. Downdetector counts are user reports, not verified outages, so they show where people noticed problems rather than how many were affected.
In Apple Stores and inside Apple
The outage did not stop at customers. At Apple Stores in New York and Chicago, employees told NBC News that their internal software had stopped working and that they could not complete purchases or book appointments. Bloomberg reported that the employee portal AppleWeb, the internal sign-in system AppleConnect and VPN access for remote workers went down, that staff could not download internal software builds, open company calendars or book meeting rooms, and that even the internal site that tracks outages was unavailable. Stores around the world were affected, disrupting sales, repairs and customer service, according to the same report.
For schools, businesses and developers
Apple Business, Apple School Manager and Schoolwork: slow or unavailable for some users from 10:40 a.m. to 2 p.m. These are the tools schools and companies use to set up and manage fleets of iPads and Macs. The Volume Purchase Program, which they use to buy apps in bulk, logged an outage from 8:45 a.m. to noon.
Developer services: Xcode Cloud was down for all users from 9 a.m. to 1 p.m., with lingering issues until 2:30 p.m. The Developer ID notary service, which Mac developers need to ship apps outside the App Store, logged an outage from 8:25 a.m. to 4:10 p.m. App Store Connect Analytics, Sales and Trends, Apple Music Connect and Apple Music for Artists were out from 9 a.m. to 4 p.m.
App Store Connect: the portal developers use to submit and manage apps logged two outages, starting at 8:50 a.m. and 10:57 a.m. on Tuesday. As of 8:55 a.m. Pacific on Wednesday, November 18, Apple’s developer page still listed both as ongoing, with "All users are affected." The subscription platform RevenueCat said late Tuesday afternoon that App Store Connect was recovering and that some requests might still fail, adding that the problem did not affect purchases or subscriptions inside apps.
What Apple said
Apple gave the same short statement to several outlets, including Bloomberg, NBC News and Engadget, by late Tuesday morning Pacific time:
Many of our systems are back up and running after an internal update caused some outages this morning. We’re working to get the remaining systems online as soon as possible. (Apple spokesperson, Nov. 17, 2026)
The company also said the outage was not caused by a cyberattack. Later, a spokesperson told CBS News that its services were "green across the board," a reference to the colored dots on the status page, as of about 2:46 p.m. Pacific. NBC News reported that the status page showed no outages by 3 p.m. Pacific.
That is the whole of Apple’s public explanation so far. It has not said which update it was, which system it changed or why the failure spread from consumers to stores to its own employees.
Why one internal update can take down so much
The pattern of what failed points to one shared layer: identity. Your Apple Account, formerly called Apple ID, is the login behind iCloud, App Store purchases, Apple Pay setup, AppleCare and device activation. Sign in with Apple, introduced in 2019, extends the same account to apps from other companies. Apple’s employees use their own Apple credentials, through AppleConnect, to reach internal tools. When the system that checks who you are stops answering, everything that asks it a question stalls at once. The servers behind each service can be perfectly healthy and still be unreachable.

Photo: Nils Huenerfuerst, 2024, via Wikimedia Commons (CC0)
That is a guess from the outside, not something Apple has confirmed. But it fits the details. The complaints clustered around the moments when a device has to check an account: signing in, paying, downloading an app, activating a new phone or buying AppleCare. It would also explain why being signed out was the worst outcome: a phone that had already signed in kept going until it was forced to ask again.
When the system that checks who you are stops answering, everything that asks it a question stalls at once.
Big services roll out changes in stages so a bad update hits a small slice of users first. Apple has not said whether this one was staged or how quickly it was rolled back. The timing on its own pages suggests the consumer side was repaired within about four to five hours, while some developer tools took far longer.
Was it a hack, and is it connected to the other outages?
Apple says no to the first question. On the second, nobody has shown a link. The Apple outage followed a run of unrelated failures: a nearly 24-hour Microsoft 365 outage that began on November 12, a nationwide air-traffic ground stop on November 13, and United Airlines and JPMorgan Chase problems on November 16. Each was described separately by the company or agency involved, and Reuters noted that companies and officials have said none were linked to cyberattacks. We covered the bank failure, and what caused the Microsoft and FAA failures, in our explainer on the Chase outage.
What the week shows is how much ordinary life now runs through a few huge, tightly coupled systems. A routine change in one place can stop payments, logins and store checkouts in thousands of others. Real intrusions tend to look different: they are usually quiet, targeted and discovered later, as in the recent wave of attacks run by AI hacking agents, not a loud, all-at-once failure followed by a fix the same afternoon.
What to do now
I was signed out of iCloud. What should I do?
Sign back in from Settings, then tap your name. Apple’s status page now lists iCloud Account and Sign In as available, so a normal sign-in should work. If it still fails, check the status page first, make sure your device is on current software, and try again on Wi-Fi. Do not reset your password just to make an outage prompt go away; that adds a step without fixing anything on Apple’s side. After you are back in, open Photos, Notes and iCloud Drive and give them time to finish syncing before you delete anything.
Did my Apple Pay purchase go through?
Check the Wallet app’s transaction list and your bank or card app. A payment that failed at the terminal usually does not post. If you see a charge for something you did not receive, or two charges for one purchase, contact the merchant or your card issuer, since Apple Pay passes the payment to your card rather than holding the money itself.
Was I charged for an app that never downloaded?
Open your purchase history at reportaproblem.apple.com or in the App Store under your account. If a purchase never arrived, you can request a refund there: choose "Request a refund," pick a reason and the item, then submit. Apple says to expect an update within 24 to 48 hours.
My new iPhone said Unable to Activate
Activation depends on reaching Apple’s servers. Check that iOS Device Activation shows as available on the status page, restart the phone and try again on a stable Wi-Fi network. If your phone is stuck after setup has worked for others, Apple Support or an Apple Store can help.
I tried to buy AppleCare on my iPhone and could not
You still have time. Apple says you can buy an AppleCare plan within 60 days of buying your iPhone, from Settings, then General, then About. If you are past that window because of the outage day, keep a note of when you tried and ask Apple Support.
I am a developer and App Store Connect still fails
Watch Apple’s Developer System Status page rather than retrying uploads in a loop. RevenueCat’s note suggests that purchases and subscriptions in shipped apps kept working. Expect delays for anything that edits products, submits builds or pulls sales data until Apple marks the outages resolved.
How do I keep my files safe next time?
Keep a local copy of what matters. iCloud is a sync service, so a sign-out or a sync glitch can make files look missing even when they are safe on Apple’s servers. A Mac can back up to an external drive with Time Machine, and an iPhone can be backed up to a computer. A second way to sign in also helps: Apple lets you add physical security keys and recovery contacts to your account, which makes it easier to get back in if something goes wrong.
Apple has been here before
November 10, 2026: a week earlier, Apple’s status page logged a separate outage from 2:49 to 4:22 p.m. Pacific that hit iCloud Mail, Calendar, Contacts, Photos, iCloud sign-in, iWork for iCloud and Game Center, with Find My slow or unavailable until 4:54 p.m. Apple did not give a cause.
March 11, 2015: the iTunes Store, App Store and related stores were down worldwide for about 12 hours. Apple blamed an "internal DNS error," a fault in the system that turns web addresses into server locations.
Outages this broad are uncommon for Apple, which is one reason Tuesday drew so much attention. Most of its incidents are short, partial and fixed before most people notice.
What Apple still has not explained
Which update, and what it touched. Apple has said only "an internal update." It has not named the system or the change.
Why the status page lagged. Several outlets noted that services were still shown as available while reports were climbing.
Why Apple Pay was never listed. By Reuters’ count, Apple Pay drew more Downdetector reports than iCloud, yet the status page never logged an incident for it.
Whether November 10 and November 17 are related. Both hit iCloud sign-in. Apple has not said whether they share a cause.
When App Store Connect will be fully back. It was still listed as down about 24 hours after the first outage began.
Bottom line
Apple’s November 17 outage was self-inflicted, not an attack, and most customers were back within a few hours. The lesson is less about Apple than about how much rides on one account: when sign-in fails, payments, downloads, stores and even the people trying to fix it can stall together. Sign back in, check your purchases and payments, and keep a local backup of anything you cannot afford to lose.
Further reading

Samsung T7 Portable SSD (1TB)
A pocket-size USB-C drive that works with Time Machine on a Mac, so a local copy of your files does not depend on signing in to iCloud.

Seagate Portable 2TB External Hard Drive
A low-cost plug-in drive with room for a Mac backup or a second copy of your photo library.

Apple AirTag (4 Pack)
Apple’s trackers for keys, bags and luggage, located through the Find My network that was slow during the November 10 outage.

Site Reliability Engineering: How Google Runs Production Systems
Google engineers explain staged rollouts, error budgets and postmortems, the practices meant to stop one bad change from becoming an outage.

Release It! Design and Deploy Production-Ready Software
Michael Nygard’s field guide to how big systems fail in cascades, and the patterns that keep one failure from taking everything else down.
