Temporal Status

All Systems Operational

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

Jun 20, 2026

No incidents reported today.

Jun 19, 2026

No incidents reported.

Jun 18, 2026

No incidents reported.

Jun 17, 2026

GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls

Resolved - The region has recovered — visibility calls are succeeding without errors. The incident is resolved.
Jun 17, 22:04 UTC

Update - A fix has been implemented. The visibility is coming back and we are monitoring.
Jun 17, 21:34 UTC

Investigating - We are currently investigating this issue.
Jun 17, 21:18 UTC

Jun 16, 2026

Some customers may be experiencing stuck workflows or activities

Resolved - This incident has been resolved.
Jun 16, 21:08 UTC

Update - Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
Jun 16, 21:07 UTC

Update - Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
Jun 16, 21:00 UTC

Update - The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.
Jun 16, 15:56 UTC

Update - Refresh operations across both open and closed workflows are complete in most regions; we continue to make steady progress across the remaining few namespaces in the us-east-1, us-west-2, us-east4, us-west1, us-central1, asia-south1, europe-west3. No additional impact has been observed since mitigation was implemented, and we continue to closely monitor the environment. The next update will be provided once the refresh process has completed.
Jun 11, 20:25 UTC

Update - Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.
Jun 8, 19:02 UTC

Update - Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.
Jun 5, 22:02 UTC

Update - As refresh of closed workflows progresses, some users may see unblocked stuck parent workflows from closed child workflows; this is happening because the missed task for closed child workflows is refreshed and delivered to parent. It could also happen on other stuck workflows that are waiting for task updates which were missed due to this incident.
Jun 4, 22:35 UTC

Update - We are continuing to monitor the ongoing refresh process for all open workflows. We are also considering options for refreshing closed workflows. We will continue to share more updates as this progresses.
Jun 4, 17:40 UTC

Monitoring - Workflows will continue to be refreshed overnight, and we are monitoring the situation.
Jun 4, 07:08 UTC

Update - Workflows will continue to be refreshed overnight, and we are monitoring the situation.
Jun 4, 06:45 UTC

Update - Refreshes are still in progress and we are monitoring the situation.
Jun 4, 06:14 UTC

Update - Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.
Jun 4, 04:27 UTC

Update - The rollback is making progress across impacted cells, and we are continuing to monitor the situation.
Jun 4, 01:40 UTC

Update - Rollback is still in progress and we are continuing to monitor the situation.
Jun 3, 23:36 UTC

Identified - A bug in the recent update in History pagination caused a rare edge case where an extra task could be added before the response was returned. This incorrectly advanced the read level, causing some tasks to be skipped. We’ve identified the issue, and are currently rolling back the update to stop this from happening again.

We will be refreshing all executions in cells where the update was deployed and will monitor these closely. This will progress any stuck workflows, but will not impact any of the closed ones.
Jun 3, 21:35 UTC

Update - We're rolling back the recent update as a possible mitigation to avoid any further occurrences of this issue. We are however still in the process of investigating root cause and will post updates as we have them.
Jun 3, 20:41 UTC

Update - We are investigating a recent update that could have caused intermittent missed task dispatches, resulting in some tasks being stuck. Impact identified as of now is limited to a handful of workflows that were caught in a rare edge case. We will continue to share more updates as investigation progresses.
Jun 3, 19:51 UTC

Update - We are continuing to investigate this issue. Please report any stuck workflows or activities to support so we can help unblock them as we work on root cause investigation and resolution.
Jun 3, 18:30 UTC

Investigating - We are investigating a few reports where a workflow or activity is becoming stuck and not making progress when it should. Please report any such issues you see to support.
Jun 3, 00:45 UTC

Jun 15, 2026

No incidents reported.

Jun 14, 2026

Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.

Resolved - Incident Resolved.
Jun 14, 16:06 UTC

Update - This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
Jun 12, 23:16 UTC

Update - This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.
Jun 12, 20:44 UTC

Monitoring - Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved.

We failed namespaces with MRN out of the cell.

We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
Jun 12, 19:09 UTC

Jun 13, 2026

No incidents reported.

Jun 12, 2026

Jun 11, 2026

Audit logs temporarily delayed for a few hours — no data loss.

Resolved - This has been fixed, and the audit logs have been backfilled.
Jun 11, 20:45 UTC

Identified - We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.
Jun 11, 19:58 UTC

Customers might observe Usage API returning missing or delayed data

Resolved - We have identified the root cause and confirmed that no customer impact occurred.
Jun 11, 15:32 UTC

Investigating - We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.
Jun 11, 14:34 UTC

Jun 10, 2026

No incidents reported.

Jun 9, 2026

GCP customers in us-east4 are experiencing elevated errors for Visibility API calls

Resolved - Namespaces have been failed back to their primary region.
This incident has been resolved
Jun 9, 00:59 UTC

Update - The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.
Jun 8, 23:18 UTC

Update - Multi Region Namespaces were failed over at 10:23 PM UTC
Jun 8, 22:42 UTC

Monitoring - A fix has been implemented and we are monitoring
Jun 8, 22:38 UTC

Investigating - We are currently investigating this issue.
Jun 8, 22:06 UTC

Jun 8, 2026

Jun 7, 2026

No incidents reported.

Jun 6, 2026

Some customers in AWS sa-east-1 may experience elevated API latencies

Resolved - This incident has been resolved.
Jun 6, 04:26 UTC

Monitoring - The issue appears to have been transient network latency that has resolved. We are monitoring the situation.
Jun 6, 02:29 UTC

Investigating - Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.
Jun 6, 02:15 UTC