outages.live
Live
WarpIncident ·

Scheduled cloud agents unavailable

ResolvedOfficial update

This incident has been resolved.

The latest update from Warp.

State

Resolved

Started

Lasted

2 h 35 min

Worst impact

Partial outage

Timeline

3 updates
15:3416:1316:5217:3018:09
Partial outageUpdate postedTimes in UTC

Identified

2 h 14 min 87%

Monitoring

20 min 13%

Updates

Times in UTC

As posted by Warp

Resolved

This incident has been resolved.

Monitoring

We have rolled out a remediation and are monitoring recovery.

Identified

We are currently investigating a regression which prevents Oz scheduled cloud agents from executing.

Affected components

1
Automations and integrations

Warp in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

3 h 40 min

This incident

30% 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 3 h 40 min
90 days agoToday

Other Warp incidents

All incidents

Warp·Degraded API reliability

This incident has been resolved.

Resolved

Warp·Warp-hosted agents waiting to be assigned to sandboxes

This incident has been resolved.

Resolved

Warp·Session sharing is degraded

This incident has been resolved.

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane