Live

Cloud agents failing to start for some customers

0

Warp reported that cloud agents failed to start for some customers, affecting Cloud agent execution. Warp later reported the incident resolved. The incident lasted about 51 minutes.

State

Resolved

Started

Lasted

51 min

Worst impact

Partial outage

Timeline

7 updates
19:4619:5820:1120:2420:36
Partial outageDegradedUpdate postedTimes in UTC

Investigating

5 min 11%

Identified

42 min 83%

Monitoring

3 min 7%

Updates

Times in UTC

As posted by Warp

Resolved

This incident has been resolved.

Monitoring

A fix has been implemented and we are monitoring the results.

Identified

We are continuing to work on a fix for this issue.

Identified

The issue has been identified and a fix is being implemented.

Identified

We are continuing to work on a fix for this issue.

Identified

The issue has been identified and a fix is being implemented.

Investigating

We are currently investigating this issue.

Affected components

1
Cloud agent execution

Warp in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

5

Median duration

1 h 58 min

This incident

57% shorter than the median

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

5 h 40 min
median 1 h 58 min
90 days agoToday

Other Warp incidents

All incidents

Follow 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.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 "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.live/feed.xml?providers=warp
Slack
/feed subscribe https://outages.live/feed.xml?providers=warp

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane