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

Power Maintenance Causing Loss of Power Redundancy in us-west-3

Reported by Lambda · AI & ML · source last read just now

Official source (opens in a new tab)
Vendor start
Mar 19, 2026, 20:12 UTC
Vendor's clock
Resolved
Mar 20, 2026, 15:23 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
19 h 11 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

  • Lambda reports degraded: "Power Maintenance Causing Loss of Power Redundancy in us-west-3".[E1, E2]
  • The vendor marked it resolved at 2026-03-20 15:23 UTC.[E3, E7]

Affected products and regions

  • Regions: us-west-3 (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-03-20 15:23 UTC · summary s1, evidence a32c5a57b85862b6

Evidence (7)
  1. E1Lambda reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Power Maintenance Causing Loss of Power Redundancy in us-west-3". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-19 20:12 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-west-3. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-03-20 15:23 UTC. (vendor)

Affected scope

us-west-3

Components: not stated by the vendor

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

Potential relevance

Lambda 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. Mar 19, 2026, 20:12 UTCVendor-reported startVendor time
  2. Mar 20, 2026, 15:23 UTCVendor-reported resolutionVendor time

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