Live

Agent Drive maintenance in us-was-1

Maintenance has started

The latest update from Blaxel.

State

Resolved

Started

Lasted

12 h 52 min

Worst impact

Maintenance

Timeline

3 updates
05:3808:5112:0415:1718:30
MaintenanceUpdate postedTimes in UTC

Scheduled

11 h 52 min 92%

In progress

1 h 8%

Updates

Times in UTC

As posted by Blaxel

Resolved
In progress

Maintenance has started

Scheduled

We’ll be performing scheduled maintenance on Agent Drive storage in **us-was-1** during this window. **What to expect:** - Agent Drive writes may experience brief delays during maintenance. Writes are automatically retried and should complete once normal operation resumes. - Reads will continue to work as usual. - Sandboxes, volumes, and other regions are unaffected. **No action is required.** Applications with short write timeouts may occasionally need to retry a write.

Blaxel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

30

Days with an incident

25

Median duration

1 h 26 min

This incident

Not comparable

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

16 h
median 1 h 26 min
90 days agoToday

Other Blaxel incidents

All incidents

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