Apple’s iCloud Account & Sign In service was still listed as an issue affecting all users at the time of writing, after a morning of outages across consumer and developer systems that the company said was caused by an internal update, not a cyberattack.
When TSN checked Apple’s System Status page shortly after 20:50 GMT on 17 November 2026, iCloud Account & Sign In was marked as an issue from 08:45 PST (16:45 GMT), with the notice that “All users are affected” and that the service “may be slow or unavailable.” AppleCare on Device was listed as an outage from 08:15 PST (16:15 GMT), also affecting all users, with the message “AppleCare purchase is temporarily unavailable.” Those two entries had no end time. The Developer System Status page, checked at the same time, still listed all-user outages on App Store Connect from 08:50 PST (16:50 GMT) and on Xcode Cloud from 09:00 PST (17:00 GMT).
The App Store and the Volume Purchase Program had already come back. Both were listed as a resolved outage running from 08:45 PST to 12:00 PST (16:45 to 20:00 GMT), with “Some users were affected.” iCloud Mail was listed as resolved. iCloud Web Apps (iCloud.com) was still shown as an ongoing performance problem for some users from 08:45 PST. Apple Business, Apple School Manager and Schoolwork were listed as an ongoing issue for some users from 10:40 PST (18:40 GMT). On the developer page, further ongoing entries covered App Store Connect Analytics and Sales and Trends, Apple Music Connect, and Apple Music for Artists. The consumer System Status page had no current event for the public Apple Music service at the time of that check.
Apple said, in a statement first given to Bloomberg and published by TechCrunch, that the disruption came from an internal update and was not a cyberattack. “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.”
The episode sits in a week of high-profile service failures already covered by TSN, including Microsoft 365 users being unable to connect, a Google Cloud outage in London, and an FAA nationwide ground stop after communication issues. Apple’s statement treats this incident as a technical failure on its own systems. The status pages give no country-by-country breakdown, so UK users are not listed separately from the “all users” and “some users” notices.
Apple’s status pages were still mixed after 20:50 GMT
The useful picture at the time of writing is not that every Apple service is down, or that everything is back. It is a split list. Sign-in and AppleCare purchases were still flagged for all users hours after the App Store window had closed. Developer tools that publishers and app teams depend on — App Store Connect and Xcode Cloud — were still listed as all-user outages. Some of the later entries, including the education and business tools from 18:40 GMT and the Music Connect and Music for Artists listings from 19:09 GMT, started after the first wave. Those later flags are part of the same day’s status record; they are not, on the pages themselves, a second named incident.
An internal-update statement is not a finished incident report
Apple’s wording to Bloomberg is clear as far as it goes: an internal update, not a cyberattack, and remaining systems still being brought back. That is a company statement, not a technical post-mortem. It does not say which update failed, which systems it touched first, or why sign-in and AppleCare purchases were still listed after the App Store had been marked resolved. The status pages, which Apple can change as it works, are the public record of what was still outstanding when this article was written. They are also the reason the piece has to be read as a snapshot taken shortly after 20:50 GMT, not as a final score.
The “all users” and “some users” labels matter in the same way. An all-user issue on iCloud Account & Sign In is a broader claim than a “some users” performance flag on iCloud.com. Neither label is a count of failed logins, and neither is a finding about the security of those accounts. Apple has said the cause was not a cyberattack. Nothing on the status pages contradicts that statement, and nothing on them independently proves it. Until Apple publishes a fuller account, or the remaining flags are cleared, the accurate story is the one on the status boards: a morning disruption that the company attributes to an internal update, with sign-in, AppleCare purchases and several developer services still listed as affected at the time of writing.
Sources
- Apple, System Status, checked shortly after 20:50 GMT on 17 November 2026.
- Apple, Developer System Status, checked shortly after 20:50 GMT on 17 November 2026.
- TechCrunch, “Apple services, including iCloud, App Store, Apple Music, and more, hit by outage,” 17 November 2026, publishing Apple’s statement to Bloomberg.
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
Microsoft 365 Users May Be Unable to Connect, Company Says is the closest recent TSN account of a major consumer-service outage this week, and is the next read.
- Google Cloud London Outage Tied to Generator PLC Fault
- FAA Issued a Nationwide Ground Stop After Communication Issues
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X





