Is Atlan Down?

This incident has been resolved. Between approximately 22:35 and 00:21 UTC, our upstream cloud infrastructure provider experienced elevated failures launching new compute instances across the us-west-2 region, caused by a subsystem supporting storage volumes required during instance launch. Our provider completed remediation and has confirmed full recovery, and all of their services are operating normally. During this window, workflows for some tenants hosted in us-west-2 were delayed because new compute capacity could not start. All affected tenants recovered automatically once launches were restored, and delayed workflows have resumed and completed processing. The Atlan UI, search and APIs were not affected at any point. If any workflow run failed or did not complete during this window, please re-run it. No other action is required. --- [2026-11-07T00:41:23Z] (monitoring) All affected tenants in the us-west-2 region have recovered. New compute capacity is starting successfully, and delayed workflows have resumed and are processing normally. The Atlan UI, search and APIs were not affected at any point. Our upstream cloud infrastructure provider has identified the underlying cause as a subsystem supporting storage volumes required when launching new compute instances in the us-west-2 region. They are seeing early signs of recovery and continue to work on fully restoring launches; existing running infrastructure was not affected. Their next update is expected by 01:30 UTC. Until the provider confirms full resolution, we are pausing any non-essential infrastructure changes in us-west-2 and will continue to monitor closely. Further updates will follow. --- [2026-11-07T00:34:20Z] (monitoring) All affected tenants in the us-west-2 region have recovered. New compute capacity is starting successfully, and delayed workflows have resumed and are processing normally. The Atlan UI, search and APIs were not affected at any point. Our upstream cloud infrastructure provider has not yet declared the underlying issue fully resolved, so we will continue to monitor closely until they confirm. Further updates will follow. --- [2026-11-07T00:05:26Z] (identified) Our upstream cloud infrastructure provider has confirmed an ongoing operational issue in the us-west-2 region: elevated failures when launching new compute instances, caused by a problem with their block storage service. This is also affecting several other services that depend on it in that region. As a result, new compute capacity cannot start, and workflows for some tenants hosted in us-west-2 are delayed. The Atlan UI, search and APIs are not affected. Our provider is actively working on mitigation. Workflows will resume automatically once capacity is restored, and no action is required from customers. We are monitoring closely, and further updates will follow. --- [2026-11-06T23:49:15Z] (identified) We have identified an issue with our upstream infrastructure provider in the us-west-2 region that is preventing new compute capacity from starting. As a result, some tenants hosted in us-west-2 may see workflows (including automations and background jobs) delayed or not starting. The Atlan UI, search and APIs are not affected. Our provider is working on mitigation, and we are monitoring closely. Workflows will resume automatically once capacity is restored; no action is needed from customers. We will post another update within 60 minutes or sooner as we learn more.

Google Cloud has confirmed the power event in europe-west2-b has been mitigated for the vast majority of customers, and we have independently verified that all affected Atlan tenant workloads are healthy, functional, and fully reachable. We are marking this incident as resolved. We apologize for the disruption this caused and thank you for your patience. A full post-incident summary will follow once Google Cloud publishes their final root-cause analysis. If you continue to experience problems, please contact support@atlan.com. --- [2026-10-20T13:26:47Z] (monitoring) Following GCP's mitigation of the power event in europe-west2-b, all affected Atlan tenant workloads are confirmed healthy and fully functional. External reachability checks are passing normally across all affected domains. We are continuing to monitor and will mark this incident resolved once Google Cloud confirms full recovery on their end. --- [2026-10-20T12:44:29Z] (monitoring) Following GCP's mitigation of the power event in europe-west2-b, our external health checks across affected services are now passing. We are continuing to monitor node and workload recovery internally and will post a final update once we're confident the incident is fully resolved. --- [2026-10-20T12:11:37Z] (monitoring) GCP has confirmed the root cause of this incident: a power event in the europe-west2-b zone beginning 2026-10-19 23:08 PDT. The power event has been mitigated and GCP is now recovering existing workloads. New workload creation in the zone may still be unavailable. GCP's tentative full-recovery estimate for existing workloads is 2026-10-20 06:00 PDT (~6:30pm IST). We are monitoring node and service recovery on our side and will post again once services are confirmed restored. --- [2026-10-20T08:26:50Z] (identified) We are aware of a Google Cloud infrastructure incident affecting network connectivity for Compute Engine instances in the `europe-west2-b` zone. Google Cloud Engineering is actively working to restore connectivity. Persistent disks and data remain safe. We will provide updates as more information becomes available.

This incident has been resolved. The connectivity errors affecting a small number of Atlan instances hosted in the Azure UAE North region were caused by a network routing issue at an upstream provider, which caused some requests to fail with gateway errors (HTTP 522/523). We applied a mitigation that restored access to the affected instances while the provider worked on a fix. The provider has since confirmed the issue is resolved, and we have returned all affected instances to their standard configuration. All instances are reachable and working normally. Instances in other regions were not affected. --- [2026-10-06T13:09:26Z] (monitoring) We've applied a mitigation that routes traffic for the affected instances around the impacted upstream network path. Connectivity has been restored, and we're watching closely to confirm stability. --- [2026-10-06T13:00:47Z] (investigating) We're looking into connectivity errors on a small number of Atlan instances hosted in the Azure UAE North region. Some requests to the affected hostnames are failing with gateway errors (HTTP 523). Production instances in other region are currently reachable and working normally.We're working with that provider and putting a mitigation in place. We'll post another update within 30 minutes or as soon as we know more.