outages.live
Live
BlaxelIncident · 2026-08-25 21:48 UTC

Dedicated IP Connectivity Issues in us-was-1

ResolvedOfficial update

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

The latest update from Blaxel.

State

Resolved

Started

69 d ago

2026-08-25 21:48 UTC

Lasted

2 h 33 min

until 2026-08-26 00:21 UTC

Worst impact

Degraded

Timeline

3 updates
21:4822:2623:0523:4300:21
DegradedUpdate postedTimes in UTC

Investigating

1 h 48 min 71%

Monitoring

45 min 29%

Updates

Times in UTC

As posted by Blaxel

Resolved2026-08-26 00:21 UTC

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

Monitoring2026-08-25 23:36 UTC

A fix has been deployed, and we’re monitoring to confirm recovery. A small amount of residual impact may persist while systems stabilize.

Investigating2026-08-25 21:48 UTC

We’re investigating an issue affecting Dedicated IP connectivity in the us-was-1 region. Workloads using Dedicated IPs may experience connectivity failures. We’re actively investigating and will provide updates as more information becomes available.

Blaxel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

21

Median duration

1 h 22 min

This incident

1.9× the median

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

16 h
median 1 h 22 min
90 days agoToday

Other Blaxel incidents

All incidents

Blaxel·Drive mount and write failures

Blaxel reports drive mount and write failures. The problem is a partial outage. Blaxel identified the cause, deployed a fix, and now monitors the systems for recovery. Some residual impact can continue while the systems stabilize.

Partial outageupdated 9 min ago

Blaxel·Workloads Unavailable on Older Generation

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

Resolvedresolved 6 h ago

Blaxel·Drive mount and write failures

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

Resolvedresolved 3 d ago

Blaxel·Sandbox proxy unavailable on us-was-1

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

Resolvedresolved 4 d ago

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

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

Resolvedresolved 5 d ago

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