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

System Errors to access Wasabi services

Reported by Wasabi · Cloud & Infrastructure · source last read 8 min ago

Official source (opens in a new tab)
Vendor start
Mar 27, 2025, 22:09 UTC
Vendor's clock
Resolved
Mar 27, 2025, 22:09 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 degraded: "System Errors to access Wasabi services".[E1, E2]
  • The vendor marked it resolved at 2025-03-27 22:09 UTC.[E3, E7]

Affected products and regions

  • Components: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), Wasabi Management Console.[E6]

What is unknown

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

Last update in these facts: 2025-03-27 22:09 UTC · summary s1, evidence 1a1f26018674ed62

Evidence (7)
  1. E1Wasabi reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "System Errors to access Wasabi services". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-03-27 22:09 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), Wasabi Management Console. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-03-27 22:09 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), Wasabi Management Console

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

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 27, 2025, 22:09 UTCVendor-reported startVendor time
  2. Mar 27, 2025, 22:09 UTCVendor-reported resolutionVendor time

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

Wasabi: System Errors to access Wasabi services — statuswall