
Tim Gouw/pexels.com
Apple Account sign-in failed for the second time in seven days on Tuesday, Nov. 17, and Apple says an internal update, not a cyberattack, caused outages that disrupted iCloud sign-in, the App Store and Apple Music and, by user reports, Apple Pay. Apple's System Status page listed iCloud sign-in problems on Nov. 10 alongside outages for iCloud Mail, Calendar and Contacts.
Apple Account is the login behind iCloud and App Store purchases, and Sign in with Apple extends it to apps built by other companies, so a failure at one point can reach every service that trusts it. Reports on recovery still diverged as of 3:57 p.m. ET. Apple has not said what the update changed.
Downdetector, which collects crowd-sourced user reports rather than verifying outages, showed a handful of connection complaints around 11:30 a.m. ET and thousands by 12:29 p.m. ET. Digital Trends noted that Downdetector does not independently confirm outages. Reuters counted about 2,300 U.S. Apple Pay reports near 12:20 p.m. ET and about 1,800 iCloud reports at the peak.
Apple's own page trailed the complaints. 9to5Mac reported at 12:33 p.m. ET that Downdetector showed problems across multiple services while Apple's System Status page still listed them as available. By 1:05 p.m. ET, Tom's Guide reported, iCloud Account and Sign In read "This service may be slow or unavailable." mobiFlip, a German site, said reports were concentrated in Europe, though a reliable geographic breakdown was not yet possible, and that many users saw Apple services still working.
The outage landed amid other disruptions. CBS News noted other recent disruptions, including an FAA ground stop and Microsoft email problems. CBS also reported that JPMorgan Chase and Bank of America customers had deposit and Zelle transfer problems on Monday.
Apple Account, formerly Apple ID, is used for App Store and iCloud functions. Sign in with Apple, announced June 9, 2019, turns that account into a single sign-on provider for other companies' apps, built on OAuth 2.0 and OpenID Connect. Single sign-on trades convenience for concentrated risk, because losing the authentication system can block access to every linked system. A single point of failure is a component whose failure stops an entire system when no backup exists.
Tuesday's reports fit that pattern, though Apple has not described the mechanism. The author of mobiFlip's report said apps linked to his Apple Account kept asking him to re-authenticate and he could not complete the step. Downdetector reports also spiked for Sign in with Apple, Tom's Guide reported.
Users who were already signed in were not necessarily safe. 9to5Mac relayed reports of unexpected iCloud sign-outs on iPhone and Mac, followed by verification failures or unknown errors on sign-back-in. Apple has not said which infrastructure failed or why the problem spread across so many services.
An Apple spokesperson said many systems were back up and running after an internal update caused outages that morning, and that the company was working to restore the remaining systems as soon as possible. The company also said the disruption was not a cyberattack. Tom's Guide logged the statement at 3:07 p.m. ET.
Apple has not identified which update was responsible, what it changed or why the failure spread, The Apple Post reported. The company has pointed to internal causes before. In March 2015, an internal DNS error crippled iTunes and other Apple services, Network World reported.
Identity vendor Ory documented a different Apple-side change in June 2025. On June 11, 2025, Apple's OpenID Connect discovery endpoint for Sign in with Apple began redirecting to a document that declared a different issuer than the one in Apple's ID tokens, so apps that validated tokens correctly rejected valid logins. Apple removed the redirect by June 12, but Ory, which sells identity products, said the two endpoints still declared different issuers afterward.
Apple also has not said whether Tuesday's update went out in stages, leaving key questions unanswered.
Apple's System Status page logged the earlier outage starting at 5:49 p.m. ET on Nov. 10, listing iCloud Mail, Calendar, Contacts, iWork for iCloud and Game Center, with Find My slow or unavailable. At 7:22 p.m. ET, Mail, Calendar and Contacts were listed as resolved while Photos and iCloud sign-in were newly listed with issues. Apple told 9to5Mac at 5:18 p.m. PT, or 8:18 p.m. ET, that all outages were resolved, Itechify reported the statement.
Developers reported first-time Sign in with Apple failures beginning around 00:56 UTC on Nov. 14, or 7:56 p.m. ET on Nov. 13. One developer said about 45% of first-time sign-ins in their App Store app failed while returning users signed in normally. A second thread gathered about 15 developers describing the same pattern. One of them said Apple's status page showed services normal. Neither thread showed a reply from Apple staff when checked.
The Claude iOS app's status page logged a Sign in with Apple incident for new accounts at 7:11 a.m. UTC, or 2:11 a.m. ET, on Nov. 14. Its latest update, at 3:12 p.m. ET that day, said the team was still investigating, with Google or email sign-up as a workaround. The Nov. 14 reports come from developers, and Apple has not confirmed them. Apple engineers have acknowledged Sign in with Apple outages before. A Developer Technical Support engineer's forum post covered a June 18 to June 23, 2025, outage that returned authentication errors, which Apple described as a configuration issue.
Reports for Apple Pay and Apple Card dropped steeply by 1:27 p.m. ET, Tom's Guide said. The Apple Post cautioned that Apple Pay reports did not necessarily mean third-party contactless payments stopped. Some people also could not activate new devices.
Customers and people who said they worked at Apple Stores reported that retail systems blocked some payments, order pickups and repair help. The Apple Post added that the reports were not independently verified at every location.
Schools, businesses and developers hit different walls. Apple's status pages added Apple Business, Apple School Manager and Schoolwork by 2:20 p.m. ET, Tom's Guide reported. Developers reported trouble accessing App Store Connect.
Recovery reports diverged by mid-afternoon. Apple told Tom's Guide at 3:34 p.m. ET that the issue was resolved, even though status pages still listed outages. At 3:56 p.m. ET, only AppleCare on Device remained listed as down. CBS News, updated at 3:57 p.m. ET, said Apple's page still showed disruptions to some services, including iCloud sign-in. How-To Geek reported the App Store and Apple Music back up.
James Knight of Digital Warfare, a former government whitehat hacker, said public reporting pointed to a sign-in and account problem, according to Tom's Guide. He warned users not to click messages telling them to verify their Apple ID and to sign in only through Settings or apple.com.
Phishing messages typically create urgency and impersonate a trusted provider. Passkeys and WebAuthn bind sign-in responses to the legitimate domain, which makes them phishing-resistant sign-in methods, while NIST does not classify manually entered one-time codes that way.
Apple's System Status page is the first stop during a server-side failure, and password resets are unlikely to help, The Apple Post said in its assessment. Itechify likewise advised against resetting a password over an outage error.
Reports diverged at 3:56 p.m. ET and 3:57 p.m. ET. Tom's Guide said only AppleCare on Device remained listed as down. CBS News said iCloud sign-in still showed issues. Apple's System Status page is the official check, and Downdetector shows only user reports.
Apple Account is the shared login behind iCloud and App Store purchases. Single sign-on designs can block access to every linked system when the authentication system fails. Apple has not confirmed that the sign-in layer was the point of failure on Nov. 17, only that an internal update caused outages.
Apple has not said. Downdetector reports spiked for Sign in with Apple on Nov. 17. mobiFlip's author could not complete re-authentication in linked apps. During the Nov. 14 incident, the Claude iOS app's status page listed Google or email sign-up as a workaround for new users.
Outlets that covered the outage advised against it, because a password reset does not fix a server-side failure. Itechify said the same. If you receive an unexpected message telling you to verify your Apple ID, do not click it and sign in through Settings or apple.com instead.
