Custom (BYOP) HTTPS proxies failing for some customers
All connections should be functioning properly again.
The latest update from Steel.
State
Resolved
Started
48 d ago
2026-09-16 18:41 UTC
Lasted
2 h 18 min
until 2026-09-16 20:59 UTC
Worst impact
Degraded
Timeline
2 updatesDegraded
2 h 18 min 100%
Updates
Times in UTCAs posted by Steel
All connections should be functioning properly again.
We're investigating what could be causing this and we'll follow up with an update shortly.
Affected components
1Steel in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
6
Median duration
1 h 47 min
This incident
1.3× the median
Other Steel incidents
All incidentsSteel·Seeing Session Creation Failures
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
Steel·Session creations are failing
We have successfully rolled out the fix out across the affected fleet. Session connectivity and error rates have returned to normal.
Steel·Intermittent live streaming and recording issues
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.
Steel·Dealing with streaming issues
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.
Steel·Our edge gateway is having issues with all requests
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.
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.
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.
https://outages.cc/feed.xml?providers=steel/feed subscribe https://outages.cc/feed.xml?providers=steelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane