StatusCake

Website downtime: The one where Google Maps went down

website down

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.

Share this

More from StatusCake

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Blog

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

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.