Warp-hosted agents waiting to be assigned to sandboxes
ResolvedOfficial update
This incident has been resolved.
The latest update from Warp.
State
Resolved
Started
Lasted
1 h 22 min
Worst impact
Degraded
Timeline
3 updates15:5816:1816:3917:0017:20
DegradedUpdate postedTimes in UTC
Investigating
1 h 22 min 100%
Updates
Times in UTCAs posted by Warp
Resolved
This incident has been resolved.
Investigating
We are continuing to investigate this issue.
Investigating
We are investigating an issue with Warp-hosted agents waiting to be assigned to sandboxes.
Affected components
1Cloud agent execution
Warp in the last 90 days
Full history90 days agoToday
Incidents in 90 days
4
Days with an incident
4
Median duration
3 h 40 min
This incident
63% shorter than the median
Other Warp incidents
All incidentsFollow Warp
Your coding agent knows when Warp is down, and tells you when a failure is theirs, not yours. You can also get Warp 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 "warp" and tell me if Warp 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=warpSlack
/feed subscribe https://outages.cc/feed.xml?providers=warpFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane