User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Call queue/phone tree issue
Source: the vendor's status page · We are not affiliated with Weave.
Estimated fix: Not enough Weave history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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 15 min ago. Last stored result reached it in 183 ms.
Minor incident
Call queue/phone tree issue Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 325 ms | 0 |
| Nov 7 | 0 | 0.0 | 172 ms | 0 |
| Nov 7 | 0 | 0.0 | 365 ms | 0 |
| Nov 7 | 0 | 0.0 | 277 ms | 0 |
| Nov 7 | 0 | 0.0 | 256 ms | 0 |
| Nov 8 | 0 | 0.0 | 322 ms | 0 |
| Nov 8 | 0 | 0.0 | 322 ms | 0 |
| Nov 8 | 0 | 0.0 | 319 ms | 0 |
| Nov 8 | 0 | 0.0 | 348 ms | 0 |
| Nov 9 | 0 | 0.0 | 469 ms | 0 |
| Nov 9 | 0 | 0.0 | 305 ms | 0 |
| Nov 9 | 0 | 0.0 | 272 ms | 0 |
| Nov 9 | 0 | 0.0 | 277 ms | 0 |
| Nov 10 | 0 | 0.0 | 287 ms | 0 |
| Nov 10 | 0 | 0.0 | 309 ms | 0 |
| Nov 10 | 0 | 0.0 | 297 ms | 0 |
| Nov 10 | 0 | 0.0 | 260 ms | 0 |
| Nov 11 | 0 | 0.0 | 368 ms | 0 |
| Nov 11 | 0 | 0.0 | 389 ms | 0 |
| Nov 11 | 0 | 0.0 | 411 ms | 0 |
| Nov 11 | 0 | 0.0 | 360 ms | 0 |
| Nov 12 | 0 | 0.0 | 260 ms | 0 |
| Nov 12 | 0 | 0.0 | 331 ms | 0 |
| Nov 12 | 0 | 0.0 | 275 ms | 0 |
| Nov 12 | 0 | 0.0 | 213 ms | 0 |
| Nov 13 | 0 | 0.0 | 284 ms | 0 |
| Nov 13 | 0 | 0.0 | 212 ms | 0 |
| Nov 13 | 0 | 0.0 | 404 ms | 0 |
| Nov 13 | 0 | 0.0 | 183 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 Weave 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 Weave goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Weave alerts to Slack, Discord or a webhook — free.
We track Weave (getweave.com) as part of the AI group. Weave brings together a world-class phone system and a suite of communication tools, so it's easy to automate more tasks, keep schedules full, get paid faster, collect more reviews and much more.
Weave publishes an official status page at status.getweave.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 293 ms average, 183–446 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Call queue/phone tree issue
We have not recorded a public Weave incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
293 ms on average over the last 24 hours (183–446 ms).
Yes, at https://status.getweave.com.
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 Weave here at once, the problem is on Weave'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 Weave. 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.