outages.live
Live

Steel

Steel is operational

Checked 3 min ago Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Steel status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Steel since Nov 3, 2026. The days before that show only what Steel published.

Incidents in 90 days

7

Days with an incident

6

Median duration

1 h 47 min

Longest incident

6 h 50 min

Components

3

Steel API

Main API Operational
90 days ago5 days with an incidentToday

Proxies

Connections Operational
90 days ago1 day with an incidentToday

Dashboard

Main - App Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Nov 2, 2026

Duration8 min16:14 to 16:22Seeing Session Creation FailuresDegraded

We have identified the root cause of the issue and pushed out a fix; this was a problem with creating sessions w/ extensions. We'll continue to monitor the situation closely

Oct 2, 2026

Duration1 h 55 min01:00 to 02:55Session creations are failingDegraded

We have successfully rolled out the fix out across the affected fleet. Session connectivity and error rates have returned to normal.

Sep 25, 2026

Duration6 h 50 min14:29 to 21:19Intermittent live streaming and recording issuesDegraded

We rolled out an update a few hours ago, and live streaming and recording have remained stable since. We’ll continue to monitor things closely to make sure everything remains healthy.

Sep 23, 2026

Duration1 h 47 min19:18 to 21:05Dealing with streaming issuesDegraded

We've pushed out a fix and these issues should be resolved now. `headless` is still facing a couple issues but we will follow up with updates there shortly.

Sep 16, 2026

Duration2 h 18 min18:41 to 20:59Custom (BYOP) HTTPS proxies failing for some customersDegraded

All connections should be functioning properly again.

Sep 4, 2026

Duration7 min23:46 to 23:53Our edge gateway is having issues with all requestsDegraded

We’ve pushed out a fix/patch; but it turns out this was a longer blip from one of our upstream providers. We’ll be working on workarounds for this going forward.

Duration3 min14:27 to 14:30Facing a higher error rate of session createsDegraded

We've pushed a fix and are monitoring the situation.

Follow Steel

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane