Live

Agent Drive storage maintenance (us-was-1)

MaintenanceOfficial update

We’ll be performing scheduled maintenance on Agent Drive storage in **us-was-1** during the scheduled window. Writes may experience brief interruptions during maintenance and can be safely retried. Reads and existing data will remain unaffected. We’ll share updates here as maintenance progresses.

The latest update from Blaxel.

State

Scheduled

Started

Ongoing for

5 h 30 min

Worst impact

Maintenance

Timeline

1 update
22:5200:1401:3702:5904:22
MaintenanceUpdate postedTimes in UTC

Scheduled

5 h 30 min 100%

Updates

Times in UTC

As posted by Blaxel

Scheduled

We’ll be performing scheduled maintenance on Agent Drive storage in **us-was-1** during the scheduled window. Writes may experience brief interruptions during maintenance and can be safely retried. Reads and existing data will remain unaffected. We’ll share updates here as maintenance progresses.

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