{"page":{"id":"01KN858NJKF1NW5FX72VHGX8D1","name":"Astro","url":"https://status.astronomer.io/","updated_at":"2026-09-04T06:07:24Z"},"incidents":[{"id":"01M1N67NVTBCAEETQPS70AQ8JR","name":"Increased auth errors","status":"resolved","created_at":"2026-09-04T03:08:43Z","updated_at":"2026-09-04T06:07:24Z","resolved_at":"2026-09-04T06:07:24Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01M1NGEVZC26DJM7YSJ97HD3XS","body":"The issue has been fully resolved. All services, including authentication, deployment access, and DAG visibility, are operating normally.\n\nWe apologize for the disruption and thank you for your patience.","created_at":"2026-09-04T06:07:24Z","display_at":"2026-09-04T06:07:24Z","incident_id":"01M1N67NVTBCAEETQPS70AQ8JR","status":"resolved","updated_at":"2026-09-04T06:07:24Z"},{"id":"01M1NFNHDQJWAMG853XT407672","body":"We identified and resolved an infrastructure configuration issue that was causing authentication failures and deployment access errors across the platform. The root cause was a network configuration change during an  infrastructure upgrade that temporarily disrupted connectivity between our control plane and customer deployments.\nThe fix has been applied and initial validation confirms services are recovering\n\nWe are actively monitoring to confirm full recovery across all affected deployments. If you are still experiencing issues, please contact support.","created_at":"2026-09-04T05:53:34Z","display_at":"2026-09-04T05:53:34Z","incident_id":"01M1N67NVTBCAEETQPS70AQ8JR","status":"monitoring","updated_at":"2026-09-04T05:53:34Z"},{"id":"01M1NC6CACGYRY5YG04JPDJ86J","body":"The potential root cause identified, and fix is underway","created_at":"2026-09-04T04:52:52Z","display_at":"2026-09-04T04:52:52Z","incident_id":"01M1N67NVTBCAEETQPS70AQ8JR","status":"identified","updated_at":"2026-09-04T04:52:52Z"},{"id":"01M1NATF9N373SMK1KE9JEGG6V","body":"We're continuing to investigate the issue affecting access/auth to some deployments and services. We will follow up with an update no later than 5:30 AM UTC on Friday, September 4, 2026, or sooner if we have something to share.","created_at":"2026-09-04T04:28:53Z","display_at":"2026-09-04T04:28:53Z","incident_id":"01M1N67NVTBCAEETQPS70AQ8JR","status":"investigating","updated_at":"2026-09-04T04:28:53Z"},{"id":"01M1N67NVTRF6D2GHF8Q5APZ0S","body":"We are currently investigating an issue affecting deployment access, authentication, and related services for multiple customers. Some users may experience 401 errors when using organization-based Astronomer URLs (ORG_ID.astronomer.run), as well as \"RBAC: access denied\" errors or difficulty viewing DAGs in the Astronomer UI.","created_at":"2026-09-04T03:08:43Z","display_at":"2026-09-04T03:08:43Z","incident_id":"01M1N67NVTBCAEETQPS70AQ8JR","status":"investigating","updated_at":"2026-09-04T03:08:43Z"}]},{"id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","name":"Potential impact to Astro deployments in GCP us-central1","status":"resolved","created_at":"2026-09-01T18:40:02Z","updated_at":"2026-09-01T22:29:52Z","resolved_at":"2026-09-01T22:29:51Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01M1FHFMP4Z9G2TZXEJQ290XGP","body":"The GCP incident is marked as Closed officially","created_at":"2026-09-01T22:29:51Z","display_at":"2026-09-01T22:29:51Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"resolved","updated_at":"2026-09-01T22:29:51Z"},{"id":"01M1FBBJPQR7NXDH6J4JGPYRDR","body":"Google Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC.\n\nDuring this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.\n\nThis issue has since been resolved by Google, but we are continuing to monitor the situation internally to ensure it's resolution.","created_at":"2026-09-01T20:42:47Z","display_at":"2026-09-01T20:42:47Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"monitoring","updated_at":"2026-09-01T20:42:47Z"},{"id":"01M1F6KRTD8M18DAP5TD2W48T7","body":"Google Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC.\n\nDuring this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.","created_at":"2026-09-01T19:19:52Z","display_at":"2026-09-01T19:19:52Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"monitoring","updated_at":"2026-09-01T19:19:52Z"},{"id":"01M1F5SGGFTD0FE8P24R3BXMY0","body":"We are investigating a Google Cloud networking incident that began around 14:41 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.\n\nFor more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev \"Google Cloud status incident\").","created_at":"2026-09-01T19:05:32Z","display_at":"2026-09-01T19:05:32Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"investigating","updated_at":"2026-09-01T19:05:32Z"},{"id":"01M1F4J41PBPB9VCEZJJK2DDDW","body":"We are currently investigating a Google Cloud networking incident that began around 16:03 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.\n\nFor more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev \"Google Cloud status incident\").","created_at":"2026-09-01T18:44:01Z","display_at":"2026-09-01T18:44:01Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"investigating","updated_at":"2026-09-01T18:44:01Z"},{"id":"01M1F4G89ZJ3T6FQ5BHD9JFZ5Q","body":"We are currently investigating a Google Cloud networking incident that began around 16:03 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.\n\nFor more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev \"Google Cloud status incident\").","created_at":"2026-09-01T18:43:00Z","display_at":"2026-09-01T18:43:00Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"investigating","updated_at":"2026-09-01T18:43:00Z"},{"id":"01M1F4ATPJVVAMRN7CS6Q5AN1M","body":"We are currently investigating a Google Cloud networking incident that may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.\n\nFor more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev \"Google Cloud status incident\").","created_at":"2026-09-01T18:40:02Z","display_at":"2026-09-01T18:40:02Z","incident_id":"01M1F4ATPJ2SJ49XG8EXN9MTZB","status":"investigating","updated_at":"2026-09-01T18:40:02Z"}]},{"id":"01M0B3EMK58DTX2DW16S9RNHV5","name":"Incorrect scheduler heartbeat metrics being reported","status":"investigating","created_at":"2026-08-18T18:51:59Z","updated_at":"2026-08-18T18:51:59Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01M0B3EMK500NA5RQR70RJJ66W","body":"Our metrics pipeline is falsely displaying spikes in scheduler heartbeat metrics, despite underlying component health. ","created_at":"2026-08-18T18:51:59Z","display_at":"2026-08-18T18:51:59Z","incident_id":"01M0B3EMK58DTX2DW16S9RNHV5","status":"investigating","updated_at":"2026-08-18T18:51:59Z"}]},{"id":"01M09HD09CG69RBJWCQ2ZHM4BP","name":"Intermittent task instances failures.","status":"resolved","created_at":"2026-08-18T04:17:17Z","updated_at":"2026-08-18T07:36:15Z","resolved_at":"2026-08-18T07:36:15Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01M09WSARX2RXDNCZQZN82R0WD","body":"Rollout has been completed","created_at":"2026-08-18T07:36:15Z","display_at":"2026-08-18T07:36:15Z","incident_id":"01M09HD09CG69RBJWCQ2ZHM4BP","status":"resolved","updated_at":"2026-08-18T07:36:15Z"},{"id":"01M09HEA6NTDS97SW5VR1JTEMD","body":"Fix is being rolled out across all astro deployments.","created_at":"2026-08-18T04:18:00Z","display_at":"2026-08-18T04:18:00Z","incident_id":"01M09HD09CG69RBJWCQ2ZHM4BP","status":"monitoring","updated_at":"2026-08-18T04:18:00Z"},{"id":"01M09HD09C8MJAZW71BEGKBSYA","body":"We have identified an issue affecting an internal rollout related to the `pre_execute` Airflow hook in Astro Hosted. We have identified a fix and are rolling it out across the fleet. We are monitoring the rollout and will provide further updates as it progresses.","created_at":"2026-08-18T04:17:17Z","display_at":"2026-08-18T04:17:17Z","incident_id":"01M09HD09CG69RBJWCQ2ZHM4BP","status":"investigating","updated_at":"2026-08-18T04:17:17Z"}]},{"id":"01KZ6N8GP1FVGTB8WPZ7WT98PR","name":"KPO podspec changes for GPU-enabled nodes may cause KPO pod startup failures","status":"resolved","created_at":"2026-08-04T15:11:19Z","updated_at":"2026-08-04T16:40:54Z","resolved_at":"2026-08-04T16:40:54Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KZ6TCJB93RDVSWK3STESYJSM","body":"Mitigations have been successful. A Platform release that corrects this errant behavior is being worked on now. Issue is resolved.","created_at":"2026-08-04T16:40:54Z","display_at":"2026-08-04T16:40:54Z","incident_id":"01KZ6N8GP1FVGTB8WPZ7WT98PR","status":"resolved","updated_at":"2026-08-04T16:40:54Z"},{"id":"01KZ6NFVKMV2W6PNMTPMRXJ5DY","body":"We have rolled back the changes that triggered this issue and are monitoring the issue for confirmation that this issue is resolved.","created_at":"2026-08-04T15:15:19Z","display_at":"2026-08-04T15:15:19Z","incident_id":"01KZ6N8GP1FVGTB8WPZ7WT98PR","status":"monitoring","updated_at":"2026-08-04T15:15:19Z"},{"id":"01KZ6N8GP1FHZG1JAEVDPZ8PT5","body":"We've identified a change that enabled GPU support for KubernetesPodOperator pods had an unintended side effect when reading pod specs without proper limits set in the expected format.\n\nWe're working on a fix, if you notice any unexpected failures for KPO tasks in your Astro deployments, please open a support ticket.","created_at":"2026-08-04T15:11:19Z","display_at":"2026-08-04T15:11:19Z","incident_id":"01KZ6N8GP1FVGTB8WPZ7WT98PR","status":"identified","updated_at":"2026-08-04T15:11:19Z"}]},{"id":"01KZ6DM59A3EPVFYXNV8G6CH6H","name":"Intermittent Delays Managing Airflow Deployments in Azure Central US","status":"resolved","created_at":"2026-08-04T12:57:52Z","updated_at":"2026-08-04T14:36:21Z","resolved_at":"2026-08-04T14:36:21Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KZ6K8GEQB8PJYFZ69M736DVX","body":"This interruption has been resolved.","created_at":"2026-08-04T14:36:21Z","display_at":"2026-08-04T14:36:21Z","incident_id":"01KZ6DM59A3EPVFYXNV8G6CH6H","status":"resolved","updated_at":"2026-08-04T14:36:21Z"},{"id":"01KZ6FPF3D6W9014VZAX08AXRV","body":"Affected clusters have recovered and are operating normally. We are continuing to monitor the environment to ensure service stability.","created_at":"2026-08-04T13:34:04Z","display_at":"2026-08-04T13:34:04Z","incident_id":"01KZ6DM59A3EPVFYXNV8G6CH6H","status":"monitoring","updated_at":"2026-08-04T13:34:04Z"},{"id":"01KZ6DM59AGT1D4N45JYPKYM6P","body":"We are investigating intermittent connectivity issues affecting clusters in Azure Central US when calling Astronomer APIs. This may prevent or delay attempts to create, update, or delete Airflow Deployments. Our engineering team is actively investigating the issue and working to restore normal service.","created_at":"2026-08-04T12:57:52Z","display_at":"2026-08-04T12:57:52Z","incident_id":"01KZ6DM59A3EPVFYXNV8G6CH6H","status":"investigating","updated_at":"2026-08-04T12:57:52Z"}]},{"id":"01KYSW7GC5H1S4AE1ADFAVKNQK","name":"Platform Log ingestion issue","status":"resolved","created_at":"2026-07-30T16:02:58Z","updated_at":"2026-07-30T22:38:19Z","resolved_at":"2026-07-30T22:38:19Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KYTJVCW5FCG8553MERACXQ3Z","body":"Ingestion lag is back at baseline","created_at":"2026-07-30T22:38:19Z","display_at":"2026-07-30T22:38:19Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"resolved","updated_at":"2026-07-30T22:38:19Z"},{"id":"01KYTFXYZ9TG7PW94SFAX527CK","body":"We are continuing to see progress as the log injestions works through the backlog. Available logs are now about ~20mins old, and we expect to see that latency return to normal baseline in the next 2 hours.","created_at":"2026-07-30T21:47:17Z","display_at":"2026-07-30T21:47:17Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"monitoring","updated_at":"2026-07-30T21:47:17Z"},{"id":"01KYTA3CR21HT4N13QN9G0NS23","body":"We continue to see log ingestion improving on the platform, and we're continuing to monitor the situation.","created_at":"2026-07-30T20:05:23Z","display_at":"2026-07-30T20:05:23Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"monitoring","updated_at":"2026-07-30T20:05:23Z"},{"id":"01KYT6QBK6MZ2AJKDMWS27NBV6","body":"We are beginning to see ingestion catch up with backlog log load. Customers may begin to see some logs becoming available in the Cloud UI","created_at":"2026-07-30T19:06:23Z","display_at":"2026-07-30T19:06:23Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"monitoring","updated_at":"2026-07-30T19:06:23Z"},{"id":"01KYT5CJRZHVWHYX17N96N4SJY","body":"We are continuing to investigate and monitor this issue.","created_at":"2026-07-30T18:43:02Z","display_at":"2026-07-30T18:43:02Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"identified","updated_at":"2026-07-30T18:43:02Z"},{"id":"01KYT33WRAW4143151Z0BXZ6XZ","body":"We have identified the source of increased log generation volume, which is causing issues on the ingestion side. We're implementing mitigations now and are monitoring the results.","created_at":"2026-07-30T18:03:20Z","display_at":"2026-07-30T18:03:20Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"identified","updated_at":"2026-07-30T18:03:20Z"},{"id":"01KYSXZXZD093SSEQ1VR1FG1WV","body":"We are continuing to investigate this issue, and will provide another update in 30mins or as new information is available.","created_at":"2026-07-30T16:33:47Z","display_at":"2026-07-30T16:33:47Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"investigating","updated_at":"2026-07-30T16:33:47Z"},{"id":"01KYSW7GC5B704C0N29V3P2X8X","body":"We are currently investigating an issue with platform log ingestion for Astro. Logs may not be available in the Cloud UI.","created_at":"2026-07-30T16:02:58Z","display_at":"2026-07-30T16:02:58Z","incident_id":"01KYSW7GC5H1S4AE1ADFAVKNQK","status":"investigating","updated_at":"2026-07-30T16:02:58Z"}]},{"id":"01KWZAK2QDJ50ZJ6B1ZP23C9Z9","name":"Node Scaling Issue in Azure EastUS2 Region","status":"resolved","created_at":"2026-07-07T22:18:46Z","updated_at":"2026-07-07T22:47:19Z","resolved_at":"2026-07-07T22:47:19Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KWZC7BQ4HPM304S061MRK7EC","body":"The incident is fully resolved and all Azure clusters in EastUS2 are functioning as expected.","created_at":"2026-07-07T22:47:19Z","display_at":"2026-07-07T22:47:19Z","incident_id":"01KWZAK2QDJ50ZJ6B1ZP23C9Z9","status":"resolved","updated_at":"2026-07-07T22:47:19Z"},{"id":"01KWZC5DEXW07TB7ETQCSMCJGY","body":"Engineers observe that affected clusters are returning to \"healthy\" status.","created_at":"2026-07-07T22:46:15Z","display_at":"2026-07-07T22:46:15Z","incident_id":"01KWZAK2QDJ50ZJ6B1ZP23C9Z9","status":"monitoring","updated_at":"2026-07-07T22:46:15Z"},{"id":"01KWZAK2QDHB55HDSY6T075MSD","body":"We have detected node scaling issues in the Azure EastUS2 region and are currently investigating.","created_at":"2026-07-07T22:18:46Z","display_at":"2026-07-07T22:18:46Z","incident_id":"01KWZAK2QDJ50ZJ6B1ZP23C9Z9","status":"investigating","updated_at":"2026-07-07T22:18:46Z"}]},{"id":"01KWVKCDM7BXXGN6JQHY1D8S4D","name":"Node Scaling issues in AWS us-east-1 region","status":"resolved","created_at":"2026-07-06T11:35:27Z","updated_at":"2026-07-06T16:06:06Z","resolved_at":"2026-07-06T16:06:06Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KWW2W01J4GKFPXN49H2BJHM1","body":"AWS has confirmed this incident is resolved.","created_at":"2026-07-06T16:06:06Z","display_at":"2026-07-06T16:06:06Z","incident_id":"01KWVKCDM7BXXGN6JQHY1D8S4D","status":"resolved","updated_at":"2026-07-06T16:06:06Z"},{"id":"01KWVZ4330CYA8CC1PJQSCQQ6B","body":"We are no longer seeing any impacting clusters in the AWS us-east-1 region. We're continuing to monitor the situation.","created_at":"2026-07-06T15:00:37Z","display_at":"2026-07-06T15:00:37Z","incident_id":"01KWVKCDM7BXXGN6JQHY1D8S4D","status":"monitoring","updated_at":"2026-07-06T15:00:37Z"},{"id":"01KWVX2AD4FY48BGYXF9T1Y76T","body":"AWS has now acknowledged a us-east-1 EC2 Launch Template API incident impacting EKS node provisioning/scaling (incl. Karpenter). We are continuing to monitor the situation.","created_at":"2026-07-06T14:24:42Z","display_at":"2026-07-06T14:24:42Z","incident_id":"01KWVKCDM7BXXGN6JQHY1D8S4D","status":"monitoring","updated_at":"2026-07-06T14:24:42Z"},{"id":"01KWVR8ATPK8N4E85PAS7A4HCK","body":"AWS has published a status update for this issue. We are actively monitoring their progress and will continue to share updates.\n\u003chttps://health.aws.amazon.com/health/status?path=service-history\u003e","created_at":"2026-07-06T13:00:36Z","display_at":"2026-07-06T13:00:36Z","incident_id":"01KWVKCDM7BXXGN6JQHY1D8S4D","status":"investigating","updated_at":"2026-07-06T13:00:36Z"},{"id":"01KWVKCDM7N1DJT92Y6FQ6N1XD","body":"We are investigating node scaling issues in the AWS us-east-1 region. Customers may experience issues with worker scale-up and new task startup.","created_at":"2026-07-06T11:35:27Z","display_at":"2026-07-06T11:35:27Z","incident_id":"01KWVKCDM7BXXGN6JQHY1D8S4D","status":"investigating","updated_at":"2026-07-06T11:56:59Z"}]},{"id":"01KV6VYCRMY5QK0BAYGBEN9EZ4","name":"Azure clusters may experience issues with worker scale up and task pod scheduling","status":"resolved","created_at":"2026-06-16T00:05:20Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-06-16T00:53:16Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KV6ZFAW693GVWW1RM6FSPVZR","body":"This incident has been resolved.","created_at":"2026-06-16T01:07:01Z","display_at":"2026-06-16T00:53:16Z","incident_id":"01KV6VYCRMY5QK0BAYGBEN9EZ4","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KV6VYCRMD282DAWYDHHWRC0B","body":"A fix has been implemented and we are monitoring the results.","created_at":"2026-06-16T00:05:20Z","display_at":"2026-06-15T23:34:39Z","incident_id":"01KV6VYCRMY5QK0BAYGBEN9EZ4","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KV6VYCRM96J70ESPWJN95MHN","body":"**The issue, according to Azure status page**\n\nInvestigating a spike in 401 authentication errors We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We've identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.\n\nThis message was last updated at 23:04 UTC on 15 June 2026","created_at":"2026-06-16T00:05:20Z","display_at":"2026-06-15T23:28:33Z","incident_id":"01KV6VYCRMY5QK0BAYGBEN9EZ4","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KV6VYCRMPHJVRZNHRFP311DV","body":"We are currently investigating this issue.","created_at":"2026-06-16T00:05:20Z","display_at":"2026-06-15T23:27:23Z","incident_id":"01KV6VYCRMY5QK0BAYGBEN9EZ4","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KV61HFQ96PDBQ6M3T569D9JA","name":"astro deploys not reflecting on certain Astro clusters","status":"resolved","created_at":"2026-06-15T16:23:54Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-06-15T17:51:43Z","impact":"none","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KV66JAKKC3CTPE2Q96WYG7RD","body":"Mitigation was effective and all affected clusters are healthy.","created_at":"2026-06-15T17:51:44Z","display_at":"2026-06-15T17:51:43Z","incident_id":"01KV61HFQ96PDBQ6M3T569D9JA","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KV639AKNMH4NMMMTG14HVAMA","body":"We are monitoring the affect of the applied fix and are observing error rates coming down/ceasing for affected clusters.","created_at":"2026-06-15T16:54:24Z","display_at":"2026-06-15T16:54:22Z","incident_id":"01KV61HFQ96PDBQ6M3T569D9JA","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KV61HFQ9R7XKW6BHNQTYKPJA","body":"We've identified an issue with `astro deploy`s not updating manifests in Astro Hosted clusters, and we're currently applying a workaround and are continuing to monitor the situation.","created_at":"2026-06-15T16:23:54Z","display_at":"2026-06-15T16:23:51Z","incident_id":"01KV61HFQ96PDBQ6M3T569D9JA","status":"identified","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KR39YTN08XR55ENR1MXD9421","name":"Increased Task Failures in US-East-1 (AWS) - AWS Incident","status":"resolved","created_at":"2026-05-08T08:06:11Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-05-09T01:43:53Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KR57TNE8323VT0E1T2BM6C3Z","body":"AWS has confirmed recovery in the affected Availability Zone (use1-az4), and system performance has returned to normal levels.\n\nWe are no longer observing elevated task failures or latency in the AWS us-east-1 region. Any previously impacted workloads should now be operating as expected.\n\nIf you continue to experience issues, please reach out to Astronomer Support for assistance.","created_at":"2026-05-09T02:07:26Z","display_at":"2026-05-09T01:43:53Z","incident_id":"01KR39YTN08XR55ENR1MXD9421","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR39YTN0MJGMVBRPWGXHYZWP","body":"We are continuing to monitor the situation as AWS works toward full recovery in the affected Availability Zone. At this time, we are seeing signs of stabilization, and most transient failures should continue to self-resolve.\n\nWe will provide further updates once AWS confirms that the issue has been fully resolved.","created_at":"2026-05-08T08:06:11Z","display_at":"2026-05-08T07:45:35Z","incident_id":"01KR39YTN08XR55ENR1MXD9421","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR39YTN0N2WF3J7YDY77HT7Q","body":"We are currently observing elevated task failures and latency for some deployments running in the AWS us-east-1 region. This is related to an ongoing AWS incident affecting a single Availability Zone (use1-az4), where EC2 and EBS resources have experienced impairments.\n\nWhat to expect: You may see intermittent task failures or retries in your deployments. In most cases, these failures are transient and should self-resolve automatically as AWS continues recovery.\n\nWhat you should do: No immediate action is required. However, if you notice consistent or prolonged failures, please reach out to Astronomer Support, and we’ll help investigate further.\n\nWe are continuing to monitor the situation closely and will share updates as needed.\n\nRefer: https://health.aws.amazon.com/health/status","created_at":"2026-05-08T08:06:11Z","display_at":"2026-05-08T07:43:41Z","incident_id":"01KR39YTN08XR55ENR1MXD9421","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KR11ZVM86WTS15YSNYQKGY0B","name":"Delayed delivery for some time-based alerts","status":"resolved","created_at":"2026-05-07T11:08:27Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-05-07T14:24:42Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KR1FQK1RK53WHSAF6FXR0D90","body":"The incident has been resolved.","created_at":"2026-05-07T15:08:36Z","display_at":"2026-05-07T14:24:42Z","incident_id":"01KR11ZVM86WTS15YSNYQKGY0B","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR1C7MJ08GJ9W9WPQS1PQPK6","body":"A fix has been implemented, and we are monitoring the results.","created_at":"2026-05-07T14:07:28Z","display_at":"2026-05-07T13:49:16Z","incident_id":"01KR11ZVM86WTS15YSNYQKGY0B","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR18RDD6DKSGTZ599FM04W5P","body":"A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway.","created_at":"2026-05-07T13:06:43Z","display_at":"2026-05-07T12:57:33Z","incident_id":"01KR11ZVM86WTS15YSNYQKGY0B","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR15EMZEYFTZN6JJX555CVAJ","body":"We have identified the cause of the delayed delivery for some time-based alerts and are implementing a fix. We will provide another update once the fix has been deployed and validated.","created_at":"2026-05-07T12:08:58Z","display_at":"2026-05-07T11:15:03Z","incident_id":"01KR11ZVM86WTS15YSNYQKGY0B","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KR11ZVM8B17H5R6Z0BH6GX5J","body":"We are investigating delayed delivery for some time-based alerts. The delay is primarily visible for DAG Timeliness alerts, and may also affect Observe-related SLA, Proactive SLA, and Data Quality monitor alerts. DAG Duration and Task Duration alerts do not appear to be affected at this time.","created_at":"2026-05-07T11:08:27Z","display_at":"2026-05-07T10:31:36Z","incident_id":"01KR11ZVM86WTS15YSNYQKGY0B","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KQZEAH1H8T5FGV8C60DQKMP9","name":"Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.","status":"resolved","created_at":"2026-05-06T20:05:31Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-05-06T20:05:27Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KQZHS2WFZ1VV18ZSGSBZEXR6","body":"Our team has determined this only affects internal access, Astro end users are unaffected.","created_at":"2026-05-06T21:05:54Z","display_at":"2026-05-06T20:05:27Z","incident_id":"01KQZEAH1H8T5FGV8C60DQKMP9","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQZEAH1HBXM7VPJNWQM8GYD1","body":"Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.","created_at":"2026-05-06T20:05:31Z","display_at":"2026-05-06T19:56:05Z","incident_id":"01KQZEAH1H8T5FGV8C60DQKMP9","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KQSATPVQHXR8HA7VA81K3NQR","name":"Dashboard cost breakdown data delays","status":"resolved","created_at":"2026-05-04T11:09:00Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-05-04T20:15:15Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KQTD45C7MA4FEG1KH0H7HJQ1","body":"This incident is now resolved, and all Cost Breakdown data is now up to date. The issue that caused the delay has been fixed and should not recur.","created_at":"2026-05-04T21:08:22Z","display_at":"2026-05-04T20:15:15Z","incident_id":"01KQSATPVQHXR8HA7VA81K3NQR","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQSATPVQE7W3H8P4VCKM3HJ5","body":"We are continuing to investigate this issue.","created_at":"2026-05-04T11:09:00Z","display_at":"2026-05-04T10:56:52Z","incident_id":"01KQSATPVQHXR8HA7VA81K3NQR","status":"investigating","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQSATPVQC65XKJVVQD6PKA5R","body":"We’re investigating an issue affecting Dashboard cost breakdown data. For affected customers, cost breakdown information may appear stale and may not have updated since May 1, 2026. Our team is actively investigating the cause and working to restore current data. We’ll share another update as we have more information.","created_at":"2026-05-04T11:09:00Z","display_at":"2026-05-04T10:56:21Z","incident_id":"01KQSATPVQHXR8HA7VA81K3NQR","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KQ8FPEV48KJ7ZKGZFE0SKST6","name":"Airflow UI showing 403s for some customers","status":"resolved","created_at":"2026-04-27T22:06:58Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-28T00:16:03Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KQ8SZJ16HPK6KE9KRPYK4BK8","body":"We rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found their 403s resolved themselves after some time.","created_at":"2026-04-28T01:06:42Z","display_at":"2026-04-28T00:16:03Z","incident_id":"01KQ8FPEV48KJ7ZKGZFE0SKST6","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQ8FPEV4Z8J32GSAT7SDWZWG","body":"We are continuing to investigate this issue.","created_at":"2026-04-27T22:06:58Z","display_at":"2026-04-27T22:05:05Z","incident_id":"01KQ8FPEV48KJ7ZKGZFE0SKST6","status":"investigating","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQ8FPEV4FTEH05HM2TY7ZH5H","body":"It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.","created_at":"2026-04-27T22:06:58Z","display_at":"2026-04-27T22:04:59Z","incident_id":"01KQ8FPEV48KJ7ZKGZFE0SKST6","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KQ08JF5Q6FP1RFDZP4DBS46T","name":"Azure East US multiservice outage impacting Astro deployments in the region","status":"resolved","created_at":"2026-04-24T17:28:32Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-25T05:05:40Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KQ1GNA0W496G46ZXD1ZMCBS6","body":"Azure has confirmed the issue is resolved and services are back to normal. This incident is now closed. For more details, see the Azure incident history: https://azure.status.microsoft/en-us/status/history/","created_at":"2026-04-25T05:09:08Z","display_at":"2026-04-25T05:05:40Z","incident_id":"01KQ08JF5Q6FP1RFDZP4DBS46T","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQ1D5T48RGRXF3XYGTNKBERD","body":"Azure has fixed the issue, and services are back to normal in East US. We are monitoring to make sure everything stays stable.","created_at":"2026-04-25T04:08:15Z","display_at":"2026-04-25T03:56:39Z","incident_id":"01KQ08JF5Q6FP1RFDZP4DBS46T","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KQ08JF5QQKCB026HXRQ3YHF1","body":"Azure East US has reported multi-service impact that is affecting Astro deployments in the region. For more information on Azure outage, please visit: https://azure.status.microsoft/en-us/status","created_at":"2026-04-24T17:28:32Z","display_at":"2026-04-24T17:28:31Z","incident_id":"01KQ08JF5Q6FP1RFDZP4DBS46T","status":"identified","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KPD7Q7JRQJQN4GJRW4ZW7T4M","name":"Terminating Workers Accepting Tasks Causing Failures in Astro Executor","status":"resolved","created_at":"2026-04-17T08:08:05Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-17T11:47:24Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KPDNDNWT23NQ7A3TFN0GQ73J","body":"This issue has been resolved.","created_at":"2026-04-17T12:07:33Z","display_at":"2026-04-17T11:47:24Z","incident_id":"01KPD7Q7JRQJQN4GJRW4ZW7T4M","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KPDEK3P27MMSRSGN3RVM24GT","body":"The fix has been implemented, and we are now monitoring the deployments.","created_at":"2026-04-17T10:08:11Z","display_at":"2026-04-17T10:01:53Z","incident_id":"01KPD7Q7JRQJQN4GJRW4ZW7T4M","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KPD7Q7JRHQED7QBGSJYTKSB6","body":"We have identified the issue and we are rolling out the fix for the affected deployments.","created_at":"2026-04-17T08:08:06Z","display_at":"2026-04-17T08:05:31Z","incident_id":"01KPD7Q7JRQJQN4GJRW4ZW7T4M","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KPD7Q7JRD18RQDE4CC8GKHRS","body":"We have identified an issue with Astro Executor deployments where terminating workers can continue to accept new tasks, which can, in some cases, can cause these tasks to fail.","created_at":"2026-04-17T08:08:06Z","display_at":"2026-04-17T08:04:46Z","incident_id":"01KPD7Q7JRQJQN4GJRW4ZW7T4M","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KPBQK2447ZEQ6SZ4Q7W0PCG8","name":"Runtime 3.2-1 Yanked - Incompatible with Env Manager","status":"resolved","created_at":"2026-04-16T18:06:57Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-16T22:25:35Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KPC8QSTKJ7DHT2PTTPQHG8S7","body":"Astronomer Runtime 3.2-2 has been released with the fix.","created_at":"2026-04-16T23:06:38Z","display_at":"2026-04-16T22:25:35Z","incident_id":"01KPBQK2447ZEQ6SZ4Q7W0PCG8","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KPBQK244E2QD62FSDKNQ90MX","body":"We have identified that Runtime 3.2-1 is incompatible with the Astro Environment Manager. Any Connections or Variables stored at the Workspace level will not be available on deployments running 3.2-1. For this reason, we have disallowed the use of 3.2-1 for any deployments which are not already on that version. We are working to release a 3.2-2 version that is properly compatible as quickly as possible.","created_at":"2026-04-16T18:06:57Z","display_at":"2026-04-16T18:04:39Z","incident_id":"01KPBQK2447ZEQ6SZ4Q7W0PCG8","status":"identified","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KP4E4Y6FKA0AZ5AEH64K1GSR","name":"Degraded service for some deployments in Azure West Europe","status":"resolved","created_at":"2026-04-13T22:07:16Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-13T22:11:44Z","impact":"none","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KP4HGDV7RYWNRETVFQZBXV41","body":"**RESOLVED** – Azure West Europe Cluster Capacity Issue\n\nWe have resolved a capacity issue affecting our Azure West Europe (westeurope) shared cluster that occurred between 1:34 PM and 3:09 PM PDT on April 13.\n\nDuring this window, the cluster reached its vCPU quota, causing some deployments to become unhealthy. Our team immediately engaged Azure support and provisioned additional capacity as a temporary workaround, allowing all workloads to resume scheduling.\n\nAll services are now fully operational and healthy. We're working with Azure on a permanent quota increase to prevent recurrence.\n\nWe apologize for any disruption. If you experienced issues, please contact our support team.","created_at":"2026-04-13T23:05:58Z","display_at":"2026-04-13T22:11:44Z","incident_id":"01KP4E4Y6FKA0AZ5AEH64K1GSR","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KP4HGDV77DDN6XARYFFC0GAJ","body":"We are continuing to work on a fix for this issue.","created_at":"2026-04-13T23:05:58Z","display_at":"2026-04-13T22:10:49Z","incident_id":"01KP4E4Y6FKA0AZ5AEH64K1GSR","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KP4E4Y6FA38VFX5SJ7EY8Z4Z","body":"We are currently investigating an issue affecting deployments in our Azure West Europe region. Some customer deployments are experiencing degraded performance due to a compute resource constraint in our shared infrastructure.\n\nOur engineering team has identified that the region has reached its vCPU quota limit for a specific compute type, which is preventing new resources from being provisioned. We have opened a high-priority support request with Azure to increase this quota and are actively working with our Azure representative to expedite the approval.\n\nWe will provide updates as soon as we have more information about the timeline for resolution. We apologize for any disruption this may cause to your service.","created_at":"2026-04-13T22:07:16Z","display_at":"2026-04-13T21:44:04Z","incident_id":"01KP4E4Y6FKA0AZ5AEH64K1GSR","status":"identified","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KP1YJMNEPDV1TZVJ7XE2FEHZ","name":"Astro Alerts Degraded Performance","status":"resolved","created_at":"2026-04-12T22:56:39Z","updated_at":"2026-06-30T19:06:50Z","resolved_at":"2026-04-13T11:12:30Z","impact":"minor","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KP3BTKSRHY7TKEJ2K6MJM3NN","body":"The issue has been resolved. Over the weekend, we observed a degradation in alert performance. With the fix now applied, any missed alerts are expected to be delivered now, and new alerts will be triggered without latency. Alerting has returned to normal, and there is no ongoing delay. All alerts should now fire as expected.","created_at":"2026-04-13T12:07:26Z","display_at":"2026-04-13T11:12:30Z","incident_id":"01KP1YJMNEPDV1TZVJ7XE2FEHZ","status":"resolved","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KP24FY51F8JFV73KYSX02KM6","body":"We have applied a fix for the Astro Alerts degraded performance and currently monitoring it.","created_at":"2026-04-13T00:40:02Z","display_at":"2026-04-13T00:40:01Z","incident_id":"01KP1YJMNEPDV1TZVJ7XE2FEHZ","status":"monitoring","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KP238EPPAWHVFEC2A54GMKHG","body":"We have identified the issue with Astro Alert's degraded performance and currently working on a fix.","created_at":"2026-04-13T00:18:28Z","display_at":"2026-04-13T00:18:27Z","incident_id":"01KP1YJMNEPDV1TZVJ7XE2FEHZ","status":"identified","updated_at":"2026-06-30T19:06:50Z"},{"id":"01KP1YJMNE3TXSNE5M1V773GPK","body":"We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.","created_at":"2026-04-12T22:56:39Z","display_at":"2026-04-12T22:56:38Z","incident_id":"01KP1YJMNEPDV1TZVJ7XE2FEHZ","status":"investigating","updated_at":"2026-06-30T19:06:50Z"}]},{"id":"01KN859T53BEG8W1SE338A0X0B","name":"Astronomer Cloud Outage","status":"resolved","created_at":"2026-04-02T22:33:55Z","updated_at":"2026-06-30T19:06:58Z","resolved_at":"2021-12-16T15:28:13Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KN859T53CBNSPN1QRFQV0CDX","body":"This incident has been resolved.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-16T15:28:13Z","incident_id":"01KN859T53BEG8W1SE338A0X0B","status":"resolved","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859T53TK5H530T5EC6Y00A","body":"At this time, all components appear to be back online and operating as expected. We're going to monitor for a while before fully resolving this incident.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-16T15:06:17Z","incident_id":"01KN859T53BEG8W1SE338A0X0B","status":"monitoring","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859T53SV2FXVFV51YMSR4T","body":"We are currently investigating an issue with the Astronomer Cloud UI and API.\n\nUser impact: The interface may be intermittently available at this time, and Airflow UIs appear to be inaccessible due to the inability to authenticate users through the API. Given the API's role in Deployment and Cluster management, those components are likely to be unresponsive during this time.\n\nPlease stand by for updates. If you have any immediate questions, please reach out in Slack or open a ticket at support.astronomer.io.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-16T14:38:02Z","incident_id":"01KN859T53BEG8W1SE338A0X0B","status":"investigating","updated_at":"2026-06-30T19:06:58Z"}]},{"id":"01KN859TBGGH8G2NSR8WD87NF7","name":"AWS Outage","status":"resolved","created_at":"2026-04-02T22:33:55Z","updated_at":"2026-06-30T19:06:58Z","resolved_at":"2021-12-15T22:10:32Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KN859TBGR5MXXN4Y6N610YKD","body":"This incident has been resolved.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-15T22:10:32Z","incident_id":"01KN859TBGGH8G2NSR8WD87NF7","status":"resolved","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TBGGH5KG2965BR9GKB3","body":"The AWS outage has been resolved, however, as a result of that outage, our monitoring infrastructure has remained partially down. We've identified the issue, and are waiting for things to resolve now. While this is ongoing, deployment health statuses will remain red, indicating an unhealthy deployment. This may not actually be the case. Tasks should continue to run. Users likely won't be able to access their deployment in the usual way as the button will read 'Airflow Unavailable', but navigating to the URL of the deployment directly should work.\n\nAs always, if you have any questions, please open a support ticket at support.astronomer.io.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-15T18:25:39Z","incident_id":"01KN859TBGGH8G2NSR8WD87NF7","status":"monitoring","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TBGZ7JXA6B0H03G40J2","body":"While this outage is ongoing, users may be unable to access their Airflow Deployment UI. They may also be unable to deploy code (DAG), deployment configuration, or cluster configuration changes. Please stand by for further updates.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-15T16:14:18Z","incident_id":"01KN859TBGGH8G2NSR8WD87NF7","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TBGDC3BCGY90Z7VE5ST","body":"We are aware of an ongoing AWS outage. At this time, we know it's affecting the us-west-2 region. We're continuing to monitor the situation and will provide updates as they become available.\n\nhttps://status.aws.amazon.com/","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-15T15:57:34Z","incident_id":"01KN859TBGGH8G2NSR8WD87NF7","status":"investigating","updated_at":"2026-06-30T19:06:58Z"}]},{"id":"01KN859TKSNQS5NMDFBZN2AYE2","name":"Image Registry Unavailable","status":"resolved","created_at":"2026-04-02T22:33:55Z","updated_at":"2026-06-30T19:06:58Z","resolved_at":"2021-12-09T09:42:43Z","impact":"major","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KN859TKSRA2P1ZQBG89QGZCQ","body":"A fix is applied where we added a new query in astro API that retrieves deployments and updated the docker registry auth proxy to use that query","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T09:42:43Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"resolved","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKSB1CGRW9HXKX9ZX2E","body":"We are continuing to investigate this issue.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T09:41:37Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKS0XHGBB85Y17EXS0Q","body":"A fix is applied where we added a new query in astro API that retrieves deployments and updated the docker registry auth proxy to use that query","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T09:38:59Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKSWF0P832KSXKJPBJG","body":"Fix has been applied for docker-registry auth proxy.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T09:38:44Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKS4JY7P414S5PH3AZD","body":"We are continuing to investigate this issue.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T07:59:38Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKS7B858RM6KG6BKGFA","body":"The issue with our image repository is still being investigated, but most customers should be able to resume normal operations. Please subscribe for further updates.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T04:58:57Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TKSQQ7HE3T3MY91C92H","body":"Our image repository is currently unavailable. We're investigating the issue and will update as we know more.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-09T01:37:34Z","incident_id":"01KN859TKSNQS5NMDFBZN2AYE2","status":"investigating","updated_at":"2026-06-30T19:06:58Z"}]},{"id":"01KN859TZ975K6JW79P5DP3XWV","name":"AWS Outage","status":"resolved","created_at":"2026-04-02T22:33:55Z","updated_at":"2026-06-30T19:06:58Z","resolved_at":"2021-12-08T12:53:04Z","impact":"none","page_id":"01KN858NJKF1NW5FX72VHGX8D1","incident_updates":[{"id":"01KN859TZ9GPE3B8F2D5W00655","body":"This incident has been resolved.","created_at":"2026-04-02T22:33:56Z","display_at":"2021-12-08T12:53:04Z","incident_id":"01KN859TZ975K6JW79P5DP3XWV","status":"resolved","updated_at":"2026-06-30T19:06:58Z"},{"id":"01KN859TZ9ZJJTJM6H7PZNJ99X","body":"There is an ongoing AWS outage, specifically in the us-east-1 region, as reported here: https://status.aws.amazon.com/\n\nThis outage is limiting our ability to troubleshoot and mitigate issues within customer clusters and Airflow deployments that are hosted in this region. All health indicators show these clusters and deployments remain healthy at this time, but we recommend not making any changes until the outage is over.","created_at":"2026-04-02T22:33:55Z","display_at":"2021-12-07T17:56:03Z","incident_id":"01KN859TZ975K6JW79P5DP3XWV","status":"identified","updated_at":"2026-06-30T19:06:58Z"}]}]}