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
March saw many of the big tech companies have technical issues with their products and services. But the biggest one was by far the colossal Google; Google Maps experienced the much dreaded website downtime impacting thousands of users across the globe. It was reported online that Google Maps had suffered a partial outage meaning that many couldn’t access the location tool, but why and more importantly, how?
What impact did it have?
Users searching for a place and needing directions, and sites that have an API link with the plugin to display their location and other essential services that rely on Google Maps all faced issues. Think of all the users that were forced to use alternative apps to help them navigate their way and might end up sticking with them as they found they were easier to use or even better.
Like many things that we take for granted, Google Maps has become synonymous with modern day explorers that make full use of the service to find what they are looking for whether it be in cities, countryside and even the wilderness. This type of outage might not be an issue for most people as they can use alternatives like Apple Maps but a lot of businesses rely on this service to direct customers to their premises and the potential financial loss could be significant.
What was Google’s response?
On the 18th March a Google spokesperson via an email statement confirmed the outage and said “We’re seeing reports of difficulties accessing some Google Maps and Google Maps Platform services. Our team is investigating and working to resolve the issue as quickly as possible.”
Google still has not said what caused the outage, simply that there was a partial outage but have not gone into more detail. However I feel I have to mention that Google worked very quickly on a fix and within a few hours the service was back up and running. Phew.
How did the public react to Google’s downtime?
Many users were stunned that Google Maps was down and had to find an alternative method to help with navigation, something they hadn’t even had to consider doing before. It’s safe to say, however, that the trusty old printed maps did not make a return. In actual fact, the main topic was how little Apple Maps is used. It was clearly highlighted by many users that the reason for this is because it’s a “much poorer user experience especially when compared to Google Maps”. I can’t speak from experience as I’ve always used an Android phone but I guess there must be a lot of iPhone users that use Google Maps on the down low. Shh.
The moral of the story? Even the tech giants like Google can experience downtime. That’s why you need uptime monitoring.
StatusCake Team
Share this
More from StatusCake
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
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026