What happened at Apple
MacRumors put the start of the problems at around 11:45 a.m. ET. Social media reports at the time described people who couldn't reach their Apple Accounts or sign in to services. Apple's retail store systems also went offline, and customers in stores couldn't complete purchases.
Apple's own status page listed outages for several services. PBS, citing the AP, reported that Apple Music, the App Store and AppleCare suffered full outages, and that iCloud sign-in was also having issues. TechCrunch reported that the iCloud Account & Sign In problem affected "all users." As the incident developed, the page grew to include:
- Apple Business
- Apple School Manager
- Schoolwork
- iCloud Mail
- iCloud Web Apps (iCloud.com)
- the Volume Purchase Program
Downdetector also showed a spike in user complaints about Apple Pay. That is user-report data. It does not show that Apple officially listed Apple Pay as down.
Apple's emailed statement said many systems were back up after an internal update caused some outages that morning. The company said it was working to restore the rest. It told Bloomberg the outage was not a cyberattack. TechCrunch reported that by 6 p.m. ET Tuesday the status page showed all outages resolved.
Apple hasn't said what the update contained or how it broke things. No root-cause report has appeared, so "internal update" is the full explanation for now.
Why a sign-in outage feels bigger
Authentication failures cause problems well beyond one app. TechCrunch noted that iCloud problems can make an iPhone ask for your Apple ID and password, and can make other sign-in attempts with that account fail. Some Reddit users also said they couldn't activate a new iPhone. TechCrunch described that as likely related, but Apple hasn't confirmed it.
If you hit this kind of failure, the evidence supports a short list of steps:
- Check the provider's status page before touching anything on your device.
- Work out whether the problem is the account or sign-in service, or just your device.
- Don't treat repeated credential prompts as proof your account was compromised while a provider-wide sign-in incident is under way. That isn't a guarantee that your account is safe.
- Don't reset devices, change passwords repeatedly or reinstall apps. Nothing in the reporting suggests those actions fix a service-side outage.
For organizations, the status page's inclusion of Apple Business, Apple School Manager and the Volume Purchase Program shows how admin and deployment portals can go down along with consumer services. I'd say that's a reason to check whether your device-management and app-licensing workflows have a plan for a vendor-side outage. That is general industry reasoning, not something the reporting established.
The Microsoft 365 outage
The PBS report cited Microsoft's statement that there was no indication malicious activity caused the outage. Microsoft also said the outage was not related to a cyberattack or AI agents. BleepingComputer has since reported Microsoft's preliminary post-incident findings:
- A software bug introduced in July caused a cascading failure that left more than 80% of Microsoft's networking gateway servers unresponsive.
- The nearly 24-hour outage on November 12 hit Outlook, Exchange Online, Teams and Copilot worldwide.
- The preliminary report in the Microsoft 365 Admin Center named three problems: a previously undetected software bug, increased traffic after a Teams failover, and reduced server capacity.
- The bug was triggered when Teams automatically switched to the networking infrastructure used by Exchange Online about 15 hours before the outage.
- Microsoft confirmed active customer impact had ended by 11:10 AM ET on November 13.
BleepingComputer also noted that a separate Teams outage earlier that day may or may not be related. Admins looking for Microsoft's own tracking should check the Microsoft 365 admin center. Secondary reporting cites incident MO1550821 for the main outage, but I haven't confirmed that against Microsoft's own pages.
Microsoft's failure came from internal infrastructure and configuration. Apple's came from an internal update. Neither company has said anything that would suggest a shared cause.
The other incidents
The AP roundup lists these separately:
- FAA: The FAA's own account, per the research notes, describes a technical problem on Friday, November 13 that led to a nationwide ground stop. Its preliminary explanation points to legacy equipment becoming unstable under a flood of connection attempts. The FAA said the root cause was still under investigation. I couldn't open the FAA page myself, so treat those details as relayed rather than verified.
- United Airlines: A system outage on Monday lasted more than 90 minutes and delayed departures. United said there was no indication it was cybersecurity-related.
- JPMorgan Chase and Zelle: Thousands of customers had trouble reaching online accounts at several major banks and Zelle after a technical issue at Chase. Chase said it wasn't a cyberattack and confirmed Tuesday that systems were normal.
- Marriott: The company said it resolved a technical issue affecting sign-in on Marriott.com and the Bonvoy app. Its review found no sign the problem was cybersecurity-related.
Is it all connected?
Public suspicion is running high. MacRumors' comment section was full of readers doubting the "internal update" explanation. That reaction is understandable, but the timing alone doesn't prove a link. TechCrunch's reporting says none of the week's outages has been attributed to cyberattacks.
The companies all have an incentive to rule out an attack quickly, and their statements are early. Microsoft's detailed report gives a plausible, documented mechanism. Apple hasn't offered one, so its explanation is still unverified. The honest position is that these are separate incidents with unconnected stated causes, and that Apple's cause is still unknown.
What admins and users can take from it
- Bookmark each vendor's status page, and keep an out-of-band way to reach your team if email and chat go down together.
- Read the post-incident reports when they appear. Microsoft's shows that a bug can sit unnoticed for months before a traffic shift triggers it.
- Don't assume an outage is an attack. Wait for the vendor's account of what happened.
Apple's outage looks resolved. Whether Apple publishes a fuller explanation is the thing to watch.
References
- Apple joins the list of recent tech breakdowns after an update goes awry - PBS PBS · 2026-11-17T22:26:17+00:00
- Apple Blames Internal Update for Outage, Says It Wasn't a Cyberattack - MacRumors macrumors.com
- Apple services, including iCloud, App Store, Apple Music, and more, hit by outage | TechCrunch techcrunch.com