outages.live
Live
BackblazeMaintenance ·

US East Region Network Maintenance Nov 4, 2026

MaintenanceOfficial update

Backblaze will be upgrading components of our network infrastructure in the US East Region. We anticipate minimal customer impact during this maintenance window. The expected duration of this maintenance window is from 11/4/2026 starting at 10:00 until 12:00 Pacific Tim

The latest update from Backblaze.

State

Reported

Started

Ongoing for

1 h 7 min

Worst impact

Maintenance

Timeline

2 updates
18:0018:1718:3318:5019:07
MaintenanceUpdate postedTimes in UTC

Reported

1 h 7 min 100%

Updates

Times in UTC

As posted by Backblaze

Reported

Backblaze will be upgrading components of our network infrastructure in the US East Region. We anticipate minimal customer impact during this maintenance window. The expected duration of this maintenance window is from 11/4/2026 starting at 10:00 until 12:00 Pacific Tim

Reported

Affected components

1
US East Region

Backblaze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

6

Median duration

5 days

This incident

Not comparable

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

6 days
median 5 days
90 days agoToday

Other Backblaze incidents

All incidents

Backblaze·Customers in the US east region might be facing issues with downloads

Backblaze reports download problems for some customers in the US east region. The issue is resolved. It lasted about 4 days and 14 hours.

Resolved

Backblaze·EU Region High Upload Failures

Backblaze reports high upload failures in the EU region. The failures affect some customers in that region. Backblaze is investigating and states that some upload issues remain after earlier mitigation.

Partial outage

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.cc/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.cc/feed.xml?providers=backblaze
Slack
/feed subscribe https://outages.cc/feed.xml?providers=backblaze

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane