Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Delayed Metrics in Cloud Console - GCP us-east4

Reported by Elastic Cloud · Data & Analytics · source last read 5 min ago

Vendor start
Sep 12, 2026, 23:21 UTC
Vendor's clock
Resolved
Sep 13, 2026, 07:45 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
8 h 24 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

  • Elastic Cloud reports partial outage: "Delayed Metrics in Cloud Console - GCP us-east4".[E1, E2]
  • The vendor marked it resolved at 2026-09-13 07:45 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east4 (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-13 07:45 UTC · summary s1, evidence 7018fe5b12b386dc

Evidence (7)
  1. E1Elastic Cloud reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed Metrics in Cloud Console - GCP us-east4". (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-12 23:21 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east4. (Statuswall) source (opens in a new tab)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-09-13 07:45 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east4

Components: not stated by the vendor

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

Potential relevance

Elastic Cloud 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 12, 2026, 23:21 UTCVendor-reported startVendor time
  2. Sep 13, 2026, 07:45 UTCVendor-reported resolutionVendor time

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