Vendor reports: degradedResolved · vendor status “resolved”Official status API

Potential impact to Astro deployments in GCP us-central1

Reported by Astronomer · Data & Analytics · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Sep 1, 2026, 18:40 UTC
Vendor's clock
Resolved
Sep 1, 2026, 22:29 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 50 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Astronomer reports degraded: "Potential impact to Astro deployments in GCP us-central1".[E1, E2]
  • The vendor marked it resolved at 2026-09-01 22:29 UTC.[E3, E7]

Affected products and regions

  • Regions: us-central1 (read from the title, so inferred).[E5]

What is unknown

  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-09-01 22:29 UTC · summary s1, evidence 863dc52ddd638acf

Evidence (7)
  1. E1Astronomer reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Potential impact to Astro deployments in GCP us-central1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-09-01 18:40 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-central1. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-09-01 22:29 UTC. (vendor)

Affected scope

us-central1

Components: not stated by the vendor

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Astronomer is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Sep 1, 2026, 18:40 UTCVendor-reported startVendor time
  2. Sep 1, 2026, 22:29 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.