If you are having trouble loading Gmail or a YouTube video tonight, you aren't alone. A whole ton of Google services were having problems. Google Drive, Hangouts, Stadia, the Play Store, and even Nest were all affected, though reports indicate the issue has since resolved.
The Play Store and many other services were entirely inaccessible during the outage.
Some services, like the Play Store and Google Calendar, refused to load at all. Others, like Gmail, would load after a very long wait, though it could take a while for your list of messages to be populated, and you may have had difficulty sending or receiving emails.
Loading Gmail may have taken a while.
Though the service is unreliable when it comes to specifics, Downdetector indicated reports of problems for pretty much all of the Google services it lists. However, other services from third-party companies are receiving similar reports. The issue may be larger than Google itself, though these other affected services may simply be Google Cloud customers. Though reports were fairly widespread, we don't know if the issue was regional, though several of us across the US here at Android Police were affected.
A little under an hour later, the G Suite Dashboard was updated to show some services were having problems.
Following our original coverage, the G Suite Status Dashboard was later updated to state that some services were having issues. The Google Cloud Status Dashboard also indicated that many of Google's business and developer-facing services, including Firestore and Google Cloud SQL, were having a "service disruption," though all issues are reportedly resolved as of 10:07 PM ET.
When asked for comment, a Google Cloud spokesperson provided us with the following statement:
"We experienced a short service disruption affecting several products including G Suite, and are now recovering. For more details, please visit our status dashboard."
The problem was short-lived. Reports and our own anecdotes indicate that the affected services are all back up, and our coverage has been updated. It looks like the issues were suffered across pretty much the entire Google Cloud Platform starting at 18:28 (Pacific) September 24, with the engineering team taking around an hour to resolve the situation. It's not clear exactly what went wrong, but it's great to see that Google was able to fix it so quickly.