Skip to content
PulseWatchOUTAGE.INTEL
Wasabi logo

Cloud Infrastructure

Is Wasabi down right now?

NormalOfficial status last polled Oct 12, 2026 04:23 UTCwasabi.comOfficial status page

Are you on the Wasabi team and see something inaccurate? Report it to us. We respond within one business day.

Is Wasabi down right now?

No. Wasabi has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 05:22 UTC

Normal

Wasabi is operating normally

As of Oct 12, 2026 05:22 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 10, 2026 04:20 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Wasabi.

1

Incident days

29

No recorded incident

1h 35m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Wasabi. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

1

Days with incidents

1 incident

Busiest day

1h 35m

Recorded duration

Report volume

0 reports in last 24H

05:15 AM08:45 AM12:15 PM03:45 PM07:15 PM10:45 PM02:15 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Wasabi: vendor-reported major incident on October 10 (tracked 1h 34m)

Oct 10, 02:45 AM → Oct 10, 04:20 AM · 1h 34m · high

Wasabi reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1h 34m, closing it on 2026-10-10T04:20:46.334Z.

Duration
1h 34m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. The incident is known from Wasabi's own status page, where a major outage was declared.

Incident timeline

  1. Oct 10, 02:45 AM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 10, 02:45 AM

    Status updated: possible issue

  3. Oct 10, 04:20 AM

    PulseWatch closed the incident

Official updates

  1. Oct 10, 02:45 AM

    Wasabi reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

99.78%

90-day uptime

99.82%

Calculated from Wasabi's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Wasabi: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Wasabi or have an alert rule on it can be alerted, labelled vendor-reported.

10/10/2026, 2:45:52 AM · 1h 34m

02:45 AM04:20 AM
Detection10/10/2026, 2:45:52 AM · 2d ago

Detected — high severity

Wasabi: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Wasabi or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Wasabi incident correlated across 1 signal group: official/vendor.

9/1/2026, 8:34:13 AM · 2h 23m

08:34 AM10:57 AM
Detection9/1/2026, 8:34:13 AM · 1mo ago

Detected — medium severity

Wasabi incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Wasabi enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

wasabi.com