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

System Errors in AP-NORTHEAST-1

Reported by Wasabi · Cloud & Infrastructure · source last read just now

Official source (opens in a new tab)
Vendor start
Mar 30, 2026, 15:28 UTC
Vendor's clock
Resolved
Mar 24, 2026, 19:30 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Wasabi reports operational: "System Errors in AP-NORTHEAST-1".[E1, E2]
  • The vendor marked it resolved at 2026-03-24 19:30 UTC.[E3, E7]

Affected products and regions

  • Regions: ap-northeast-1 (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-30 15:28 UTC · summary s1, evidence 8b3e469c208e31a0

Evidence (7)
  1. E1Wasabi reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "System Errors in AP-NORTHEAST-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-30 15:28 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): ap-northeast-1. (Statuswall) source (opens in a new tab)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-03-24 19:30 UTC. (vendor) source (opens in a new tab)

Affected scope

ap-northeast-1

Components: not stated by the vendor

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

Potential relevance

Wasabi 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 24, 2026, 19:30 UTCVendor-reported resolutionVendor time
  2. Mar 30, 2026, 15:28 UTCVendor-reported startVendor time

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