Live

Customers in the EU region might be facing issues accessing some files

Major outageOfficial update
0

Backblaze reports that some files are unavailable in the EU region. The provider is investigating the issue. The incident started at 03:35 UTC on 5 November 2026.

State

Investigating

Started

Ongoing for

2 h 17 min

Worst impact

Major outage

Timeline

1 update
03:3504:0904:4405:1805:52
Major outageUpdate postedTimes in UTC

Investigating

2 h 17 min 100%

Updates

Times in UTC

As posted by Backblaze

Investigating

We are investigating an issue in the EU region where a subset of customer files may be temporarily unavailable

Backblaze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

7

Median duration

5 days

This incident

98% shorter than the median

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

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