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
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
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026