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
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
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