Temporal Status

Customers in GCP us-east4 may experience elevated API latencies

Update - We are continuing to monitor for any further issues.
Jul 09, 2026 - 18:56 UTC

Update - We are continuing to monitor for any further issues.
Jul 08, 2026 - 00:05 UTC

Monitoring - We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic.
Jul 07, 2026 - 23:53 UTC

Update - We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4.

We will provide further updates within one hour.
Jul 07, 2026 - 22:20 UTC

Identified - We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.
Jul 07, 2026 - 19:14 UTC

Update - We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.
Jul 07, 2026 - 18:21 UTC

Investigating - Customers in GCP us-east4 may experience elevated API latencies.
Jul 07, 2026 - 13:00 UTC

Amazon Web Services (AWS) Operational

ap-northeast-1 Operational

ap-northeast-2 Operational

ap-south-1 Operational

ap-south-2 Operational

ap-southeast-1 Operational

ap-southeast-2 Operational

ca-central-1 Operational

eu-central-1 Operational

eu-west-1 Operational

eu-west-2 Operational

sa-east-1 Operational

us-east-1 Operational

us-east-2 Operational

us-west-2 Operational

Google Cloud Provider (GCP) Operational

asia-south1 Operational

europe-west3 Operational

us-east4 Operational

us-central1 Operational

us-west1 Operational

asia-southeast2 Operational

Global Services Operational

Web UI Operational

Cloud Ops API Operational

Metrics Operational

Namespace Management Operational

Auth(n)/Auth(z) Operational

Audit Logging Operational

Export History Operational

Billing Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Jul 10, 2026

No incidents reported today.

Jul 9, 2026

Some customers in AWS us-west-2 may experience unjustified throttling errors

Resolved - This incident has been resolved.
Jul 9, 16:25 UTC

Investigating - Some customers in AWS us-west-2 may experience unjustified throttling errors.
Jul 9, 16:08 UTC

Jul 8, 2026

Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies

Resolved - A set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.
Jul 8, 21:47 UTC

Monitoring - The service has remained stable since 15:00 UTC.

We continue to investigate the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are monitoring for any further occurrences.
Jul 8, 19:07 UTC

Investigating - We are currently investigating the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are working to mitigate any recurring impact.
Jul 8, 16:46 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Jul 8, 16:00 UTC

Identified - The issue has been identified and a fix is being implemented.
Jul 8, 15:44 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Jul 8, 15:28 UTC

Investigating - Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Jul 8, 14:26 UTC

Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies

Resolved - This incident has been resolved.
Jul 8, 10:14 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Jul 8, 02:45 UTC

Investigating - Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Jul 8, 02:40 UTC

Some customers in AWS us-east-1 may experience elevated rate of transient API errors

Resolved - This incident has been resolved.
Jul 8, 10:04 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Jul 8, 00:59 UTC

Investigating - Some customers in AWS us-east-1 may experience elevated rate of transient API errors.
Jul 7, 23:25 UTC

Jul 7, 2026

Some customers in GCP europe-west3 may experience elevated API latencies

Resolved - This incident has been resolved.
Jul 7, 07:29 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Jul 7, 06:05 UTC

Identified - Some customers in GCP europe-west3 may experience elevated API latencies from 05:54 to 06:05 UTC
Jul 7, 05:54 UTC

Jul 6, 2026

No incidents reported.

Jul 5, 2026

Some customers in AWS us-east-2 may have experienced elevated API latencies and errors

Resolved - This incident has been resolved.
Jul 5, 19:38 UTC

Monitoring - Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC
Jul 5, 18:41 UTC

Some customers in GCP us-west1 may have experienced elevated API latencies

Resolved - Some customers in GCP us-west1 may have experienced elevated API latencies between 17:50 and 17:57 UTC.
Jul 5, 18:31 UTC

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions

Resolved - The rollout is complete and resolves the compression issues. All listed affected versions should no longer experience any compression-related errors.
Jul 2, 16:26 UTC

Monitoring - The fix has been rolled out across all regions, and we are actively monitoring.
Jul 2, 13:55 UTC

Update - Fix is being rolled out across all regions, current impact is limited to us-west-2 and us-east-1 regions. All systems stable and we're actively monitoring this. Next update will be posted once rollouts completed.
Jul 1, 22:12 UTC

Identified - Customers on the latest SDK versions may see decompression errors when calling the GetSystemInfo and gRPC health check endpoints, and in rare cases, some workflows may hit a non-determinism error (NDE) during replay. A fix for this is rolling out.

Affected versions -

Java 1.36.0
Go 1.45.0
TypeScript 1.19.0
Rust 0.5.0
Python 1.29.0

Workaround - Disable gzip compression in the SDK client (set gRPC compression to none)
Jul 1, 18:02 UTC

Jul 1, 2026

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.