User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 46 min ago. Last stored result reached it in 308 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 501 ms | 0 |
| Mon 20 | 0 | 0.0 | 419 ms | 0 |
| Mon 22 | 0 | 0.0 | 519 ms | 0 |
| Tue 00 | 0 | 0.0 | 433 ms | 0 |
| Tue 02 | 0 | 0.0 | 388 ms | 0 |
| Tue 05 | 0 | 0.0 | 446 ms | 0 |
| Tue 07 | 0 | 0.0 | 458 ms | 0 |
| Tue 09 | 0 | 0.0 | 492 ms | 0 |
| Tue 11 | 0 | 0.0 | 424 ms | 0 |
| Tue 13 | 0 | 0.0 | 373 ms | 0 |
| Tue 15 | 0 | 0.0 | 451 ms | 0 |
| Tue 18 | 0 | 0.0 | 300 ms | 0 |
| Tue 20 | 0 | 0.0 | 507 ms | 0 |
| Tue 22 | 0 | 0.0 | 316 ms | 0 |
| Wed 00 | 0 | 0.0 | 324 ms | 0 |
| Wed 03 | 0 | 0.0 | 451 ms | 0 |
| Wed 05 | 0 | 0.0 | 504 ms | 0 |
| Wed 07 | 0 | 0.0 | 324 ms | 0 |
| Wed 09 | 0 | 0.0 | 398 ms | 0 |
| Wed 12 | 0 | 0.0 | 347 ms | 0 |
| Wed 14 | 0 | 0.0 | 544 ms | 0 |
| Wed 16 | 0 | 0.0 | 413 ms | 0 |
| Wed 18 | 0 | 0.0 | 550 ms | 0 |
| Wed 20 | 0 | 0.0 | 538 ms | 0 |
| Wed 22 | 0 | 0.0 | 350 ms | 0 |
| Thu 01 | 0 | 0.0 | 344 ms | 0 |
| Thu 03 | 0 | 0.0 | 497 ms | 0 |
| Thu 05 | 0 | 0.0 | 417 ms | 0 |
| Thu 06 | 0 | 0.0 | 353 ms | 0 |
| Thu 08 | 0 | 0.0 | 350 ms | 0 |
| Thu 10 | 0 | 0.0 | 640 ms | 0 |
| Thu 12 | 0 | 0.0 | 416 ms | 0 |
| Thu 14 | 0 | 0.0 | 273 ms | 0 |
| Thu 16 | 0 | 0.0 | 408 ms | 0 |
| Thu 18 | 0 | 0.0 | 585 ms | 0 |
| Thu 20 | 0 | 0.0 | 348 ms | 0 |
| Thu 22 | 0 | 0.0 | 456 ms | 0 |
| Fri 00 | 0 | 0.0 | 343 ms | 0 |
| Fri 02 | 0 | 0.0 | 424 ms | 0 |
| Fri 04 | 0 | 0.0 | 275 ms | 0 |
| Fri 06 | 0 | 0.0 | 314 ms | 0 |
| Fri 08 | 0 | 0.0 | 331 ms | 0 |
| Fri 10 | 0 | 0.0 | 375 ms | 0 |
| Fri 12 | 0 | 0.0 | 430 ms | 0 |
| Fri 14 | 0 | 0.0 | 391 ms | 0 |
| Fri 16 | 0 | 0.0 | 412 ms | 0 |
| Fri 18 | 0 | 0.0 | 296 ms | 0 |
| Fri 19 | 0 | 0.0 | 308 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Warp yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Warp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Warp alerts to Slack, Discord or a webhook — free.
Warp, at warp.dev, is one of the AI services we monitor. Build your software factory on Warp: factories as code, any model or harness, with evals, benchmarks, and self-improvement built in.
Warp publishes an official status page at status.warp.dev; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 367 ms average, 275–567 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Warp incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
367 ms on average over the last 24 hours (275–567 ms).
Yes, at https://status.warp.dev.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Warp here at once, the problem is on Warp's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Warp. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.