Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
We all know and associate Apple as a reliable and innovative tech giant which sets endless new trends for its industry. It’s arguably the one company that many aspire to be like and emulate with the massive global growth they’ve seen over the past decade. But even this goliath tech company has its bad days and unfortunately for Apple, it had a whole week of bad luck that tested the patience of its customers across the world.
What happened to Apple?
The week beginning the 21st of March is a week that Apple would like to forget after suffering 2 different outages to its services. With the reputation Apple has we would have never thought or expected them to have had such an issue with their servers.
Apple’s outages explained
The first outage on Monday the 21st of March affected millions of Apple users as the Apple Music, Apple Maps, iCloud, iCloud Calendar, iCloud Contacts, iCloud Mail, iCloud Private Relay, iTunes Store, Radio, Podcasts, the App Store, iMessage, and Apple TV+. which practically means every Apple device would have been affected and pretty much everyone that uses an Apple service. The bad luck did not stop there either; the issues also extended to Apple’s corporate side as well as affecting their retail system practically pausing the company which undoubtedly was very costly to them.
What caused Apple’s outages?
The reason for the issue was identified as a Domain Name issue which you would think Apple would have picked up on or sorted out way before it got to a global outage. However, Apple did not go into any detail about why this issue occurred. The next day it identified that Apple’s Mac App Store, Apple Card, Apple Books, iCloud Web Apps, and Weather stopped working. In essence, what this Domain Name Issue caused was a complete outage for Apple and the service it provides to its customers. Once the issue was identified it was dealt with really quickly by Apple which was praised by its millions of customers.
Another Apple outage
A couple of days later on the 24th of March, there were more issues for Apple, this time affecting messenger and it was identified as a server issue. What was strange about this incident is that it was not reported on Apple’s status page, so it’s either Apple did not want to inform their customers as it would be quick to fix or worst they didn’t even realise until someone mentioned the issue. There was some speculation that it might be because Apple is now creating its own cloud storage server system and are slowly moving services over its server. Apple is investing heavily in this service and has also announced it will be spending over $1.5 billion on AWS in the next few years which shows the increase in demand for its services. Simultaneously it is also creating its own servers centres and soon is expecting to finish its Danish Data centre.
This upgrade will be needed by Apple as they are also adding additional services to its current business offering with Apple Pay as its introduction to the financial world but now there is speculation that Apple is dipping its toes in the advertising segment as it sees this as a potential growth area. By doing this it will now compete with Meta, Google and Amazon the other tech giants in this segment.
StatusCake Team
Share this
More from StatusCake
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026