outages.live
Live
BackblazeIncident ·

Unable to login to EWC in production

Major outageOfficial update
0

Backblaze reports that customers cannot log in to the Enterprise Web Console. All Organization Services APIs are unavailable, which also affects bucket creation for organization accounts. Backblaze identified the problem and works to restore service.

State

Identified

Started

Ongoing for

1 h 51 min

Worst impact

Major outage

Timeline

3 updates
23:0923:3700:0500:3201:00
Major outageUpdate postedTimes in UTC

Investigating

1 h 33 min 83%

Identified

18 min 17%

Updates

Times in UTC

As posted by Backblaze

Identified

Due to an ongoing service issue, all Organization Services APIs are currently unavailable, affecting Enterprise Web Console logins and bucket creation for organization accounts. Our team is investigating and working to restore service. We will provide updates as more information becomes available.

Investigating

Due to an ongoing service issue, all Organization Services APIs are currently unavailable, affecting Enterprise Web Console logins and bucket creation for organization accounts. Our team is investigating and working to restore service. We will provide updates as more information becomes available.

Investigating

We are investigating an issue preventing customers from logging in to the Enterprise Web Console. Our team is working to restore access, and we will provide updates as more information becomes available.

Backblaze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

8

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.

7 days
median 5 days
90 days agoToday

Other Backblaze incidents

All incidents

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

Some files are not available to customers in the EU region. Backblaze identified the issue and applied a fix. Backblaze continues to monitor the services and has completed additional cleanup.

Major outage

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