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

AWS eu-central-1 - Metrics - Outage

Reported by Logz.io · Observability & Incident · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Feb 23, 2026, 17:38 UTC
Vendor's clock
Resolved
Feb 23, 2026, 17:59 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
21 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

  • Logz.io reports operational: "AWS eu-central-1 - Metrics - Outage".[E1, E2]
  • The vendor marked it resolved at 2026-02-23 17:59 UTC.[E3, E7]

Affected products and regions

  • Regions: eu-central-1 (read from the title, so inferred).[E5]
  • Components: Metrics Ingestion.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-23 17:59 UTC · summary s1, evidence 63b43353cec95d61

Evidence (7)
  1. E1Logz.io reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "AWS eu-central-1 - Metrics - Outage". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-23 17:38 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): eu-central-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Metrics Ingestion. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-02-23 17:59 UTC. (vendor) source (opens in a new tab)

Affected scope

eu-central-1

Components: Metrics Ingestion

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

Potential relevance

Logz.io 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. Feb 23, 2026, 17:38 UTCVendor-reported startVendor time
  2. Feb 23, 2026, 17:59 UTCVendor-reported resolutionVendor time

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