Live

Core Services Maintenance

Backblaze will be investing in our infrastructure with routine, but extended, maintenance. Affected services Web Interface Website sign-on New account creation Computer Backup Data restore and recovery Backups may sleep temporarily Sign-in via installers and apps B2 Cloud Storage Bucket creation, deletion, and API update B2 Snapshot creation

The latest update from Backblaze.

State

Resolved

Started

Lasted

2 h 28 min

Worst impact

Maintenance

Timeline

2 updates
23:1123:4800:2501:0201:39
MaintenanceUpdate postedTimes in UTC

Identified

2 h 28 min 100%

Updates

Times in UTC

As posted by Backblaze

Resolved
Identified

Backblaze will be investing in our infrastructure with routine, but extended, maintenance. Affected services Web Interface Website sign-on New account creation Computer Backup Data restore and recovery Backups may sleep temporarily Sign-in via installers and apps B2 Cloud Storage Bucket creation, deletion, and API update B2 Snapshot creation

Backblaze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

20

Median duration

3 days

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

20 days
median 3 days
90 days agoToday

Other Backblaze incidents

All incidents

Follow Backblaze

Your coding agent knows when Backblaze is down, and tells you when a failure is theirs, not yours. You can also get Backblaze incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "backblaze" and tell me if Backblaze has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=backblaze
Slack
/feed subscribe https://outages.live/feed.xml?providers=backblaze

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane