Alation Cloud Service Outage History
Alation Cloud Service is up right nowPingoru has recorded 34 incidents for Alation Cloud Service: 14 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 30 of 720 (4%) |
| May 2026 | 1 | 3 of 744 (0%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 3 | 2 of 744 (0%) |
| September 2026 | 2 | 3 of 720 (0%) |
| October 2026 | 0 | 0 of 523 (0%) |
Incidents, newest first
Notice September 22, 2026 Third-party provider outage (AWS) US-East-1 6m Americas (US-east) - Dev, Americas (US-east), PoV (Proof of Value)
Started Sep 22, 2026, 12:25 AM UTC· resolved Sep 22, 2026, 12:32 AM UTC
- identified Sep 22, 2026, 12:25 AM UTC
AWS is reporting a service disruption in us-east-1 region, which is affecting one or more of their core services that Alation depends on. Our own systems are healthy, but AWS instability may possibly affect service delivery for our users. Impact: Some users may experience slower response times, timeouts, or failures when using certain features (for example: data catalog search, ingestion jobs, API calls or dashboard refreshes). Data integrity is not impacted; no data loss or corruption has been detected. Queued operations will retry automatically once upstream services recover.
- monitoring Sep 22, 2026, 12:31 AM UTC
AWS has reported the issues has been resolved. Our teams will continue to monitor the environment to ensure continued stability.
- resolved Sep 22, 2026, 12:32 AM UTC
This incident has been resolved.
Critical September 10, 2026 Connectivity Issues: US-East-1 Cluster 2h 25m Americas (US-east)
Started Sep 10, 2026, 12:15 AM UTC· resolved Sep 10, 2026, 02:41 AM UTC
- investigating Sep 10, 2026, 01:29 AM UTC
We are currently investigating connectivity issues affecting services hosted on our US-East-1 (use1) cluster. Some customers may experience delays, timeouts, or intermittent failures when accessing the affected services. Our engineering team is actively investigating the root cause and working to restore full connectivity as quickly as possible. We will post updates here as more information becomes available. If you are experiencing impact, we appreciate your patience while we work to resolve this issue.
- monitoring Sep 10, 2026, 01:53 AM UTC
The connectivity issues affecting services hosted on our US-East-1 (use1) cluster. Alerts are now recovering and we are seeing signs of improvement across affected services. Our engineering team continues to monitor closely to confirm full recovery. We will post another update once systems are fully stable. We appreciate your patience while we complete this monitoring period
- resolved Sep 10, 2026, 02:41 AM UTC
The connectivity issues affecting services hosted on our US-East-1 (use1) cluster have been resolved. All the services are operating normally. We will continue monitoring to ensure stability. If you continue to experience any issues, please reach out to support. Thank you for your patience throughout this incident.
Critical August 20, 2026 Service Disruption – APAC(Sydney) 18m APAC (Sydney)
Started Aug 20, 2026, 10:08 PM UTC· resolved Aug 20, 2026, 10:27 PM UTC
- identified Aug 20, 2026, 10:08 PM UTC
We are currently experiencing a service disruption affecting all customers in the APAC(Sydney) region. Our team has identified the root cause and is actively working on implementing a fix.
- resolved Aug 20, 2026, 10:27 PM UTC
The service disruption has been resolved. All systems are operating normally. We apologize for the inconvenience and thank you for your patience.
Major August 18, 2026 Degraded availability for a subset of customers 55m Americas (US-east)
Started Aug 18, 2026, 04:35 PM UTC· resolved Aug 18, 2026, 05:31 PM UTC
- identified Aug 18, 2026, 04:35 PM UTC
We are currently investigating an issue affecting a limited number of customers. Our team is actively working on a resolution
- monitoring Aug 18, 2026, 04:44 PM UTC
Fix has been implemented and we are actively monitoring the environment to ensure stability. Affected customers should see services restored.
- resolved Aug 18, 2026, 05:31 PM UTC
The issue has been resolved and all affected customers are fully operational. Our team has confirmed stability across the environment.
Major August 10, 2026 Service Disruption: eu-west-1 1h 5m EMEA (Ireland)
Started Aug 10, 2026, 09:15 PM UTC· resolved Aug 10, 2026, 10:20 PM UTC
- investigating Aug 10, 2026, 09:15 PM UTC
We're aware that our eu-west-1 region is currently unavailable, and our team is already on it. We know how important reliable access is, and restoring service is our top priority right now. We'll keep you updated as we make progress — thank you for bearing with us.
- investigating Aug 10, 2026, 09:16 PM UTC
We are continuing to investigate this issue.
- identified Aug 10, 2026, 10:04 PM UTC
We've identified the cause of the issue affecting our eu-west-1 region and are working on a fix. We'll share another update shortly. Thank you for your patience.
- monitoring Aug 10, 2026, 10:15 PM UTC
A fix has been implemented and eu-west-1 is now operating normally. We're monitoring closely to confirm full stability. Thank you for your patience.
- resolved Aug 10, 2026, 10:20 PM UTC
The issue affecting our eu-west-1 region has been fully resolved and all services are operating normally. Thank you for your patience throughout, and we apologize for any inconvenience caused.
Notice June 10, 2026 Service Disruption — Alation Cloud 38m
Started Jun 10, 2026, 10:30 AM UTC· resolved Jun 10, 2026, 11:08 AM UTC
- resolved Jun 10, 2026, 03:47 PM UTC
A few customers might not have been able to access the platform due to a brief service interruption on the Alation instance in the US-East 1 cluster. Due to an infrastructure problem on our end, your Alation instance was momentarily unavailable on June 10, 2026, between roughly 4:04 PM and 4:38 PM IST (10:34–11:08 UTC). Errors may have occurred when users tried to access the platform during this window. By 4:38 PM IST (11:08 UTC), every system had fully recovered.
Minor May 20, 2026 Data Products Service — Elevated Latency and Errors 3h 26m Americas (US-east) - Dev, Americas (US-east)
Started May 20, 2026, 03:38 PM UTC· resolved May 20, 2026, 07:04 PM UTC
- investigating May 20, 2026, 03:38 PM UTC
We are investigating elevated latency and intermittent errors affecting the Data Products and Alation AI. Other Alation functionality is unaffected. Mitigations are in progress and our team is actively working to identify the root cause.
- identified May 20, 2026, 04:07 PM UTC
We have identified the root cause of the elevated latency affecting Data Products and Alation AI. The team is working on mitigation.
- monitoring May 20, 2026, 05:25 PM UTC
The underlying issue has been mitigated. Data Products and Alation AI are returning to normal operation. We are continuing to monitor service health to confirm full recovery.
- resolved May 20, 2026, 07:04 PM UTC
This incident has been resolved. Data Products and Alation AI are operating normally. A detailed RCA will be shared shortly.
Minor April 24, 2026 Service Disruption Affecting Agent Interactions 1d 5h Americas (US-east), Americas (US-west), Canada (Montreal), EMEA (Ireland) and 5 more
Started Apr 24, 2026, 01:00 AM UTC· resolved Apr 25, 2026, 06:52 AM UTC
- investigating Apr 24, 2026, 02:38 PM UTC
We recently experienced a service disruption that caused agent interactions to fail. The issue was traced to an expired token, which prevented a backend service from writing query results to storage. We have applied a temporary mitigation by recycling the affected tenant, which has restored normal functionality. Our team is actively working on a permanent fix to prevent this issue from recurring. Impact: This issue affected agent interactions only. All other platform functionality remained unaffected
- identified Apr 24, 2026, 02:39 PM UTC
We have applied a temporary mitigation by recycling the affected tenant, which has restored normal functionality. Our team is actively working on a permanent fix to prevent this issue from recurring.
- monitoring Apr 24, 2026, 05:47 PM UTC
The issue causing agent interaction failures has been resolved, and the agent system is now fully functional. We are actively monitoring system health to ensure continued stability.
- resolved Apr 25, 2026, 06:52 AM UTC
This incident has been resolved.
Notice April 23, 2026 Alation Service Degradation - Catalog editor – Americas (US-east) - Dev, Americas (US-east), Americas (US-west), Americas (US-west) - Dev and 15 more
Started Apr 23, 2026, 03:57 PM UTC· resolved Apr 23, 2026, 03:57 PM UTC
- resolved Apr 23, 2026, 03:57 PM UTC
We discovered an issue where Rich Text Editor fields across the Catalog are not displaying content correctly. The issue has been resolved by rolling back the problematic deployment.
Notice March 11, 2026 Alation service degradation - Alation agent 6h 35m Americas (US-east), Americas (US-west)
Started Mar 11, 2026, 11:47 PM UTC· resolved Mar 12, 2026, 06:23 AM UTC
- monitoring Mar 11, 2026, 11:47 PM UTC
A service interruption to Alation agent was encountered by some customers in the US-East-1 and US-West-2 regions. The service interruption has been remediated, and we are monitoring the status.
- resolved Mar 12, 2026, 06:23 AM UTC
We have not seen the error reoccur in the last few hours; we are marking the incident as resolved.
Major February 19, 2026 Alation Service Degradation 9h 40m Americas (US-east)
Started Feb 19, 2026, 11:01 AM UTC· resolved Feb 19, 2026, 08:42 PM UTC
- investigating Feb 19, 2026, 11:01 AM UTC
We are investigating reports of degraded performance affecting the Alation service. We will update as soon as we have more information available.
- identified Feb 19, 2026, 11:39 AM UTC
We are actively investigating the incident; preliminary analysis suggests a fault within the hosted control plane that caused downstream impact across multiple Alation services. Service recovery is now underway and metrics indicate stabilization.
- monitoring Feb 19, 2026, 11:51 AM UTC
The issue originating from the hosted control plane has been mitigated. All impacted Alation services have been fully restored and are operating normally. We will continue to monitor system stability and will share a detailed RCA once the investigation is complete
- identified Feb 19, 2026, 01:49 PM UTC
We are currently investigating a recurrence of the issue affecting Alation services. A downstream service is intermittently returning HTTP 500 errors, resulting in service failures and renewed impact. Our team is actively analyzing the issue and working to mitigate the impact. We will provide further updates as additional information becomes available.
- monitoring Feb 19, 2026, 02:48 PM UTC
Services have fully recovered, and we are no longer observing customer impact. The issue was related to underlying infrastructure instability within our cloud environment, which led to downstream service disruption. We are actively working with our cloud provider to complete the root cause analysis and ensure preventive measures are implemented.
- monitoring Feb 19, 2026, 03:22 PM UTC
We continue to observe intermittent instability related to the underlying cloud infrastructure. We are actively working with the cloud provider to investigate the cause of this intermittent behaviour and to implement corrective measures. Our teams remain engaged and are closely monitoring the environment. We will provide further updates as more information becomes available.
- monitoring Feb 19, 2026, 05:37 PM UTC
All services are currently operational. Some customers may still experience intermittent slowness while remediation efforts continue. We are actively working with AWS to address the underlying infrastructure instability, and our internal engineering teams are simultaneously reviewing application functionality to ensure stability and performance. We remain focused on driving the environment to full recovery and are closely monitoring service health. Further updates will be shared as progress continues.
- resolved Feb 19, 2026, 08:42 PM UTC
Our investigation determined that the incident was driven by IOPS saturation on a few compute nodes in one of the node groups in the us-east-1 region. This condition impacted a subset of our infrastructure and contributed to intermittent downstream service errors for a handful of customers in this region. As part of remediation, we will be increasing the provisioned IOPS capacity for the impacted node group to provide additional IO headroom and improve overall resilience. We are also working closely with AWS to analyse the underlying increase in disk usage further and validate long-term corrective measures. Services are currently stable. We are continuing to monitor closely to ensure sustained reliability. We apologise for the inconvenience and will follow up with a detailed root cause analysis.
Minor February 2, 2026 Degraded Service - Alation. 3h 49m Americas (US-east)
Started Feb 02, 2026, 01:01 PM UTC· resolved Feb 02, 2026, 04:51 PM UTC
- investigating Feb 02, 2026, 02:01 PM UTC
Alation service has recovered for most tenants and is operating normally. However, a limited number of tenants are still experiencing service disruption (login failures, timeouts, or degraded performance). Our engineering team is actively working with priority to restore service for the remaining affected tenants.
- identified Feb 02, 2026, 02:18 PM UTC
Service has been restored for the majority of tenants. We have identified an issue affecting a small subset of tenants that are still experiencing errors and/or degraded performance. Targeted remediation is in progress to recover the remaining impacted tenants.
- identified Feb 02, 2026, 03:01 PM UTC
Most tenants have recovered. A small subset of tenants still remains impacted; we’re continuing targeted remediation
- monitoring Feb 02, 2026, 03:24 PM UTC
Service has been restored for the tenants that experienced failures. We are actively monitoring the infrastructure and application to validate expected behaviour.
- resolved Feb 02, 2026, 04:51 PM UTC
Incident resolved. We’ll continue routine monitoring and will follow up if anything changes.”
Notice October 21, 2025 Metadata extraction / QLI failures with BAD REQUEST HTTP response headers 3h 38m Americas (US-east) - Dev, Americas (US-east)
Started Oct 21, 2025, 05:26 PM UTC· resolved Oct 21, 2025, 09:04 PM UTC
- investigating Oct 21, 2025, 05:26 PM UTC
We are currently investigating an issue with the MDE Pipeline service, which is preventing data extraction and causing errors. The error is related to a timeout connection to the pipeline service. Our team is working to resolve the issue as quickly as possible. We will keep you posted with the progress as it becomes available.
- identified Oct 21, 2025, 06:35 PM UTC
Cause has been identified and fix implemented. Working on resolution.
- resolved Oct 21, 2025, 09:04 PM UTC
Fix has been implemented and confirmed to successfully resolve the issue. Root cause was result of AWS US-East-1 outage from previous day (Monday, October 20).
Minor October 20, 2025 Service Degradation for EU Customers 4h 39m EMEA (Ireland)
Started Oct 20, 2025, 09:45 AM UTC· resolved Oct 20, 2025, 02:25 PM UTC
- identified Oct 20, 2025, 02:18 PM UTC
We are investigating reports of degraded performance impacting customers in the EU region.
- identified Oct 20, 2025, 02:20 PM UTC
A subset of EU customers may experience: Slower load times or timeouts when accessing the Alation application. Delays in query execution, search indexing, and accessing catalog services
- resolved Oct 20, 2025, 02:25 PM UTC
The issue that was impacting customers in the EU region has been resolved, system performance is showing normal performance, and the services are now operating normally.
Critical October 20, 2025 Third-party provider outage (AWS) 2h 19m Americas (US-east) - Dev, Americas (US-east)
Started Oct 20, 2025, 07:40 AM UTC· resolved Oct 20, 2025, 10:00 AM UTC
- identified Oct 20, 2025, 08:07 AM UTC
We have detected elevated error rates and degraded performance across parts of the Alation platform. This is caused by a service disruption at AWS, which is affecting one or more of their core services that Alation depends on. Our own systems are healthy, but upstream instability is affecting service delivery for our users. Impact: Some users may experience slower response times, timeouts, or failures when using certain features (for example: data catalog search, ingestion jobs, API calls or dashboard refreshes). Data integrity is not impacted; no data loss or corruption has been detected. Queued operations will retry automatically once upstream services recover.
- identified Oct 20, 2025, 09:52 AM UTC
AWS states that they are still working on finding the root cause and actively working on the issue.
- monitoring Oct 20, 2025, 09:54 AM UTC
AWS further reports “significant signs of recovery”: most requests should now be succeeding, though some services still have latency and backlog to clear. We see early signs of Alation service recovery; we will keep you updated.
- resolved Oct 20, 2025, 10:00 AM UTC
The underlying AWS service has recovered, and all Alation services have returned to normal operation for affected customers. Our teams will continue to monitor the environment to ensure continued stability.
Notice July 16, 2025 Latency across multiple regions 5h Americas (US-east) - Dev, Americas (US-east), Americas (US-west), Americas (US-west) - Dev and 15 more
Started Jul 16, 2025, 03:59 PM UTC· resolved Jul 16, 2025, 08:59 PM UTC
- investigating Jul 16, 2025, 03:59 PM UTC
Our engineering teams are working to identify the issue and are actively working to mitigate the impact. We will provide updates here every 30 minutes or as new information becomes available.
- monitoring Jul 16, 2025, 06:25 PM UTC
We have identified and deployed a fix across all tenants and are monitoring performance.
- resolved Jul 16, 2025, 08:59 PM UTC
This incident has been resolved.
Notice July 15, 2025 Investigating latency across multiple regions 13h 28m Americas (US-east) - Dev, Americas (US-east), Americas (US-west), Americas (US-west) - Dev and 15 more
Started Jul 15, 2025, 04:27 PM UTC· resolved Jul 16, 2025, 05:56 AM UTC
- investigating Jul 15, 2025, 04:27 PM UTC
We are currently investigating reports of latency across multiple regions. This is impacting availability and performance for some customers using our services. Our engineering teams are working to identify the issue and are actively working to mitigate the impact. We will provide updates here every 30 minutes or as new information becomes available.
- monitoring Jul 15, 2025, 05:23 PM UTC
We have implemented a revised memory configuration, resulting in enhanced system stability and reduced latency. We will continue monitoring through the day and provide updates as appropriate.
- monitoring Jul 15, 2025, 08:56 PM UTC
We are continuing to monitor environments for issues.
- resolved Jul 16, 2025, 05:56 AM UTC
This incident has been resolved.
Major July 14, 2025 Investigating connectivity issues 1h 38m Americas (US-east) - Dev, Americas (US-east), Americas (US-west), Americas (US-west) - Dev and 15 more
Started Jul 14, 2025, 04:53 PM UTC· resolved Jul 14, 2025, 06:32 PM UTC
- investigating Jul 14, 2025, 04:53 PM UTC
We are currently experiencing a service disruption across all regions. This is impacting availability and performance for some customers using our services. Our engineering teams are working to identify the issue and are actively working to mitigate the impact. We will provide updates here every 30 minutes or as new information becomes available.
- identified Jul 14, 2025, 05:47 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 14, 2025, 06:31 PM UTC
The problem has been resolved, and all of our applications are now working properly. We are constantly monitoring the system.
- resolved Jul 14, 2025, 06:32 PM UTC
This incident has been resolved.
Minor June 4, 2025 We are experiencing connectivity issue on the US Cluster 3h 11m Americas (US-east)
Started Jun 04, 2025, 08:20 AM UTC· resolved Jun 04, 2025, 11:31 AM UTC
- investigating Jun 04, 2025, 08:20 AM UTC
We are currently experiencing a service disruption in the us-east1 region. This is impacting availability and performance for some customers using our services hosted in this region. Our engineering teams are working to identify the issue and are actively working to mitigate the impact. We will provide updates here every 30 minutes or as new information becomes available.
- identified Jun 04, 2025, 08:53 AM UTC
Our investigation revealed the issue originated from underlying infrastructure limitations. We have scaled up resources in the affected region and are monitoring for stability.
- monitoring Jun 04, 2025, 08:56 AM UTC
All impacted customers are back online. Our team is actively monitoring the systems to ensure everything remains stable and performs as expected.
- resolved Jun 04, 2025, 11:31 AM UTC
This incident has been resolved.
Minor May 5, 2025 Alation Cloud Service - DEV unavailable for some customers in US region 3d 3h Americas (US-east) - Dev, Americas (US-west) - Dev
Started May 05, 2025, 05:30 AM UTC· resolved May 08, 2025, 08:36 AM UTC
- investigating May 05, 2025, 07:56 AM UTC
We have discovered a problem with the US cluster's DEV tenants' sporadic availability, and we are currently investigating the cause.
- investigating May 05, 2025, 08:02 AM UTC
We are working on it, and the matter is still being investigated. We will update when we have further info.
- identified May 05, 2025, 10:01 AM UTC
We have identified the issue as being with the cache cluster, and we are working with our vendor to resolve the issue. We will update more information as it becomes available.
- identified May 05, 2025, 02:01 PM UTC
We have added additional resources to the cluster and are waiting on the rebalancing of the cluster.
- identified May 05, 2025, 02:12 PM UTC
We’re still seeing elevated connection activity within our application, which impacts the Dev tenants in the US cluster. Our team is actively investigating and working on a fix. We apologize for the inconvenience and appreciate your patience.
- identified May 05, 2025, 04:45 PM UTC
Our team is actively working on a hotfix to resolve the ongoing issue. We will update as soon as the fix is ready for release. We appreciate your understanding and patience.
- identified May 06, 2025, 01:05 PM UTC
Our team is actively working on a hotfix to address the issue and it's currently undergoing testing. We will share another update as soon as the hotfix has passed validation and is ready for deployment.
- identified May 07, 2025, 03:05 PM UTC
The hotfix has successfully passed initial validation and is currently undergoing performance testing. Our team is monitoring the results closely to ensure it meets all stability and reliability standards. We will provide another update once testing is complete and the hotfix is ready for deployment.
- identified May 07, 2025, 04:34 PM UTC
We are currently preparing for the patch rollout and ensuring all systems are ready for a smooth deployment. Our team is finalizing the necessary steps, and we will share another update once we are ready to begin the rollout
- identified May 07, 2025, 11:40 PM UTC
Minor release 2025.1.2.1 with a fix for the issue impacting Dev tenants has been released. Deployment is scheduled for 5:00 PM PDT.
- monitoring May 08, 2025, 05:17 AM UTC
We have initiated the deployment of the hotfix (version 2025.1.2.1) . This rollout is being conducted in phases to ensure stability across all systems. Our team is actively monitoring the process and will provide updates as it progresses.
- monitoring May 08, 2025, 05:17 AM UTC
The hotfix (version 2025.1.2.1) has been successfully rolled out. At this time, all systems are operating as expected. Our team will continue to monitor the infrastructure closely to ensure ongoing stability and performance. We’ll share further updates if needed.
- resolved May 08, 2025, 08:36 AM UTC
The issue has been fully resolved. The hotfix has been deployed successfully, and all systems are stable. We will continue to monitor as part of our standard operations. Thank you for your patience throughout this process.
Major November 27, 2024 Alation Cloud Service unavailable for some customers in ap-southeast-2 region 45m APAC (Sydney)
Started Nov 27, 2024, 01:00 AM UTC· resolved Nov 27, 2024, 01:45 AM UTC
- investigating Nov 27, 2024, 01:00 AM UTC
ACS is unavailable for some customers in Sydney region. The issue has been identified and engineers are working on remediation.
- monitoring Nov 27, 2024, 01:23 AM UTC
Issue has been identified and a fix has been implemented. We are monitoring the results.
- resolved Nov 27, 2024, 05:51 AM UTC
The incident that was affecting the ACS service has been resolved.
Minor October 31, 2024 Long Running MDE/QLI jobs failing in US-WEST-2 1d 8h Americas (US-west)
Started Oct 31, 2024, 10:26 PM UTC· resolved Nov 02, 2024, 07:18 AM UTC
- investigating Oct 31, 2024, 10:26 PM UTC
We are currently investigating an issue which impacts long running QLI/MDE jobs in the ACS US-WEST.
- resolved Nov 02, 2024, 07:18 AM UTC
This incident has been resolved. Infrastructure maintenance has been completed.
Minor October 29, 2024 Metadata Extraction failure with read timeout to airflow cluster - Elevated Error 1d 19h Americas (US-east), Americas (US-west), Canada (Montreal), EMEA (Ireland) and 4 more
Started Oct 29, 2024, 11:30 PM UTC· resolved Oct 31, 2024, 06:38 PM UTC
- investigating Oct 30, 2024, 06:39 PM UTC
We are currently investigating an issue with the MDE Pipeline service, which is preventing data extraction and causing errors. The error is related to a timeout connection to the pipeline service. Our team is working to resolve the issue as quickly as possible. We will keep you posted with the progress as it becomes available.
- investigating Oct 30, 2024, 08:17 PM UTC
The issue is impacting US-east region only. All other regions are fully operational. Following error message may be seen in impacted region. "HTTPConnectionPool(host='airflow-pipeline-service.default.svc.cluster.local', port=80): Read timed out. (read timeout=1800) "
- monitoring Oct 31, 2024, 03:40 AM UTC
Our engineering team has successfully resolved the issue causing the timeout connection to the Airflow pipeline service, and the system is now functioning as expected.
- resolved Oct 31, 2024, 06:38 PM UTC
The incident had been resolved and we have not seen the error reoccur during our monitoring period.
Critical October 28, 2024 Connectivity issue in us-west-2 1h 19m Americas (US-west), Americas (US-west) - Dev
Started Oct 28, 2024, 11:56 AM UTC· resolved Oct 28, 2024, 01:15 PM UTC
- investigating Oct 28, 2024, 11:56 AM UTC
Connectivity issue affecting the US-West-2 region. We are working to resolve it as quickly as possible and will provide updates shortly.
- identified Oct 28, 2024, 12:08 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 28, 2024, 12:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 28, 2024, 01:15 PM UTC
This incident has been resolved.