UptimeProject

Backblaze B2

Operational

Backblaze · Object Storage

Updated

24h availability

100.00%

0 min down

7d availability

100.00%

0 min down

30d availability

100.00%

0 min down

90d availability

99.99%

2 min down

Period:
Avg response time 365ms
0% 50% 100% 2026-08-09 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-08-10 00:00 UTC Status: down Availability: 99.86% p50 latency: 367ms 2026-08-11 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-12 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-13 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-14 00:00 UTC Status: up Availability: 100.00% p50 latency: 368ms 2026-08-15 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-08-16 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-08-17 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-08-18 00:00 UTC Status: up Availability: 100.00% p50 latency: 373ms 2026-08-19 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-08-20 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-08-21 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-08-22 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-08-23 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-08-24 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-08-25 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-08-26 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-08-27 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-08-28 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-29 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-30 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-08-31 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-01 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-09-02 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-09-03 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-04 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-05 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-06 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-07 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-08 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-09 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-10 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-09-11 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-12 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-13 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-14 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-15 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-09-16 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-09-17 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-18 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-19 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-09-20 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-09-21 00:00 UTC Status: up Availability: 100.00% p50 latency: 384ms 2026-09-22 00:00 UTC Status: up Availability: 100.00% p50 latency: 370ms 2026-09-23 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-09-24 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-09-25 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-09-26 00:00 UTC Status: up Availability: 100.00% p50 latency: 362ms 2026-09-27 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-09-28 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-09-29 00:00 UTC Status: up Availability: 100.00% p50 latency: 362ms 2026-09-30 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-10-01 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-02 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-10-03 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-10-04 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-05 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-06 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-07 00:00 UTC Status: degraded Availability: 99.93% p50 latency: 364ms 2026-10-08 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-09 00:00 UTC Status: up Availability: 100.00% p50 latency: 363ms 2026-10-10 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-10-11 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-10-12 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-13 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-14 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-15 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-16 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-10-17 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-18 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-19 00:00 UTC Status: up Availability: 100.00% p50 latency: 366ms 2026-10-20 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-21 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-22 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-23 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-10-24 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-25 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-26 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-10-27 00:00 UTC Status: up Availability: 100.00% p50 latency: 370ms 2026-10-28 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-10-29 00:00 UTC Status: up Availability: 100.00% p50 latency: 369ms 2026-10-30 00:00 UTC Status: up Availability: 100.00% p50 latency: 367ms 2026-10-31 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-11-01 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-11-02 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-11-03 00:00 UTC Status: up Availability: 100.00% p50 latency: 365ms 2026-11-04 00:00 UTC Status: up Availability: 100.00% p50 latency: 364ms 2026-11-05 00:00 UTC Status: up Availability: 100.00% p50 latency: 362ms 2026-11-06 00:00 UTC Status: up Availability: 100.00% p50 latency: 361ms 389ms 356ms 09 Aug 06 Nov 90d availability · latency (p50)

90d: 2 min down, 1 min degraded, 0 min unmeasured

Recent incidents

All incidents Atom feed

No incidents recorded in the lookback window.

Vantage points

Falkenstein, DE Hetzner
502ms Operational
Roubaix, FR OVH
441ms Operational
New York, US DigitalOcean
226ms Operational
Seattle, US Vultr
89ms Operational
Singapore Vultr
525ms Operational

What we monitor

3 active checks

Each row below is one probe-side measurement we run from every vantage point. The availability number on this page is the consensus across these checks, not a single endpoint hit.

  • HTTP https://api.backblazeb2.com/b2api/v3/b2_authorize_account every minute
  • Storage https://f005.backblazeb2.com/file/redacted/probe.bin every 10 minutes
  • TLS api.backblazeb2.com:443 every hour

About this data

Availability is measured independently by probes in five locations. Each probe runs the appropriate mix of HTTP, DNS, TLS, and storage checks at per-check cadences and records timing, status code, and any error. A probe votes "up" for a given minute if any of its checks for this service succeeded; the minute is then counted as "up" on the leaderboard only when a strict majority of reporting probes voted up. Minutes where fewer than three probes reported are excluded from the denominator. Full methodology

Embed a badge

Markdown for a README. The image is served by the public API and links back to this page.

          [![Backblaze B2 uptime](https://api.uptimeproject.org/v1/services/backblaze-b2/badge.svg)](https://uptimeproject.org/service/backblaze-b2/)
        
Back to Object Storage leaderboard