Google Security Products Status Dashboard

Google Security Products Status Dashboard
Incidents
Google SecOps customers using Bindplane agents configured with HTTPS endpoints are experiencing intermittent drop in ingestion volume in US multi-region, asia-south-1 and me-central-1. It’s possible customers in other regions may experience the issue.

This page provides status information on the services that are part of Google Security Products. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. For additional information on these services, please visit https://cloud.google.com/security.

Available
Service information
Service disruption
Service outage

Incident affecting Google SecOps

Google SecOps customers using Bindplane agents configured with HTTPS endpoints are experiencing intermittent drop in ingestion volume in US multi-region, asia-south-1 and me-central-1. It’s possible customers in other regions may experience the issue.

Incident began at 2026-02-23 06:00 and ended at 2026-02-23 14:00 (all times are US/Pacific).

Previously affected location(s)

Mumbai (asia-south1)Doha (me-central1)Multi-region: us

Date Time Description

	Date	Time	Description
	24 Feb 2026	14:14 PST	Summary Google SecOps customers using Bindplane agents configured with HTTPS endpoints may experience intermittent drop in ingestion volume in US multi-region, asia-south-1 and me-central-1. It’s possible that customers in other regions may experience the issue as well. Description A fix is now available for customers experiencing issues with Google SecOps customers using Bindplane agents configured with HTTPS. The impacted customers should update to Bindplane Collector v1.94.2 which resolves the issue by enqueuing the data retrying when 429s occur. This release is available in GitHub and when installing the agent through the Bindplane UI. If the data still exist at the log source, customers should try to recollect that data. For example: with Windows Events Source, the Start at Beginning setting in the Bindplane receiver, can be used to recollect the potentially lost events. We thank you for your patience while we worked on resolving the issue. Customer Symptoms How to Monitor if you are impacted: If you are using Bindplane HTTPS then follow below- Go to your GCP project on the SIEM settings APIs & Services Select Chronicle APIs Select only `ImportLogs` in methods Look for any 429 errors in `Traffic by response code` Workaround None at this time.
	24 Feb 2026	11:55 PST	Description We are experiencing intermittent issues with Google SecOps for customers using HTTPS endpoints using Bindplane, symptoms began Monday, 2026-02-23 06:00 PST and continued for approximately one hour. The issue reoccurred on Tuesday, 2026-02-24 06:00 PST, for approximately one hour. The issue has been intermittent since then. SecOps started returning HTTP 429 errors to certain customers for a limited period of time, which led to the Bindplane agent dropping logs. Our engineering team and Bindplane’s engineering team have identified the issue and are working on a fix. We will provide more information by Tuesday, 2026-02-24 15:30 PST with current details. We apologize to all who are affected by the disruption. Diagnosis/Symptoms How to Monitor if you are impacted: If you are using Bindplane HTTPS then follow below- Go to your GCP project on the SIEM settings APIs & Services Select Chronicle APIs select only `ImportLogs` in methods Look for any 429 errors in `Traffic by response code` Workaround None at this time.

24 Feb 2026

14:14 PST

Summary

Google SecOps customers using Bindplane agents configured with HTTPS endpoints may experience intermittent drop in ingestion volume in US multi-region, asia-south-1 and me-central-1. It’s possible that customers in other regions may experience the issue as well.

Description

A fix is now available for customers experiencing issues with Google SecOps customers using Bindplane agents configured with HTTPS. The impacted customers should update to Bindplane Collector v1.94.2 which resolves the issue by enqueuing the data retrying when 429s occur. This release is available in GitHub and when installing the agent through the Bindplane UI.

If the data still exist at the log source, customers should try to recollect that data. For example: with Windows Events Source, the Start at Beginning setting in the Bindplane receiver, can be used to recollect the potentially lost events.

We thank you for your patience while we worked on resolving the issue.

Customer Symptoms

How to Monitor if you are impacted:

If you are using Bindplane HTTPS then follow below-

Go to your GCP project on the SIEM settings
APIs & Services
Select Chronicle APIs
Select only ImportLogs in methods

Look for any 429 errors in Traffic by response code

Workaround

None at this time.

24 Feb 2026

11:55 PST

Description

We are experiencing intermittent issues with Google SecOps for customers using HTTPS endpoints using Bindplane, symptoms began Monday, 2026-02-23 06:00 PST and continued for approximately one hour. The issue reoccurred on Tuesday, 2026-02-24 06:00 PST, for approximately one hour. The issue has been intermittent since then.

SecOps started returning HTTP 429 errors to certain customers for a limited period of time, which led to the Bindplane agent dropping logs.

Our engineering team and Bindplane’s engineering team have identified the issue and are working on a fix.

We will provide more information by Tuesday, 2026-02-24 15:30 PST with current details.

We apologize to all who are affected by the disruption.

Diagnosis/Symptoms

How to Monitor if you are impacted:

If you are using Bindplane HTTPS then follow below-

Go to your GCP project on the SIEM settings
APIs & Services
Select Chronicle APIs
select only ImportLogs in methods

Look for any 429 errors in Traffic by response code

Workaround

None at this time.

All times are US/Pacific