Google Outage History

Google is up right now

Google had 126 outages in the last 2 years totaling 576h 27m of downtime — averaging 5.2 incidents per month.

There were 126 Google outages since July 18, 2025 totaling 576h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloud.google.com/ · Aggregated across Google products

Major September 16, 2026 via Firebase

Crashlytics and Performance Monitoring consoles experiencing low availability.

Detected by Pingoru
Sep 16, 2026, 06:00 PM UTC
Resolved
Sep 16, 2026, 08:30 PM UTC
Duration
2h 30m
Affected: CrashlyticsPerformance MonitoringCrashlytics (global)Performance Monitoring (global)
Timeline · 2 updates
  1. investigating Sep 16, 2026, 07:25 PM UTC

    Crashlytics and Performance Monitoring consoles experiencing low availability.

  2. resolved Sep 16, 2026, 08:36 PM UTC

    Disruption is resolved at 13:30 PDT

Read the full incident report →

Major September 16, 2026 via Google Pay

RESOLVED: We're aware of a problem with Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API affecting a majority of users. We will provide an update by Sep 16, 2026, 3:47 p.m. UTC detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. The affected users are able to access Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior.

Detected by Pingoru
Sep 16, 2026, 04:37 PM UTC
Resolved
Sep 16, 2026, 04:37 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 16, 2026, 04:37 PM UTC

    Incident began at 2026-09-16 15:00 and ended at 2026-09-16 16:30 (times are in Coordinated Universal Time (UTC) ). The problem with Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API and Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior. Affected products: Android CreateButton API, Android IsReadyToPay API, Android LoadPaymentData API, Secure Payment Authentication (SPA), Web CreateButton API, Web IsReadyToPay API, Web LoadPaymentData API

Read the full incident report →

Major September 16, 2026 via Google Play

Incident affecting Play Billing Purchases

Detected by Pingoru
Sep 16, 2026, 03:00 PM UTC
Resolved
Sep 16, 2026, 05:00 PM UTC
Duration
2h
Affected: Play Billing Purchases
Timeline · 2 updates
  1. investigating Sep 16, 2026, 04:07 PM UTC

    We're investigating reports of an issue with Play Billing Purchases. We will provide more information shortly. The affected users are able to access Play Billing Purchases, but are seeing error messages, high latency, and/or other unexpected behavior.

  2. investigating Sep 16, 2026, 05:04 PM UTC

    The problem with Play Billing Purchases has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Minor September 11, 2026 via Google Workspace

Mitigated intermittent elevated error rates with Gemini 3.1 Pro models on Gemini Web and Gemini App.

Detected by Pingoru
Sep 11, 2026, 01:00 PM UTC
Resolved
Sep 11, 2026, 08:22 PM UTC
Duration
7h 22m
Affected: Gemini
Timeline · 1 update
  1. resolved Sep 11, 2026, 08:45 PM UTC

    Description: Between 6:00 PDT and 13:22 PDT on 11 September 2026, a subset of Gemini users may have experienced elevated error rates with Gemini 3.1 Pro models on Gemini Web and Gemini App. From preliminary analysis, the issue was triggered by a recent rollout. Our engineers identified the cause and mitigated it with a code change. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have encountered intermittent errors when using Gemini 3.1 Pro models on Gemini Web and Gemini App.

Read the full incident report →

Major September 10, 2026 via Firebase

Incident affecting Test Lab

Detected by Pingoru
Sep 10, 2026, 06:00 AM UTC
Resolved
Sep 10, 2026, 11:20 PM UTC
Duration
17h 20m
Affected: Test LabTest Lab (global)
Timeline · 1 update
  1. investigating Sep 10, 2026, 07:16 AM UTC

    Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.

Read the full incident report →

Minor September 3, 2026 via Google Play

Incident affecting Play Developer Subscriptions and In-App Purchases API

Detected by Pingoru
Sep 03, 2026, 08:28 PM UTC
Resolved
Sep 05, 2026, 02:55 AM UTC
Duration
1d 6h
Affected: Play Developer Subscriptions and In-App Purchases API
Timeline · 3 updates
  1. investigating Sep 03, 2026, 08:42 PM UTC

    We're investigating reports of an issue with Play Developer Subscriptions and In-App Purchases API. We will provide more information shortly. The affected users are able to access Play Developer Subscriptions and In-App Purchases API, but may experience delays in sending or receiving messages. Most developers are experiencing high latency with real time developer notifications.

  2. investigating Sep 04, 2026, 10:15 PM UTC

    Play Developer Subscriptions and In-App Purchases API service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access Play Developer Subscriptions and In-App Purchases API, but are seeing error messages, high latency, and/or other unexpected behavior.

  3. resolved Sep 05, 2026, 06:10 AM UTC

    The problem with Play Developer Subscriptions and In-App Purchases API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Major September 1, 2026 via Google Cloud

Multiple products in us-central1-b are experiencing network service degradation.

Detected by Pingoru
Sep 01, 2026, 02:44 PM UTC
Resolved
Sep 01, 2026, 06:52 PM UTC
Duration
4h 8m
Affected: AlloyDB for PostgreSQLApigeeCloud FilestoreCloud RunCloud SpannerGoogle App EngineGoogle BigQueryGoogle Cloud BigtableGoogle Cloud DataflowGoogle Cloud SQLGoogle Compute EngineGoogle Kubernetes EngineHybrid ConnectivityLooker (Google Cloud core)Virtual Private Cloud (VPC)us-central1AlloyDB for PostgreSQL (global)AlloyDB for PostgreSQL (us-central1)Apigee (global)Apigee (us-central1)Cloud Filestore (global)Cloud Filestore (us-central1)Cloud Run (global)Cloud Run (us-central1)Cloud Spanner (global)Cloud Spanner (us-central1)Google App Engine (global)Google App Engine (us-central1)Google BigQuery (global)Google BigQuery (us-central1)Google Cloud Bigtable (global)Google Cloud Bigtable (us-central1)Google Cloud Dataflow (global)Google Cloud Dataflow (us-central1)Google Cloud SQL (global)Google Cloud SQL (us-central1)Google Compute Engine (global)Google Compute Engine (us-central1)Google Kubernetes Engine (global)Google Kubernetes Engine (us-central1)Hybrid Connectivity (global)Hybrid Connectivity (us-central1)Looker (Google Cloud core) (global)Looker (Google Cloud core) (us-central1)Virtual Private Cloud (VPC) (global)Virtual Private Cloud (VPC) (us-central1)
Timeline · 8 updates

Read the full incident report →

Major September 1, 2026 via Google Maps Platform

Multiple products in us-central1-b are experiencing network service degradation.

Detected by Pingoru
Sep 01, 2026, 02:44 PM UTC
Resolved
Sep 01, 2026, 06:52 PM UTC
Duration
4h 8m
Affected: AlloyDB for PostgreSQLApigeeCloud FilestoreCloud RunCloud SpannerGoogle App EngineGoogle BigQueryGoogle Cloud BigtableGoogle Cloud DataflowGoogle Cloud SQLGoogle Compute EngineGoogle Kubernetes EngineHybrid ConnectivityLooker (Google Cloud core)Virtual Private Cloud (VPC)us-central1AlloyDB for PostgreSQL (global)AlloyDB for PostgreSQL (us-central1)Apigee (global)Apigee (us-central1)Cloud Filestore (global)Cloud Filestore (us-central1)Cloud Run (global)Cloud Run (us-central1)Cloud Spanner (global)Cloud Spanner (us-central1)Google App Engine (global)Google App Engine (us-central1)Google BigQuery (global)Google BigQuery (us-central1)Google Cloud Bigtable (global)Google Cloud Bigtable (us-central1)Google Cloud Dataflow (global)Google Cloud Dataflow (us-central1)Google Cloud SQL (global)Google Cloud SQL (us-central1)Google Compute Engine (global)Google Compute Engine (us-central1)Google Kubernetes Engine (global)Google Kubernetes Engine (us-central1)Hybrid Connectivity (global)Hybrid Connectivity (us-central1)Looker (Google Cloud core) (global)Looker (Google Cloud core) (us-central1)Virtual Private Cloud (VPC) (global)Virtual Private Cloud (VPC) (us-central1)
Timeline · 8 updates

Read the full incident report →

Minor September 1, 2026 via Google Ads

Incident affecting Google Ad Manager DAI

Detected by Pingoru
Sep 01, 2026, 02:28 PM UTC
Resolved
Sep 01, 2026, 10:05 PM UTC
Duration
7h 37m
Affected: Google Ad Manager DAI Google Ad Manager DAI (global)
Timeline · 2 updates
  1. monitoring Sep 01, 2026, 04:28 PM UTC

    Google Ad Manager DAI service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access Google Ad Manager DAI, but are seeing error messages, high latency, and/or other unexpected behavior. Ad Manager DAI streams return internal error. Engineering has identified the root cause and deployed a mitigation covering most streams, while work continues to address the remaining impact. There is currently no workaround.

  2. resolved Sep 01, 2026, 10:05 PM UTC

    The problem with Google Ad Manager DAI has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access Google Ad Manager DAI, but are seeing error messages, high latency, and/or other unexpected behavior. Ad Manager DAI stream requests failing with internal errors (4xx or 5xx). The issue is now resolved.

Read the full incident report →

Minor September 1, 2026 via Google Play

Incident affecting Play Billing Purchases, Play Developer Subscriptions and In-App Purchases API and Play Subscriptions Renewal and Management

Detected by Pingoru
Sep 01, 2026, 08:54 AM UTC
Resolved
Sep 01, 2026, 11:43 AM UTC
Duration
2h 49m
Affected: Play Billing PurchasesPlay Developer Subscriptions and In-App Purchases APIPlay Subscriptions Renewal and Management
Timeline · 2 updates
  1. investigating Sep 01, 2026, 11:11 AM UTC

    We're investigating reports of an issue with Play Billing Purchases and Play Subscriptions Renewal and Management. We will provide more information shortly. The affected users are able to access Play Billing Purchases and Play Subscriptions Renewal and Management, but are seeing error messages, high latency, and/or other unexpected behavior.

  2. resolved Sep 01, 2026, 01:59 PM UTC

    The problem with Play Billing Purchases, Play Developer Subscriptions and In-App Purchases API, and Play Subscriptions Renewal and Management has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Major September 1, 2026 via Firebase

RESOLVED: Firebase Cloud Messaging - low availability in North America

Detected by Pingoru
Sep 01, 2026, 08:40 AM UTC
Resolved
Sep 01, 2026, 12:31 PM UTC
Duration
3h 51m
Affected: Cloud MessagingCloud Messaging (global)
Timeline · 3 updates
  1. investigating Sep 01, 2026, 10:29 AM UTC

    We're aware of a problem with Firebase Cloud Messaging affecting its availability and latency in North America. We will provide an update by 04:30AM detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.

  2. investigating Sep 01, 2026, 11:43 AM UTC

    Services are recovering. Next update at 05:30

  3. resolved Sep 01, 2026, 12:53 PM UTC

    The problem has been resolved. All services in scope are back to normal.

Read the full incident report →

Minor September 1, 2026 via Google Play

Incident affecting Play Integrity API

Detected by Pingoru
Sep 01, 2026, 08:00 AM UTC
Resolved
Sep 01, 2026, 12:22 PM UTC
Duration
4h 22m
Affected: Play Integrity API
Timeline · 2 updates
  1. investigating Sep 01, 2026, 03:44 PM UTC

    We're investigating reports of an issue with Play Integrity API. We will provide more information shortly.

  2. resolved Sep 01, 2026, 03:50 PM UTC

    The problem with Play Integrity API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Minor August 28, 2026 via Google Workspace

Incident affecting Google Chat

Detected by Pingoru
Aug 28, 2026, 05:50 PM UTC
Resolved
Aug 28, 2026, 08:34 PM UTC
Duration
2h 44m
Affected: Google Chat
Timeline · 3 updates
  1. monitoring Aug 28, 2026, 07:25 PM UTC

    Description: We are experiencing an intermittent issue with Google Chat Friday, 2026-08-28 10:25 PDT. Our engineering team has investigated the issue and are currently working on mitigating the issue. We will provide more information by Friday, 2026-08-28 14:15 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users are experiencing an issue where they receive notifications for new messages, but the actual messages fail to appear in their chat application unless the user refreshes their view Workaround: Users can refresh to see new messages

  2. resolved Aug 28, 2026, 08:55 PM UTC

    Description: The issue with Google Chat has been resolved for all affected users as of Friday, 2026-08-28 13:45 PDT. From preliminary analysis the issue was triggered due to a recent change which was rolled back to mitigate the impact. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users were experiencing an issue where they received notifications for new messages, but the actual messages failed to appear in their chat application unless the user refreshed their view. Workaround: None as the issue is resolved.

  3. resolved Sep 04, 2026, 03:43 AM UTC

    Google chat: * Delayed message rendering: New messages did not appear in active conversation streams automatically. Users were required to manually refresh their client or send a new message/react to force the stream to synchronize. * Stalled read states and inbox sorting: Background actions, such as updating unread badges and moving active spaces to the top of the inbox, experienced heavy internal error rates and were significantly delayed for users. * Search indexing delays: New messages sent during the outage window stalled in the indexing pipeline, experiencing delays in becoming searchable. Scope exclusions: * No Data Loss: At no point was customer data lost or compromised. All messages transmitted during the incident window were securely captured in primary storage and successfully delivered to conversation streams once the backlog cleared.

Read the full incident report →

Major August 24, 2026 via Google Ads

Incident affecting Google Ad Manager

Detected by Pingoru
Aug 24, 2026, 03:53 AM UTC
Resolved
Aug 24, 2026, 04:59 AM UTC
Duration
1h 6m
Affected: Google Ad Manager Google Ad Manager (global)
Timeline · 2 updates
  1. investigating Aug 24, 2026, 03:55 AM UTC

    We're aware of a problem with Google Ad Manager affecting a majority of users. We will provide an update by Aug 24, 2026, 3:53 AM UTC detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. The Demand Channel Settings page is not loading for users

  2. resolved Aug 24, 2026, 05:00 AM UTC

    The problem with Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The Demand Channel Settings page is now loading for all users

Read the full incident report →

Minor August 20, 2026 via Google Ads

Incident affecting AdMob

Detected by Pingoru
Aug 20, 2026, 09:19 PM UTC
Resolved
Aug 31, 2026, 05:57 PM UTC
Duration
10d 20h
Affected: AdMob AdMob (global)
Timeline · 4 updates
  1. monitoring Aug 20, 2026, 09:24 PM UTC

    We're investigating reports of an issue with AdMob. We will provide more information shortly. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. AdMob rewarded ads fail to play video and instead show a large play icon on Android apps. There is currently no workaround.

  2. monitoring Aug 22, 2026, 01:10 AM UTC

    AdMob service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. AdMob rewarded ads fail to play video and instead show a large play icon on Android apps. Engineering has deployed a mitigation. There is currently no workaround.

  3. monitoring Aug 28, 2026, 05:16 PM UTC

    AdMob service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. AdMob rewarded ads fail to play video and instead show a large play icon on Android apps. Engineering has identified the root cause and deployed a mitigation covering most users, while work continues to address the remaining impact. There is currently no workaround.

  4. resolved Sep 01, 2026, 05:56 AM UTC

    The problem with AdMob has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. AdMob rewarded ads fail to play video and instead show a large play icon on Android apps. The issue is now resolved.

Read the full incident report →

Critical August 20, 2026 via Google Cloud

Incident affecting AlloyDB for PostgreSQL, Apigee Edge Public Cloud and Apigee X

Detected by Pingoru
Aug 20, 2026, 03:40 PM UTC
Resolved
Aug 20, 2026, 07:20 PM UTC
Duration
3h 40m
Affected: AlloyDB for PostgreSQLApigee Edge Public CloudApigee XArtifact RegistryBigQuery Data Transfer ServiceCloud BuildCloud Data FusionCloud FilestoreCloud Key Management ServiceCloud MonitoringCloud RunContact Center AI PlatformDataproc MetastoreGoogle App EngineGoogle BigQueryGoogle Cloud BigtableGoogle Cloud ComposerGoogle Cloud DataflowGoogle Cloud DataprocGoogle Cloud Pub/SubGoogle Cloud SQLGoogle Cloud StorageGoogle Compute EngineGoogle Kubernetes EngineIdentity and Access ManagementManaged Service for Apache KafkaPersistent Diskglobalus-west1AlloyDB for PostgreSQL (global)AlloyDB for PostgreSQL (us-west1)Apigee Edge Public Cloud (global)Apigee Edge Public Cloud (us-west1)Apigee X (global)Apigee X (us-west1)Artifact Registry (global)Artifact Registry (us-west1)BigQuery Data Transfer Service (global)BigQuery Data Transfer Service (us-west1)Cloud Build (global)Cloud Build (us-west1)Cloud Data Fusion (global)Cloud Data Fusion (us-west1)Cloud Filestore (global)Cloud Filestore (us-west1)Cloud Key Management Service (global)Cloud Key Management Service (us-west1)Cloud Monitoring (global)Cloud Monitoring (us-west1)Cloud Run (global)Cloud Run (us-west1)Contact Center AI Platform (global)Contact Center AI Platform (us-west1)Dataproc Metastore (global)Dataproc Metastore (us-west1)Google App Engine (global)Google App Engine (us-west1)Google BigQuery (global)Google BigQuery (us-west1)Google Cloud Bigtable (global)Google Cloud Bigtable (us-west1)Google Cloud Composer (global)Google Cloud Composer (us-west1)Google Cloud Dataflow (global)Google Cloud Dataflow (us-west1)Google Cloud Dataproc (global)Google Cloud Dataproc (us-west1)Google Cloud Pub/Sub (global)Google Cloud Pub/Sub (us-west1)Google Cloud SQL (global)Google Cloud SQL (us-west1)Google Cloud Storage (global)Google Cloud Storage (us-west1)Google Compute Engine (global)Google Compute Engine (us-west1)Google Kubernetes Engine (global)Google Kubernetes Engine (us-west1)Identity and Access Management (global)Identity and Access Management (us-west1)Managed Service for Apache Kafka (global)Managed Service for Apache Kafka (us-west1)Persistent Disk (global)Persistent Disk (us-west1)
Timeline · 9 updates

Read the full incident report →

Critical August 20, 2026 via Google Maps Platform

Incident affecting AlloyDB for PostgreSQL, Apigee Edge Public Cloud and Apigee X

Detected by Pingoru
Aug 20, 2026, 03:40 PM UTC
Resolved
Aug 20, 2026, 07:20 PM UTC
Duration
3h 40m
Affected: AlloyDB for PostgreSQLApigee Edge Public CloudApigee XArtifact RegistryBigQuery Data Transfer ServiceCloud BuildCloud Data FusionCloud FilestoreCloud Key Management ServiceCloud MonitoringCloud RunContact Center AI PlatformDataproc MetastoreGoogle App EngineGoogle BigQueryGoogle Cloud BigtableGoogle Cloud ComposerGoogle Cloud DataflowGoogle Cloud DataprocGoogle Cloud Pub/SubGoogle Cloud SQLGoogle Cloud StorageGoogle Compute EngineGoogle Kubernetes EngineIdentity and Access ManagementManaged Service for Apache KafkaPersistent Diskglobalus-west1AlloyDB for PostgreSQL (global)AlloyDB for PostgreSQL (us-west1)Apigee Edge Public Cloud (global)Apigee Edge Public Cloud (us-west1)Apigee X (global)Apigee X (us-west1)Artifact Registry (global)Artifact Registry (us-west1)BigQuery Data Transfer Service (global)BigQuery Data Transfer Service (us-west1)Cloud Build (global)Cloud Build (us-west1)Cloud Data Fusion (global)Cloud Data Fusion (us-west1)Cloud Filestore (global)Cloud Filestore (us-west1)Cloud Key Management Service (global)Cloud Key Management Service (us-west1)Cloud Monitoring (global)Cloud Monitoring (us-west1)Cloud Run (global)Cloud Run (us-west1)Contact Center AI Platform (global)Contact Center AI Platform (us-west1)Dataproc Metastore (global)Dataproc Metastore (us-west1)Google App Engine (global)Google App Engine (us-west1)Google BigQuery (global)Google BigQuery (us-west1)Google Cloud Bigtable (global)Google Cloud Bigtable (us-west1)Google Cloud Composer (global)Google Cloud Composer (us-west1)Google Cloud Dataflow (global)Google Cloud Dataflow (us-west1)Google Cloud Dataproc (global)Google Cloud Dataproc (us-west1)Google Cloud Pub/Sub (global)Google Cloud Pub/Sub (us-west1)Google Cloud SQL (global)Google Cloud SQL (us-west1)Google Cloud Storage (global)Google Cloud Storage (us-west1)Google Compute Engine (global)Google Compute Engine (us-west1)Google Kubernetes Engine (global)Google Kubernetes Engine (us-west1)Identity and Access Management (global)Identity and Access Management (us-west1)Managed Service for Apache Kafka (global)Managed Service for Apache Kafka (us-west1)Persistent Disk (global)Persistent Disk (us-west1)
Timeline · 9 updates

Read the full incident report →

Minor August 18, 2026 via Google Workspace

Investigating access issues with Classroom’s new web homepage.

Detected by Pingoru
Aug 18, 2026, 07:03 PM UTC
Resolved
Aug 18, 2026, 10:30 PM UTC
Duration
3h 27m
Affected: Classroom
Timeline · 4 updates
  1. monitoring Aug 18, 2026, 07:35 PM UTC

    Description: We are investigating increasing reports of access issues with Classroom’s new web homepage beginning on Thursday, 2026-08-13. Our engineering team is currently working on a potential fix while continuing to investigate the full root cause. We will provide an update by Tuesday, 2026-08-18 13:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Admins and some Teachers may experience permission errors when accessing Classroom’s new web homepage. Workaround: Users should still be able to navigate to other views from the left hand pane of the interface.

  2. monitoring Aug 18, 2026, 08:00 PM UTC

    Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-08-18 14:00 PDT. We will provide more information by Tuesday, 2026-08-18 14:15 PDT. Symptoms: Admins and some Teachers may experience permission errors when accessing Classroom’s new web homepage. Workaround: Users should still be able to navigate to other views from the left hand pane of the interface.

  3. monitoring Aug 18, 2026, 08:27 PM UTC

    Description: Our engineering has identified the cause and mitigation work is currently underway. The mitigation rollout is expected to take several hours. We will provide more information by Wednesday, 2026-08-19 8:00 PDT. Symptoms: Workspace Admins may experience permission errors when accessing Classroom’s web homepage. Remaining Classroom functionality remains unaffected. The Classroom Mobile App and the Classroom API are unaffected by the issue. Workaround: All other pages are unaffected and admins can navigate to other pages using the left hand pane on the interface. Workspace Admins can still create classes without any issue. Workspace Admins can also view the courses that they are in by going to https://classroom.google.com/h/tv

  4. resolved Aug 18, 2026, 11:02 PM UTC

    Description: The issue with Classroom has been resolved for all affected users as of Tuesday, 2026-08-18 15:30 PDT. From preliminary analysis, the issue was triggered due to a recent change which caused the permission mismatch, our Engineering team has rolled out the fix to mitigate the impact. We thank you for your patience while we worked on resolving the issue. Symptoms: Workspace Admins may have experienced permission errors when accessing Classroom’s web homepage. Remaining Classroom functionality remained unaffected. The Classroom Mobile App and the Classroom API were unaffected by the issue. Workaround: None as the issue is resolved

Read the full incident report →

Minor August 18, 2026 via Google Search

August 2026 spam update

Detected by Pingoru
Aug 18, 2026, 04:27 PM UTC
Resolved
Aug 21, 2026, 08:49 AM UTC
Duration
2d 16h
Affected: Ranking
Timeline · 2 updates
  1. monitoring Aug 18, 2026, 04:28 PM UTC

    Released the August 2026 spam update , which applies globally and to all languages. The rollout may take a few days to complete.

  2. resolved Aug 21, 2026, 08:49 AM UTC

    The rollout was complete as of August 21, 2026.

Read the full incident report →

Minor August 15, 2026 via Google Ads

Incident affecting Exchange Platforms

Detected by Pingoru
Aug 15, 2026, 12:24 AM UTC
Resolved
Aug 17, 2026, 11:04 PM UTC
Duration
2d 22h
Affected: Exchange PlatformsExchange Platforms (global)
Timeline · 1 update
  1. monitoring Aug 15, 2026, 12:32 AM UTC

    The problem with Exchange Platforms has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. Some seller entries in the Seller.JSON file were missing domains for a period of a 2-3 days.

Read the full incident report →

Major August 13, 2026 via Firebase

Firebase A/B Testing Issue

Detected by Pingoru
Aug 13, 2026, 05:23 PM UTC
Resolved
Aug 14, 2026, 11:13 AM UTC
Duration
17h 50m
Affected: A/B Testing (Beta)A/B Testing (Beta) (global)
Timeline · 4 updates
  1. investigating Aug 13, 2026, 05:56 PM UTC

    We are investigating an issue with Firebase A/B Testing. Some users are not able to modify or create an experiment. We will provide more information shortly.

  2. investigating Aug 13, 2026, 06:42 PM UTC

    We are still looking into this.

  3. investigating Aug 13, 2026, 08:49 PM UTC

    We are still working on this. Meanwhile, please contact Firebase support for help in case you face any issues with A/B Testing

  4. resolved Aug 14, 2026, 11:14 AM UTC

    The issue with Firebase A/B Testing has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →