Who is down right now

Down now18This week221

18 down now · 221 this week

Astronomer · Data and observabilitySep 1, 2026, 18:40 UTC 2 months ago

Potential impact to Astro deployments in GCP us-central1

MinorNot disclosedUpdated 2h ago
Sep 1, 18:40 UTCSep 1, 22:29 UTC
Duration
3h 50m
Impact
Minor
Root cause
Not disclosed
Astronomer, 90 days
17 incidents
Affected
Not listed by the vendor.
Status page

Final update

The GCP incident is marked as Closed officially

Timeline

  1. Resolved · Sep 1, 22:29 UTC
    The GCP incident is marked as Closed officially
  2. Monitoring · Sep 1, 20:42 UTC
    Google 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.
  3. Monitoring · Sep 1, 19:19 UTC
    Google 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.
  4. Investigating · Sep 1, 19:05 UTC
    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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
  5. Investigating · Sep 1, 18:44 UTC
    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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
  6. Investigating · Sep 1, 18:43 UTC
    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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
  7. Investigating · Sep 1, 18:40 UTC
    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. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").

More from Astronomer

Full history
NoticeOngoingOct 22, 18:26 UTC
PHP Security Advisory: Astro and Astro Private Cloud Not Affected; Review Custom Imagesstill open
NoticeOct 22, 00:01 UTC
Security Update: Runtime Releases and Guidance for the eMudhra/emSign Certificate Issuelasted 45h 27m
MajorOct 20, 06:40 UTC
Delayed delivery of Astro Alertslasted 26h 9m
MajorOct 19, 09:37 UTC
Organization Dashboards are failing to load with Invalid kid parameter errorlasted 1h 23m
MajorOct 13, 18:02 UTC
Astro UI and API are appearing offline for some userslasted 1h 51m
MinorOct 6, 03:33 UTC
Capacity constraints in GCP us-central1 may delay or fail some task executionslasted 7d 21h