Astro Status · History · Incident #28173
RESOLVEDPotential impact to Astro deployments in GCP us-central1
Minor · Started Sep 1, 2026 · 6:40 PM
Astro Status · History · Incident #28173
RESOLVEDMinor · Started Sep 1, 2026 · 6:40 PM
Duration
3h 49m
Severity
Minor
Detection lead
—
User reports
—
Summary
The GCP incident is marked as Closed officially
Started
Sep 1, 2026 · 6:40 PM
Resolved
Sep 1, 2026 · 10:29 PM
Duration
3h 49m
Severity
Minor
Event timeline
Investigating
Sep 1 · 6:40 PM AstroWe 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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
Investigating
Sep 1 · 6:43 PM AstroWe 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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
Investigating
Sep 1 · 6:44 PM AstroWe 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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
Investigating
Sep 1 · 7:05 PM AstroWe 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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
Monitoring
Sep 1 · 7:19 PM AstroGoogle Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC. During this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments.
Monitoring
Sep 1 · 8:42 PM AstroGoogle Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC. During this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments. This issue has since been resolved by Google, but we are continuing to monitor the situation internally to ensure it's resolution.
Resolved
Sep 1 · 10:29 PM AstroThe GCP incident is marked as Closed officially
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.