Thursday, 19 November 2026

Apple outage cause: its own update, and yes, it’s fixed now

Apple says a change it pushed itself, not hackers, broke iCloud sign-ins, Apple Pay and the App Store for hours on Tuesday. Here's what failed and why.

Server racks with status lights in a data center

The short version

  • Apple says an internal update it made itself caused the outage on Tuesday, November 17, and that it was not a cyberattack.
  • Problems began around 11:45 a.m. ET and hit iCloud sign-ins, Apple Pay, the App Store, Apple Music, AppleCare and Apple retail stores.
  • Apple's System Status page showed every affected service resolved by 6 p.m. ET the same day.
  • The outage came during a week of unrelated failures at Microsoft, the FAA, Chase and United, none blamed on hackers.
Quick read · 2 min

Apple says the cause of its big outage on Tuesday, November 17, was an internal update it rolled out itself. It was not a cyberattack, the company says, and by 6 p.m. ET its System Status page showed every affected service working again.

The trouble started around 11:45 a.m. ET. Because the update broke Apple Account sign-in, the damage spread far beyond one app:

  • iPhone and Mac users were signed out of iCloud or saw verification errors.
  • Apple Pay, the App Store and Apple Music stopped working for many people, and Apple Stores couldn't complete sales.
  • Schools, businesses and developers lost tools such as Apple School Manager and App Store Connect.

The outage arrived during a week of failures at Microsoft, the FAA, Chase and United. None has been blamed on hackers, and officials say there's no evidence the incidents are connected. Apple hasn't said exactly what its update changed.

The Apple outage cause was Apple itself. The company says an internal update it rolled out on Tuesday, November 17, knocked iCloud sign-ins, Apple Pay, the App Store and Apple Music offline for hours, and it says plainly that no cyberattack was involved.

And yes, the Apple outage is over. By 6 p.m. ET on Tuesday, Apple’s System Status page listed every affected service as resolved. If you were signed out of your Apple Account, couldn’t pay with your iPhone or watched an app download stall, this is what broke, why it felt so widespread and why it landed in a week when everything else seemed to be failing too.

01

Apple outage cause: what Apple actually said

Apple blamed an unspecified internal update. In a statement given to several news organizations, a spokesperson said many systems were already running again after the update caused outages that morning, and that Apple was working to restore the rest as quickly as it could.

That is the full official explanation. Apple has not said what the update changed, which team pushed it or why it spread to so many services at once. It did go out of its way to rule out an attack, which matters because many users online had already started guessing that hackers were behind it.

Like every large tech company, Apple has cloud hiccups from time to time. This one stood out because it hit iCloud account sign-in, which almost every Apple service relies on. When sign-in fails, the services built on top of it struggle too.

Payment terminal on a store counter beside a phone
02

Which Apple services went down, and for how long

Trouble started around 11:45 a.m. ET, just before lunchtime on the East Coast, when people began reporting that they couldn’t reach their Apple Accounts or sign in to services. Within about an hour, the tracking site Downdetector was full of complaints. At the peak, roughly 2,300 US users reported Apple Pay problems and about 1,800 reported trouble with iCloud.

Apple’s own status page eventually confirmed a long list of problems. The consumer side included:

  • iCloud account sign-in, which Apple marked as affecting all users
  • Apple Pay and the App Store, where apps wouldn’t load or download
  • Apple Music, plus iCloud Mail and the iCloud website
  • AppleCare on Device and Apple Support
  • iPhone activation, which stopped some people setting up new devices

Schools and businesses were hit too. Apple School Manager, Schoolwork, Apple Business and the Volume Purchase Program all showed issues, and developers had trouble getting into App Store Connect and Xcode Cloud. Apple retail stores went offline as well, and shoppers inside couldn’t complete purchases.

Recovery came in stages. Apple said Apple Music was online again while other systems were still being restored, and consumer services returned before the developer tools did. By 6 p.m. ET, the status page showed every outage resolved, so most services were down for a few hours rather than a full day.

03

Why this one felt worse than a normal Apple glitch

Most Apple outages hit one service, such as Music or iMessage, and you can work around them. This one hit sign-in, and that changes everything for an iPhone or Mac owner.

When iCloud can’t confirm who you are, your iPhone may keep asking for your Apple Account password, and attempts to sign in to other Apple services fail. Some people were signed out of iCloud without warning on iPhone and Mac, then saw a blunt “Verification Failed” message or an unknown error when they tried to sign back in.

There was also a trust problem. In the early part of the outage, Apple’s status page kept showing services as available while Downdetector filled with reports. Apple did update it as the day went on, adding service after service.

04

What the outage means for your iPhone, Mac and Apple Pay

For most people, there is nothing left to fix. Apple says the problem was on its side, it says this wasn’t an attack, and its services were restored the same day.

The more useful lesson is how much rides on one login. Apple Pay at the checkout, app downloads, music streaming, backups and even setting up a new phone all lean on your Apple Account. When that layer breaks, a store purchase can fail just as easily as a song can stop.

If a payment failed during those hours, the outage explains it. Apple Pay drew more US reports than iCloud at the peak, and Apple Stores themselves couldn’t ring up sales for a time.

For the next time something looks wrong, Apple’s System Status page lists each service with its current state, and the company has a separate status page for developer services. Tuesday showed that the page can trail behind what users see, so reports on Downdetector and social media often surface a problem first.

05

A rough week of outages, but no link found

Apple’s failure landed in the middle of a run of high-profile breakdowns, which is why so many people assumed something bigger was going on. On Thursday, November 12, Microsoft Outlook went down for nearly 24 hours, and Microsoft later blamed a latent defect tied to a fix on its networking gateway servers. On Friday, a Federal Aviation Administration communications problem led to a nationwide ground stop.

Then on Monday, a software bug at JPMorgan Chase slowed online banking and payments that touched other banks and Zelle, and United Airlines had a system outage that lasted more than 90 minutes. On the same Tuesday as Apple’s trouble, some people also reported problems with Gmail, though Google said it saw no sign of a broad disruption.

So far, not one of these companies or agencies has pointed to a cyberattack. Each blamed its own software, equipment or systems. Officials and companies say there is no evidence tying the incidents together, though the timing kept the question alive all week.

06

Quick answers

Was the Apple outage a cyberattack?

No. Apple says an internal update it made caused the outage on November 17, and it specifically ruled out a cyberattack.

Is Apple down right now?

The November 17 outage is over. Apple’s System Status page showed all affected services resolved by 6 p.m. ET that day, so any new problem would be a separate issue.

What time did the Apple outage start?

Reports began around 11:45 a.m. ET on Tuesday, and complaints on Downdetector climbed sharply over the following hour.

You're reading the quick version.