Google Outage History

Started Apr 29, 2026, 06:30 PM UTC· resolved Apr 29, 2026, 08:45 PM UTC

1. investigating Apr 29, 2026, 07:17 PM UTC

   Description: We are experiencing an issue with Classroom beginning at Wednesday, 2026-04-29 11:30 PDT. Our engineering team continues to investigate the issue. We will provide more information by Wednesday, 2026-04-29 13:00 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

2. monitoring Apr 29, 2026, 07:53 PM UTC

   Description: Our engineering team has identified the cause and working on mitigation of the issue . The mitigation is expected to complete by Wednesday, 2026-04-29 15:00 PDT. We will provide more information by Wednesday, 2026-04-29 15:15 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

3. monitoring Apr 29, 2026, 08:13 PM UTC

   Description: A fix has been deployed, and services have stabilized for the majority of users. We are aware that a small subset of users may still encounter errors. Our engineering team is actively working on a secondary resolution to address these remaining users. Full resolution for remaining users is expected to complete by Wednesday, 2026-04-29 14:00 PDT. We will provide an update by Wednesday, 2026-04-29 14:15 PDT with current details. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

4. resolved Apr 29, 2026, 09:07 PM UTC

   Description: A fix has been deployed, and services have stabilized for all users. The issue with Google Classroom has been resolved for all affected users as of Wednesday, 2026-04-29 13:45 PDT. The issue was due to an internal software migration. Our engineers have mitigated the issue by rolling back the migration for impacted users. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected users may have experienced issues accessing the classroom. Workaround: The issue is resolved.

Read the full incident report →

Started Apr 28, 2026, 08:27 PM UTC· resolved Apr 30, 2026, 06:59 AM UTC

1. investigating Apr 28, 2026, 08:29 PM UTC

   Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.

2. resolved Apr 29, 2026, 07:53 AM UTC

   The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Started Apr 28, 2026, 07:30 AM UTC· resolved Apr 28, 2026, 03:50 PM UTC

1. monitoring Apr 28, 2026, 03:20 PM UTC

   Description: We are experiencing an issue with AppSheet beginning at Tuesday, 2026-04-28 00:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-04-28 09:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.

2. monitoring Apr 28, 2026, 04:00 PM UTC

   Description: Our engineering team has implemented a fix and system telemetry indicates that latency and error rates have returned to normal levels. We are continuing to monitor the environment closely to ensure full stability. We will provide an update by Tuesday, 2026-04-28 10:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.

3. resolved Apr 28, 2026, 04:50 PM UTC

   Description: The issue with AppSheet has been resolved for all affected users as of Tuesday, 2026-04-28 08:50 PDT. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers would have experienced slow loading times and internal server errors for AppSheet apps.

Read the full incident report →

Started Apr 10, 2026, 02:08 AM UTC· resolved Apr 10, 2026, 02:50 PM UTC

1. investigating Apr 10, 2026, 10:07 AM UTC

   Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

2. investigating Apr 10, 2026, 10:55 AM UTC

   Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 05:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

3. investigating Apr 10, 2026, 11:27 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-04-10 09:00 PDT. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

4. resolved Apr 10, 2026, 03:06 PM UTC

   Description: The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

Read the full incident report →

Started Apr 09, 2026, 04:59 PM UTC· resolved Apr 09, 2026, 09:00 PM UTC

1. investigating Apr 09, 2026, 05:00 PM UTC

   We're investigating the issue and determining the cause

2. investigating Apr 09, 2026, 05:12 PM UTC

   We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests

3. resolved Apr 09, 2026, 08:57 PM UTC

   We believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue

Read the full incident report →

Started Apr 09, 2026, 12:01 PM UTC· resolved Apr 09, 2026, 10:00 PM UTC

1. investigating Apr 09, 2026, 06:09 PM UTC

   No updates so far

2. resolved Apr 10, 2026, 12:09 AM UTC

   Problem appears to be mitigated and the error rates are back to normal level.

Read the full incident report →

Started Apr 09, 2026, 07:00 AM UTC· resolved Apr 10, 2026, 07:00 AM UTC

1. investigating Apr 10, 2026, 08:56 AM UTC

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

2. resolved Apr 10, 2026, 08:57 AM UTC

   The problem with Content API for Shopping and Feeds has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access Content API for Shopping and Feeds, but are seeing error messages, high latency, and/or other unexpected behavior.

Read the full incident report →

Started Apr 08, 2026, 09:05 PM UTC· resolved Apr 08, 2026, 10:40 PM UTC

1. investigating Apr 08, 2026, 10:22 PM UTC

   Description: Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details Customer symptoms: Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. Workaround: None at this time.

2. resolved Apr 08, 2026, 11:27 PM UTC

   Description: The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. Workaround: None at this time.

Read the full incident report →

Started Apr 08, 2026, 01:30 PM UTC· resolved Apr 08, 2026, 09:40 PM UTC

1. investigating Apr 08, 2026, 06:22 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

2. investigating Apr 08, 2026, 07:02 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 13:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

3. investigating Apr 08, 2026, 08:03 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 15:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

4. investigating Apr 08, 2026, 09:49 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning on Wednesday, 2026-04-08 06:30 PDT. Our engineering team has applied the mitigation, and our internal monitoring indicates that delays and errors have subsided. We will continue to monitor for service stability to ensure full recovery. We will provide an update by Wednesday, 2026-04-08 16:00 PDT with current details. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.

5. resolved Apr 08, 2026, 10:54 PM UTC

   Description: The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.

6. resolved Apr 10, 2026, 02:32 AM UTC

   Preliminary Incident Report We apologize for the inconvenience this Gmail service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: Account Suspension: One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. Traffic Blocking: A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

7. resolved Apr 17, 2026, 09:10 AM UTC

   Incident Report Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: External Mail Provider Reachout: Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

Read the full incident report →

Started Mar 31, 2026, 07:00 PM UTC· resolved Apr 01, 2026, 06:00 AM UTC

1. investigating Apr 01, 2026, 04:21 AM UTC

   Test Lab ARM devices are experiencing elevated failures rates and delays to test results.

2. resolved Apr 01, 2026, 06:09 AM UTC

   This issue appears to be resolved now. Error rates are back to normal.

Read the full incident report →

Started Mar 27, 2026, 09:00 AM UTC· resolved Apr 08, 2026, 01:00 PM UTC

1. monitoring Mar 27, 2026, 09:14 AM UTC

   Released the March 2026 core update . The rollout may take up to 2 weeks to complete.

2. resolved Apr 08, 2026, 01:12 PM UTC

   The rollout was complete as of April 8, 2026.

Read the full incident report →

Started Mar 24, 2026, 07:00 PM UTC· resolved Mar 25, 2026, 02:30 PM UTC

1. monitoring Mar 24, 2026, 07:18 PM UTC

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

2. resolved Mar 25, 2026, 02:39 PM UTC

   The rollout was complete as of March 25, 2026.

Read the full incident report →

Started Mar 23, 2026, 09:46 PM UTC· resolved Mar 31, 2026, 11:30 AM UTC

1. investigating Mar 31, 2026, 01:34 AM UTC

   Firebase Hosting is aware of missing metrics and logs from Cloud Logging.

2. investigating Mar 31, 2026, 01:35 AM UTC

   Firebase Hosting engineers are working on backfilling missing Cloud Logging entries from 2026-03-23 21:46 UTC to 2026-03-30 16:04 UTC. The ETA is about 11:30 UTC March 31 for that process to complete.

3. resolved Mar 31, 2026, 03:32 PM UTC

   The logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.

Read the full incident report →

Started Mar 20, 2026, 10:30 PM UTC· resolved Mar 21, 2026, 05:03 AM UTC

1. investigating Mar 21, 2026, 03:19 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

2. investigating Mar 21, 2026, 03:46 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

3. investigating Mar 21, 2026, 05:33 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation. We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

4. resolved Mar 21, 2026, 07:17 AM UTC

   Description: The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Mar 17, 2026, 07:00 AM UTC· resolved Mar 17, 2026, 02:10 PM UTC

1. investigating Mar 20, 2026, 01:05 PM UTC

   A recent change is causing 404 errors for clients who send messages to a URL which includes a trailing slash (/v1/projects/my-project/messages:send/ vs /v1/projects/my-project/messages:send). We are in the process of rolling back this change. For clients that are impacted, removing the trailing slash from the send URL will immediately resolve the problem.

2. resolved Mar 20, 2026, 02:40 PM UTC

   The rollback is complete - service is fully restored.

Read the full incident report →

Started Mar 13, 2026, 12:00 PM UTC· resolved Mar 13, 2026, 02:30 PM UTC

1. monitoring Mar 13, 2026, 01:58 PM UTC

   Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. Our engineering teams are actively working to mitigate the impact. We will provide an update by Friday, 2026-03-13 08:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

2. monitoring Mar 13, 2026, 02:34 PM UTC

   Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. We have confirmed that the issue affecting Google Drive is now mitigated. Users should no longer experience unavailability when accessing or interacting with Drive files. Our engineering teams continue to actively work on mitigating the remaining impacted products. We will provide an update by Friday, 2026-03-13 09:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

3. resolved Mar 13, 2026, 02:56 PM UTC

   Description: The issue with Google Workspace has been resolved for all affected users as of Friday, 2026-03-13 07:30 PDT. From preliminary analysis, the incident was triggered by resource contention in the impacted location, following a recent update. This led to elevated error rates and latency for several Workspace products. Our engineering teams mitigated the impact by increasing infrastructure capacity,performing traffic restarts, and rolling back the identified change We thank you for your patience while we worked to resolve this issue. Customer symptoms: A subset of customers may have experienced elevated error rates when accessing the impacted products in the US region. Workaround: NA. Issue is now mitigated

Read the full incident report →

Started Mar 10, 2026, 05:51 PM UTC· resolved Mar 31, 2026, 07:00 AM UTC

1. investigating Mar 11, 2026, 05:59 PM UTC

   Investigating: We are aware of a service disruption affecting App Hosting deployments from Firebase Studio. Impact: Users are currently unable to publish apps with App Hosting from Firebase Studio. Action: Our engineers are currently working to identify the root cause and restore deployment functionality as quickly as possible. We will provide an update as soon as we can. Workaround: In the meantime, you can publish using the Firebase App Hosting console or the Firebase CLI. Learn more at https://firebase.google.com/docs/app-hosting/get-started .

2. resolved Apr 02, 2026, 06:49 PM UTC

   This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.

Read the full incident report →

Started Mar 10, 2026, 02:51 PM UTC· resolved Mar 10, 2026, 04:43 PM UTC

1. resolved Mar 10, 2026, 03:59 PM UTC

   We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

Read the full incident report →

Started Mar 10, 2026, 01:52 PM UTC· resolved Mar 14, 2026, 10:46 AM UTC

1. investigating Mar 13, 2026, 01:55 PM UTC

   Firebase Crashlytics is currently experiencing delays exporting data to BigQuery. Data from 03/09 and onwards have not been exported. We are currently investigating ways to expedite the export.

2. resolved Mar 14, 2026, 10:47 AM UTC

   All BigQuery export jobs for Firebase Crashlytics have caught up.

Read the full incident report →

Started Mar 08, 2026, 06:05 PM UTC· resolved Mar 31, 2026, 07:00 AM UTC

1. investigating Mar 13, 2026, 06:14 PM UTC

   We're aware of a problem with FCM affecting some users. We will provide an update by 13:00 PDT detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.

2. investigating Mar 13, 2026, 07:56 PM UTC

   We are continuing to investigate this issue. We will provide an update by 18:00 PDT detailing when we expect to resolve the problem.

3. investigating Mar 14, 2026, 02:58 AM UTC

   We are continuing to investigate this issue. We will provide updates in the next few days, but we believe the issue is quite minor and should not be a problem for most customers. Thank you for your patience.

4. investigating Mar 16, 2026, 11:15 PM UTC

   We have pinpointed the issue and are actively working on a resolution; only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.

5. investigating Mar 30, 2026, 02:14 PM UTC

   We are actively working on a resolution. Only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.

6. resolved Apr 01, 2026, 05:23 PM UTC

   The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.

Read the full incident report →

Started Mar 05, 2026, 04:50 PM UTC· resolved Mar 05, 2026, 07:30 PM UTC

1. investigating Mar 05, 2026, 06:32 PM UTC

   We are investigating increased errors when connecting to GitHub in us-east5. This is believed to affect automatic and manual deploys from GitHub as well as updating commit statuses with GitHub checks. As a workaround, you may deploy from local source using the Firebase command line tools.

2. resolved Mar 05, 2026, 08:23 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Feb 27, 2026, 12:37 PM UTC· resolved Feb 27, 2026, 02:35 PM UTC

1. monitoring Feb 27, 2026, 04:12 PM UTC

   Symptom: \ Customers experienced increased error rates when sending API requests to impacted multiple Gemini models through the global endpoint.

2. resolved Mar 04, 2026, 11:23 PM UTC

   Preliminary Incident Report We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support. Date/Time of the Issue (All time US/Pacific) Incident Start: 27 February 2026 04:37 Incident End: 27 February 2026 06:35 Duration: 1 hour, 58 minutes Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models (including Gemini 2.0, 2.5, and 3.0 previews) experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, the Vertex Gemini API and Dialogflow CX in US regions and the global endpoint for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. This configuration change enabled a code path that interacted poorly with specific requests, leading to service disruption for the safety filtering service. This in turn led to customers seeing overload (429 and 503) errors for their queries. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation Google engineers were alerted to the service disruption via automated alert on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change for a safety filtering service and initiated a rollback to restore the previous stable configuration. Additionally, engineers added more capacity to the service. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: - Affected Models: All Gemini versions were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. - Error Experience: - PayGo Customers: Experienced primarily 429 Resource Exhausted errors. - Provisioned Throughput (PT) Customers: Received 503 Service Unavailable errors. - For PT customers, most errors stopped at 06:00. For PayGo customers, most errors stopped at 06:20. - Geographic Scope: Global endpoint, us-central1, us-east4, and other US regions were impacted.

3. resolved Mar 09, 2026, 05:25 AM UTC

   Incident Report Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, Vertex Gemini API and Dialogflow CX in US regions and the global endpoint. The issue persisted for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we have taken immediate steps to improve the platform’s performance and availability. Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. For some specific requests, this created code paths that eventually led to service disruptions and capacity loss for the safety filtering service. Consequently, customers encountered overload (429 and 503) errors for their queries, with some users reporting elevated error rates for specific models in US regions. Remediation and Prevention Google engineers were alerted to the issue via our automated monitoring system on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change and initiated a rollback to restore the previous stable configuration. Engineers also added more capacity to the service to stabilize it. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. \ \ Google is committed to preventing a repeat of this issue and is taking the following actions: * Reinforcing rollout processes to include mandatory validation checkpoints. * Improving alerting systems to monitor critical dependencies more closely. Detailed Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: * Affected Models: All Vertex AI Gemini API models were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. * Error Experience: * PayGo Customers: Experienced primarily 429 Resource Exhausted errors. * Provisioned Throughput (PT) Customers: Received 503 Service Unavailable errors. * For PT customers, most errors stopped at 06:00. For PayGo customers, most errors stopped at 06:20. * Geographic Scope: Global endpoint, us-central1, us-east4, and other US regions were impacted.

Read the full incident report →

Started Feb 27, 2026, 12:37 PM UTC· resolved Feb 27, 2026, 02:35 PM UTC

1. monitoring Feb 27, 2026, 04:12 PM UTC

   Symptom: \ Customers experienced increased error rates when sending API requests to impacted multiple Gemini models through the global endpoint.

2. resolved Mar 04, 2026, 11:23 PM UTC

   Preliminary Incident Report We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support. Date/Time of the Issue (All time US/Pacific) Incident Start: 27 February 2026 04:37 Incident End: 27 February 2026 06:35 Duration: 1 hour, 58 minutes Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models (including Gemini 2.0, 2.5, and 3.0 previews) experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, the Vertex Gemini API and Dialogflow CX in US regions and the global endpoint for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. This configuration change enabled a code path that interacted poorly with specific requests, leading to service disruption for the safety filtering service. This in turn led to customers seeing overload (429 and 503) errors for their queries. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation Google engineers were alerted to the service disruption via automated alert on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change for a safety filtering service and initiated a rollback to restore the previous stable configuration. Additionally, engineers added more capacity to the service. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: - Affected Models: All Gemini versions were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. - Error Experience: - PayGo Customers: Experienced primarily 429 Resource Exhausted errors. - Provisioned Throughput (PT) Customers: Received 503 Service Unavailable errors. - For PT customers, most errors stopped at 06:00. For PayGo customers, most errors stopped at 06:20. - Geographic Scope: Global endpoint, us-central1, us-east4, and other US regions were impacted.

3. resolved Mar 09, 2026, 05:25 AM UTC

   Incident Report Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, Vertex Gemini API and Dialogflow CX in US regions and the global endpoint. The issue persisted for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we have taken immediate steps to improve the platform’s performance and availability. Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. For some specific requests, this created code paths that eventually led to service disruptions and capacity loss for the safety filtering service. Consequently, customers encountered overload (429 and 503) errors for their queries, with some users reporting elevated error rates for specific models in US regions. Remediation and Prevention Google engineers were alerted to the issue via our automated monitoring system on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change and initiated a rollback to restore the previous stable configuration. Engineers also added more capacity to the service to stabilize it. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. \ \ Google is committed to preventing a repeat of this issue and is taking the following actions: * Reinforcing rollout processes to include mandatory validation checkpoints. * Improving alerting systems to monitor critical dependencies more closely. Detailed Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: * Affected Models: All Vertex AI Gemini API models were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. * Error Experience: * PayGo Customers: Experienced primarily 429 Resource Exhausted errors. * Provisioned Throughput (PT) Customers: Received 503 Service Unavailable errors. * For PT customers, most errors stopped at 06:00. For PayGo customers, most errors stopped at 06:20. * Geographic Scope: Global endpoint, us-central1, us-east4, and other US regions were impacted.

Read the full incident report →

Started Feb 26, 2026, 02:11 PM UTC· resolved Feb 26, 2026, 03:11 PM UTC

1. resolved Mar 02, 2026, 10:17 PM UTC

   For approximately 1 hour starting at 06:11 PST on February 26, 2026, Firebase App Hosting backends in europe-west4 were seeing elevated errors on un-cached content due to increased network congestion and elevated requests. The issue was resolved for all affected projects as of 07:10 PST. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

Read the full incident report →

Started Feb 25, 2026, 03:55 AM UTC· resolved Feb 25, 2026, 04:10 AM UTC

1. investigating Feb 25, 2026, 06:33 AM UTC

   Serving was experiencing an issue.

2. resolved Feb 25, 2026, 06:34 AM UTC

   We fixed the issue with serving search results. There will be no more updates.

Read the full incident report →