outages.live
Live

Warp

Warp is operational

Checked Operational

User reports

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

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Warp since . The days before that show only what Warp published.

Incidents in 90 days

4

Days with an incident

4

Median duration

3 h 40 min

Longest incident

5 h 40 min

Components

9
warp.dev Operational
90 days agoNo incidentsToday
Account, team, and data services Operational
90 days ago1 day with an incidentToday
Live sessions and agent control Operational
90 days ago2 days with an incidentToday
Cloud agent execution Operational
90 days ago1 day with an incidentToday
Warp agent harness Operational
90 days agoNo incidentsToday
Automations and integrations Operational
90 days ago1 day with an incidentToday
Web app Operational
90 days ago1 day with an incidentToday
Warp Client Operational
90 days agoNo incidentsToday
Downloads and updates Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration5 h 40 min to Degraded API reliabilityDegraded

This incident has been resolved.

Oct 20, 2026

Duration1 h 22 min to Warp-hosted agents waiting to be assigned to sandboxesDegraded

This incident has been resolved.

Oct 16, 2026

Duration2 h 35 min to Scheduled cloud agents unavailablePartial outage

This incident has been resolved.

Sep 30, 2026

Duration4 h 45 min to Session sharing is degradedDegraded

This incident has been 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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane