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.
State
Investigating
Started
3 d ago
2026-10-30 00:49 UTC
Ongoing for
3 days
Worst impact
Partial outage
Timeline
1 updateInvestigating
3 days 100%
Updates
Times in UTCAs posted by Backblaze
We are investigating continued upload failures affecting some customers in the EU region. Although earlier mitigation improved service, some upload issues remain. We will provide further updates as more information becomes available.
Backblaze in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
3
Median duration
Not enough data
This incident
Not comparable
Other Backblaze incidents
All incidentsFollow 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.
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.
https://outages.cc/feed.xml?providers=backblaze/feed subscribe https://outages.cc/feed.xml?providers=backblazeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane