Is Wasabi down?

Last checked just now
Current status
Wasabi is up

No incidents right now.

  • Official status page: status.wasabi.com
  • Checked every 5 minutes
  • 27 components tracked

Wasabi is operational right now. Last checked just now; the most recent incident resolved 2d ago.

Real-time Wasabi status, recent outages, and incident history: pulled directly from Wasabi's official status page at status.wasabi.com every 5 minutes. Pingoru tracks 27 Wasabi services and has captured 34 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Wasabi reports a new incident, free for 3 monitors, no credit card.

Users who monitor Wasabi also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud Linode View all 8,000+ providers
Wasabi uptime 99.71% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 43m
    Started Oct 10, 2026, 02:27 AM UTC · Resolved Oct 10, 2026, 04:11 AM UTC
    AP-Southeast-1 (Singapore)
    Timeline · 4 updates
    • investigating · Oct 10, 2026, 02:27 AM UTC

      We are currently investigating an issue impacting the AP-SOUTHEAST-1 (Singapore) region. Due to a power event at the site, services in the region are impacted and customers may experience errors or failed requests.

    • monitoring · Oct 10, 2026, 02:55 AM UTC

      Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.

    • resolved · Oct 10, 2026, 04:11 AM UTC

      Incident resolved

    • postmortem · Oct 13, 2026, 02:10 PM UTC

      On October 10, 2026, between 01:10 and 02:30 UTC, customers may have experienced degraded performance and elevated error rates in the Singapore region due to a power unit failure at the data center. The failure disrupted connectivity to the underlying infrastructure, reducing traffic levels and interrupting API operations.  The data center team replaced the failed unit and restored power at approximately 02:23 UTC. Our team then worked with the data center provider to bring the affected equipment back online at 02:30 UTC, after which services recovered and traffic returned to normal levels. We monitored the recovery to confirm that operations had returned to normal.  For any questions, please reach out to [[email protected]](mailto:[email protected]).

    Latest: On October 10, 2026, between 01:10 and 02:30 UTC, customers may have experienced degraded performance and elevated error rates in the Singapore region due to a power unit failure a…

  2. Resolved 1h 43m
    Started Oct 06, 2026, 07:08 AM UTC · Resolved Oct 06, 2026, 08:51 AM UTC
    Wasabi Management Console
    Timeline · 2 updates
    • investigating · Oct 06, 2026, 07:08 AM UTC

      We are currently investigating some customers difficulty to access the Wasabi Console. As alternative try to use your region URL, example: console.us-east-1.wasabisys.com or console.us-east-2.wasabisys.com or console.us-west-1.wasabisys.com etc

    • resolved · Oct 06, 2026, 08:51 AM UTC

      This incident has been resolved

    Latest: This incident has been resolved

  3. Resolved 2h 5m
    Started Sep 01, 2026, 08:31 AM UTC · Resolved Sep 01, 2026, 10:36 AM UTC
    Wasabi Account Control Manager Console
    Timeline · 2 updates
    • investigating · Sep 01, 2026, 08:31 AM UTC

      We are currently investigating an issue with WACM reporting 0% storage utilization for subaccounts instead of the actual value

    • resolved · Sep 01, 2026, 10:36 AM UTC

      Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact [email protected] if you continue to see any problem related to this incident.

    Latest: Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact [email protected]…

  4. Resolved 2h 51m
    Started Aug 25, 2026, 11:46 PM UTC · Resolved Aug 26, 2026, 02:37 AM UTC
    US-East-1 (N. Virginia)
    Timeline · 3 updates
    • investigating · Aug 25, 2026, 11:46 PM UTC

      We are currently investigating issues happening in US-EAST-1 region that are impacting some of the PUT (Upload) api calls.

    • monitoring · Aug 26, 2026, 01:09 AM UTC

      Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.

    • resolved · Aug 26, 2026, 02:37 AM UTC

      The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infrastructure issue on our backend. Our team identified the cause and applied a fix. Service has been fully restored. We apologize for any inconvenience.

    Latest: The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infras…

  5. Resolved 33m
    Started Aug 04, 2026, 07:30 AM UTC · Resolved Aug 04, 2026, 08:03 AM UTC
    Timeline · 1 update
    • resolved · Aug 04, 2026, 02:21 PM UTC

      On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastructure. Wasabi’s Operations Team was alerted by our automated monitoring systems to a drop on our ingestion traffic and started investigating. The updated was rolled back and services were fully restored on the region by 08:03 UTC.

    Latest: On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastruct…

Incident record

Since April 2026 · Statuspage by Atlassian · 27 components checked every 5 minutes
51incidents recorded
16last 12 months
5last 90 days
4 hourstypical duration, 12 months

The longest incident in the last year, System Errors in AP-NORTHEAST-1 on March 24, 2026, ran for 15 hours. 56 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Wasabi Management Console3
  • AP-Northeast-1 (Tokyo)1
  • AP-Southeast-1 (Singapore)1
  • EU-Central-1 (Amsterdam)1
  • EU-Central-2 (Frankfurt)1

Latest incidents

  • System Errors in AP-SOUTHEAST-1 October 10, 2026 · 103 minutes · major outage

    We are currently investigating an issue impacting the AP-SOUTHEAST-1 (Singapore) region. Due to a power event at the site, services in the region are impacted…

  • Intermittent Wasabi Console Access October 6, 2026 · 103 minutes · degraded service

    We are currently investigating some customers difficulty to access the Wasabi Console. As alternative try to use your region URL, example…

  • WACM reporting 0% storage utilization for subaccounts September 1, 2026 · 2 hours · degraded service

    We are currently investigating an issue with WACM reporting 0% storage utilization for subaccounts instead of the actual value

Outage history

Past 90 days · 5 incidents View full outage history →