It looks like Google experienced intermittent downtime across several regions on May 12, leaving thousands of users confused as searches either failed to load or returned a strange internal server error.

The issue didn’t appear to be global in the traditional sense, but it was widespread enough across parts of APAC, India, and a few Western regions to raise eyebrows. And perhaps more interestingly, there’s still no clear explanation from Google about what exactly happened.

The first signs of trouble began surfacing around 5:30 am BST / 12:30 am EDT / 2:30 pm AEST, when outage trackers started lighting up with complaints. Platforms like Downdetector and IsDown.app recorded a sudden spike in reports from Australia, India, the Philippines, Malaysia, and New Zealand.

At its peak, Downdetector alone logged over 4000 reports from Australia, most of them tied to Google Search, content not loading, and the Google.com homepage failing to respond. In India, over 3,300 complaints were registered by around 10:23 am IST, with users reporting nearly identical issues.

What made this particularly noticeable was the error message users kept encountering: “Server Error. We’re sorry, but it appears that there has been an internal server error while processing your request. Our engineers have been notified and are working to resolve the issue.” For many, the issue was inconsistent. One search would work fine, the next would fail completely. Some users noted that specific suggested searches linked to TV shows or books seemed to trigger the problem first, before it spread to all queries.

Image Credit: Times Of India

Social platforms quickly filled with reactions. Users on X and Reddit remarked on how rare it is to see Google go down at all, with some calling it the first time they had witnessed such an outage in years.

By late afternoon in affected regions, the volume of complaints on Downdetector had dropped sharply, suggesting services were stabilising. However, as of 11:45 pm BST, Google’s own Google Workspace Status Dashboard still showed “No Incidents,” and the company had not issued any official statement or post-mortem explaining the root cause.

For now, it appears the disruption was brief but widespread enough to be felt across multiple countries. And until Google provides clarity, users are left with the unusual experience of having seen one of the internet’s most dependable services briefly stumble and recover just as quietly.