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 5 min ago. Last stored result reached it in 126 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 358 ms | 0 |
| Mon 18 | 0 | 0.0 | 92 ms | 0 |
| Mon 20 | 0 | 0.0 | 87 ms | 0 |
| Mon 22 | 0 | 0.0 | 70 ms | 0 |
| Tue 00 | 0 | 0.0 | 76 ms | 0 |
| Tue 02 | 0 | 0.0 | 179 ms | 0 |
| Tue 04 | 0 | 0.0 | 70 ms | 0 |
| Tue 06 | 0 | 0.0 | 421 ms | 0 |
| Tue 08 | 0 | 0.0 | 179 ms | 0 |
| Tue 10 | 0 | 0.0 | 156 ms | 0 |
| Tue 12 | 0 | 0.0 | 172 ms | 0 |
| Tue 15 | 0 | 0.0 | 144 ms | 0 |
| Tue 17 | 0 | 0.0 | 180 ms | 0 |
| Tue 19 | 0 | 0.0 | 136 ms | 0 |
| Tue 21 | 0 | 0.0 | 77 ms | 0 |
| Wed 00 | 0 | 0.0 | 267 ms | 0 |
| Wed 02 | 0 | 0.0 | 76 ms | 0 |
| Wed 04 | 0 | 0.0 | 209 ms | 0 |
| Wed 06 | 0 | 0.0 | 99 ms | 0 |
| Wed 09 | 0 | 0.0 | 76 ms | 0 |
| Wed 11 | 0 | 0.0 | 226 ms | 0 |
| Wed 13 | 0 | 0.0 | 201 ms | 0 |
| Wed 15 | 0 | 0.0 | 155 ms | 0 |
| Wed 17 | 0 | 0.0 | 108 ms | 0 |
| Wed 19 | 0 | 0.0 | 62 ms | 0 |
| Wed 22 | 0 | 0.0 | 119 ms | 0 |
| Thu 00 | 0 | 0.0 | 170 ms | 0 |
| Thu 01 | 0 | 0.0 | 184 ms | 0 |
| Thu 03 | 0 | 0.0 | 187 ms | 0 |
| Thu 05 | 0 | 0.0 | 181 ms | 0 |
| Thu 07 | 0 | 0.0 | 176 ms | 0 |
| Thu 09 | 0 | 0.0 | 181 ms | 0 |
| Thu 11 | 0 | 0.0 | 180 ms | 0 |
| Thu 13 | 0 | 0.0 | 209 ms | 0 |
| Thu 15 | 0 | 0.0 | 134 ms | 0 |
| Thu 18 | 0 | 0.0 | 143 ms | 0 |
| Thu 20 | 0 | 0.0 | 80 ms | 0 |
| Thu 22 | 0 | 0.0 | 153 ms | 0 |
| Fri 00 | 0 | 0.0 | 76 ms | 0 |
| Fri 02 | 0 | 0.0 | 109 ms | 0 |
| Fri 04 | 0 | 0.0 | 210 ms | 0 |
| Fri 06 | 0 | 0.0 | 249 ms | 0 |
| Fri 08 | 0 | 0.0 | 108 ms | 0 |
| Fri 10 | 0 | 0.0 | 166 ms | 0 |
| Fri 12 | 0 | 0.0 | 85 ms | 0 |
| Fri 14 | 0 | 0.0 | 138 ms | 0 |
| Fri 16 | 0 | 0.0 | 126 ms | 0 |
| Fri 17 | 0 | 0.0 | 84 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CallGrid 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 CallGrid goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CallGrid alerts to Slack, Discord or a webhook — free.
CallGrid is listed in our AI category and checked at callgrid.com. CallGrid routes and sells inbound calls through a real-time double-blind auction, billing on talk time, with AI in the routing decision. Built for sub-100ms post-dial delay.
CallGrid publishes an official status page at status.callgrid.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 133 ms average, 76–249 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CallGrid incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
133 ms on average over the last 24 hours (76–249 ms).
Yes, at https://status.callgrid.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 CallGrid here at once, the problem is on CallGrid'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 CallGrid. 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.