Back
Apple Outage, November 17 2026: Why iCloud, the App Store and Apple Pay Broke at Once
An internal update knocked out iCloud sign in, AppleCare purchases, parts of the App Store and even the registers inside Apple Stores for most of a Tuesday. Here's what Apple confirmed, where the reports disagree, and what it means if your own business leans on Apple.

Jagdish Patil
•
Incident Overview (TL;DR)
What failed: iCloud account sign in, AppleCare on Device purchases, parts of the App Store, Apple Music, iCloud Mail and web apps, Apple Business Manager and Apple School Manager, plus several developer services. Users also reported Apple Pay and Apple Support failures.
When it started: Tuesday, November 17, 2026. Apple’s System Status page flagged AppleCare at 11:15 a.m. ET (16:15 UTC), per TIME. Downdetector reports climbed from about 11:30 a.m. ET (16:30 UTC).
Where: Reports were concentrated in the US, the market every outlet we read was tracking.
Peak reports: About 2,000 Downdetector reports each for Apple Support, Apple Pay and iCloud just before 1 p.m. ET, according to TIME. Bright Defense, citing Reuters, put iCloud at roughly 1,800 US reports at peak.
Confirmed cause: An “internal update,” per an Apple spokesperson. Apple also said it was not a cyberattack.
Status: Resolved. Most consumer services were back by midafternoon ET, and CBS News reported every indicator green by about 5:46 p.m. ET (22:46 UTC). Apple hasn’t published an incident report.
What Happened
Apple runs a public System Status page and a separate one for developers. Based on what outlets captured from those pages during the day, Apple itself listed problems with AppleCare on Device (“temporarily unavailable”), iCloud account and sign in (“may be slow or unavailable”), the App Store, Apple Music, iCloud Mail and iCloud web apps, Apple Business, Apple School Manager and Schoolwork. On the developer side, Tom’s Guide logged App Store Connect, Xcode Cloud, In App Purchases and Apple Podcasts entries.
Then there’s the list Apple never posted. Apple Pay shows up in every outlet’s coverage, but only as a Downdetector complaint, not as a status page entry anyone quoted. The same goes for Apple Support, Apple Card, Sign in with Apple and device activation. Those are user reports. They’re very likely real, but Apple hasn’t confirmed them.
The store disruption came from NBC News reporting, which we saw through Bright Defense: employees in New York and Chicago said internal software stopped working, so they couldn’t complete purchases or book appointments.
Timeline
All times are approximate and in ET. Each line is traceable to the outlet named.
11:15 a.m. AppleCare on Device purchases marked unavailable on Apple’s status page (TIME).
About 11:30 a.m. First wave of Downdetector reports (Engadget).
About 11:45 a.m. iCloud sign in failures appear (Bright Defense).
12:20 p.m. Roughly 2,300 Apple Pay complaints on Downdetector in the US (Bright Defense).
12:29 p.m. Reports jump into the thousands (Engadget).
About 12:30 p.m. Philadelphia store register and app self checkout both down (NBC News via Bright Defense).
Just before 1 p.m. About 2,000 reports each for Apple Support, Apple Pay and iCloud (TIME).
2:27 p.m. App Store listed on the status page (TIME).
2:35 p.m. Apple’s “internal update” statement reaches Engadget.
3:30 p.m. App Store resolved (TIME).
3:39 p.m. AppleCare resolved (TIME).
4:45 p.m. iCloud sign in and AppleCare recovered, while Apple Business and Apple School Manager still showed problems (Bright Defense).
About 5:46 p.m. Every Apple status indicator green (CBS News, via Bright Defense and Status Is Down).
Later that evening. AppleInsider reported two App Store Connect outages still listed on the developer page (via Bright Defense). We couldn’t confirm when those cleared.
Where the Sources Disagree
Start time. TIME and Engadget put the first user reports around 11:30 to 11:40 a.m. ET, and the status page had AppleCare flagged at 11:15. The Tom’s Guide live blog opened with “around 9:45 am PT/12:45 pm ET,” more than an hour later. That’s probably when Tom’s noticed rather than when it started, but it’s a real gap.
End time. Tom’s Guide relayed Apple saying things were resolved around 3:07 p.m. ET. TIME has the App Store and AppleCare clearing by 3:39. CBS has the board fully green only around 5:46. And the developer page apparently still had open items after that. Which “end” you pick depends on whether you were buying a song, an AppleCare plan, or shipping an app build.
Peak numbers. Tom’s Guide saw Apple Pay “hit 2,000 in a matter of minutes.” TIME counted about 2,000 across three services just before 1 p.m. Bright Defense has 2,300 for Apple Pay at 12:20 and 1,800 for iCloud. These describe different services at different moments, so they don’t strictly conflict. Just don’t quote any one of them as “the” peak.
Apple Business status. Bright Defense says Apple Business was flagged around 1:40 p.m. ET. Tom’s Guide logged it at 19:01 UTC, which is 2:01 p.m. ET. About twenty minutes apart.
Who Got Hit, and How
Regular users couldn’t sign in to iCloud, buy AppleCare, download from parts of the App Store or reliably reach Apple Support. Apple Pay failures were widely reported, though not confirmed by Apple.
Businesses felt it in two ways. Apple’s own retail stores lost checkout. And anyone running Apple Business Manager or Apple School Manager saw device enrollment slow or stall well into the afternoon, which matters if you were setting up a batch of new laptops that day.
Developers got hit through App Store Connect, Xcode Cloud and In App Purchases on Apple’s developer status page. If your app sells subscriptions through Apple, some purchase attempts may have failed with nothing wrong on your end.
Downstream apps that use Sign in with Apple as a login option had a problem they couldn’t fix: users reported that button failing too.
What wasn’t reported: Gmail users also saw delivery complaints on Downdetector that day, about 2,800 by noon ET, according to Guardian and AOL coverage cited by Bright Defense. Google said it saw no broad disruption, and nobody has tied it to Apple. Don’t blame one on the other.
A reminder on Downdetector: it counts complaints from people who bothered to file one. It doesn’t count affected customers, and a few thousand reports can stand in for a much larger number of people, or a much smaller one.
Root Cause: What Apple Has Confirmed
Here is everything official, with who said it:
An Apple spokesperson told TIME and Engadget: “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.”
TIME reports Apple said the outages were not the result of a cyberattack. CBS News reported the same, per Bright Defense and Status Is Down.
That’s the full list. Apple hasn’t said which system the update touched, why it spread across commerce, identity and developer tools at once, or whether the update was rolled back or fixed forward.
Our Read of the Symptoms (Interpretation)
Everything in this section is our interpretation, not something Apple has confirmed.
When a single “internal update” takes out iCloud sign in, Apple Pay, the App Store, In App Purchases, Sign in with Apple and store registers on the same day, the obvious suspect is a shared layer underneath them. Two candidates fit.
The first is the account and identity layer. Nearly everything on the list needs an Apple Account check before it does anything. iCloud sign in was on Apple’s own status page, and the user reported failures (Apple Pay, Sign in with Apple, activation) are all things that lean on account checks. That fits well.
The second is the commerce layer. The very first status entry, at 11:15, was AppleCare purchases, not sign in. Store registers, App Store purchases and In App Purchases are all payment flows. That fits too, though it explains less of the iCloud trouble.
The honest answer is that the evidence doesn’t separate them, and it could be both if the update touched something they share. What we’d rule out is any link to the week’s other outages. Microsoft 365, AWS, the FAA ground stop, Chase and United all hit within days of this one. Nobody official has connected Apple to any of them.
What This Means for Small Teams and Solo Founders
You probably don’t think of Apple as a dependency. You should. If your app offers Sign in with Apple, your login button went down on Tuesday. If your shop takes Apple Pay, some checkouts failed. If you ship an iOS app, your build pipeline or subscription revenue may have stalled. None of that showed up on your server’s health check, because your server was fine.
This is the same lesson our Chase outage breakdown landed on a day earlier: the failure that hurts you is often inside someone else’s system, on the path your customer takes. A few things worth doing this week:
Keep a second login path. If Sign in with Apple is the only button on your signup page, add email or another provider so one vendor’s bad day doesn’t lock everyone out.
Offer a fallback at checkout. Apple Pay is great until it isn’t. A plain card form underneath costs nothing and saved sales on Tuesday.
Watch your own pages, not the vendor’s. Apple’s status board lagged user reports by up to an hour in places. Monitor your login page, your checkout page and any API your app calls.
Write the client message now. A two line “a provider we rely on is having issues, here’s what we’re doing” template is much easier to send when it already exists.
How to Protect Your Site: Alarms, Not Notifications
Tuesday’s outage started on a weekday, before lunch ET. For plenty of freelancers in other time zones, that’s the middle of the night. A push notification about a broken checkout page that arrives while your phone is on Do Not Disturb isn’t an alert. It’s a message you’ll read in the morning, after your client already has.
That’s why we built SIOPS around the alarm. When a monitor fails, SIOPS rings a native alarm on iPhone or Android that cuts through silent mode and Do Not Disturb (iPhone Critical Alerts, Android’s alarm channel), and every plan card lists call alerts too. You acknowledge it from the lock screen with one tap.
For an outage like this one, point SIOPS at the pages your customers actually use: your login page, your checkout page, your app’s API endpoint. Setup takes about two minutes with no agents or DNS changes. The free Hobby plan covers 5 monitors with 5 minute checks, and Serious checks every 60 seconds. Each project also gets a public status page you can send clients, so they’re not refreshing Apple’s.
One honest limit: SIOPS checks public HTTP and HTTPS endpoints from outside. It can tell you your checkout page stopped loading. It can’t see whether Apple Pay failed inside a customer’s wallet, so pair it with a test purchase now and then.
Apple Outage FAQ
Was the Apple outage a cyberattack?
No, according to Apple. A spokesperson blamed an internal update and said the outage was not the result of a cyberattack.
How long was Apple down on November 17?
Most consumer services were affected from about 11:15 a.m. ET until midafternoon. CBS News reported every status indicator green around 5:46 p.m. ET, and some developer tools showed issues later that evening.
Why couldn’t I use Apple Pay?
Thousands of people reported Apple Pay failures on Downdetector during the outage. Apple didn’t list Apple Pay on its status page in any report we read, so it’s unconfirmed, but it lines up with the iCloud account problems Apple did confirm.
Is Apple down right now?
Check Apple’s System Status page for consumer services and the developer status page for App Store Connect and Xcode Cloud. As of the last reports, every consumer service was back.
Did the outage affect app developers?
Yes. App Store Connect, Xcode Cloud, In App Purchases and Apple Podcasts all had entries on Apple’s developer status page during the day.
Why did Apple Stores stop taking payments?
Store staff told NBC News their internal software stopped working, so they couldn’t complete purchases or book appointments. Apple hasn’t explained that part separately from its internal update statement.
We’ll update this outage breakdown if Apple publishes more about what the update changed.



