outages.live
Live
BlaxelIncident ·

Increased Agent Drive Latency on us-was-1

Partial outageOfficial update
0

Blaxel reports increased Agent Drive latency on us-was-1. This is a partial outage. Blaxel has identified the cause and is working on a fix.

State

Identified

Started

Ongoing for

51 min

Worst impact

Partial outage

Timeline

2 updates
18:3218:4518:5819:1019:23
Partial outageDegradedUpdate postedTimes in UTC

Identified

51 min 100%

Updates

Times in UTC

As posted by Blaxel

Identified

We’ve identified the cause and are working on a fix. Some users may continue to experience degraded performance while we resolve the issue. We’ll share another update as soon as possible.

Identified

We’ve identified the cause and are working on a fix. Some users may continue to experience degraded performance while we resolve the issue. We’ll share another update as soon as possible.

Blaxel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

22

Median duration

1 h 23 min

This incident

39% shorter than the median

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

16 h
median 1 h 23 min
90 days agoToday

Other Blaxel incidents

All incidents

Blaxel·Drive mount and write failures

Blaxel reported drive mount and write failures. The provider identified the cause, deployed a fix, and monitored recovery. Blaxel says the incident is resolved and the service operates normally again. The outage lasted about 88 minutes.

Resolved

Blaxel·Workloads Unavailable on Older Generation

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Resolved

Blaxel·Drive mount and write failures

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Resolved

Blaxel·Sandbox proxy unavailable on us-was-1

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Resolved

Blaxel·Some sandboxes are unavailable in us-was-1

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Resolved

Follow Blaxel

Your coding agent knows when Blaxel is down, and tells you when a failure is theirs, not yours. You can also get Blaxel 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 "blaxel" and tell me if Blaxel 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=blaxel
Slack
/feed subscribe https://outages.live/feed.xml?providers=blaxel

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane