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 43 min ago. Last stored result reached it in 176 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 237 ms | 0 |
| Tue 00 | 0 | 0.0 | 264 ms | 0 |
| Tue 02 | 0 | 0.0 | 396 ms | 0 |
| Tue 04 | 0 | 0.0 | 489 ms | 0 |
| Tue 06 | 0 | 0.0 | 506 ms | 0 |
| Tue 08 | 0 | 0.0 | 290 ms | 0 |
| Tue 10 | 0 | 0.0 | 320 ms | 0 |
| Tue 12 | 0 | 0.0 | 260 ms | 0 |
| Tue 15 | 0 | 0.0 | 558 ms | 0 |
| Tue 17 | 0 | 0.0 | 488 ms | 0 |
| Tue 19 | 0 | 0.0 | 419 ms | 0 |
| Tue 21 | 0 | 0.0 | 310 ms | 0 |
| Wed 00 | 0 | 0.0 | 308 ms | 0 |
| Wed 02 | 0 | 0.0 | 386 ms | 0 |
| Wed 04 | 0 | 0.0 | 525 ms | 0 |
| Wed 06 | 0 | 0.0 | 508 ms | 0 |
| Wed 09 | 0 | 0.0 | 401 ms | 0 |
| Wed 10 | 0 | 0.0 | 163 ms | 0 |
| Wed 13 | 0 | 0.0 | 579 ms | 0 |
| Wed 15 | 0 | 0.0 | 461 ms | 0 |
| Wed 17 | 0 | 0.0 | 279 ms | 0 |
| Wed 19 | 0 | 0.0 | 226 ms | 0 |
| Wed 21 | 0 | 0.0 | 285 ms | 0 |
| Wed 23 | 0 | 0.0 | 296 ms | 0 |
| Thu 02 | 0 | 0.0 | 295 ms | 0 |
| Thu 04 | 0 | 0.0 | 411 ms | 0 |
| Thu 06 | 0 | 0.0 | 552 ms | 0 |
| Thu 08 | 0 | 0.0 | 440 ms | 0 |
| Thu 10 | 0 | 0.0 | 367 ms | 0 |
| Thu 12 | 0 | 0.0 | 558 ms | 0 |
| Thu 14 | 0 | 0.0 | 437 ms | 0 |
| Thu 16 | 0 | 0.0 | 541 ms | 0 |
| Thu 18 | 0 | 0.0 | 426 ms | 0 |
| Thu 20 | 0 | 0.0 | 555 ms | 0 |
| Thu 22 | 0 | 0.0 | 753 ms | 0 |
| Fri 00 | 0 | 0.0 | 292 ms | 0 |
| Fri 02 | 0 | 0.0 | 543 ms | 0 |
| Fri 04 | 0 | 0.0 | 619 ms | 0 |
| Fri 06 | 0 | 0.0 | 429 ms | 0 |
| Fri 08 | 0 | 0.0 | 316 ms | 0 |
| Fri 10 | 0 | 0.0 | 393 ms | 0 |
| Fri 11 | 0 | 0.0 | 356 ms | 0 |
| Fri 13 | 0 | 0.0 | 323 ms | 0 |
| Fri 15 | 0 | 0.0 | 514 ms | 0 |
| Fri 17 | 0 | 0.0 | 518 ms | 0 |
| Fri 19 | 0 | 0.0 | 368 ms | 0 |
| Fri 21 | 0 | 0.0 | 542 ms | 0 |
| Fri 22 | 0 | 0.0 | 176 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 Numa 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 Numa goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Numa alerts to Slack, Discord or a webhook — free.
We track Numa (numa.com) as part of the AI group. Numa is the AI Operating System for Car Dealerships. 1,500+ rooftops run on Numa to answer every call, book appointments, and protect CSI in real time.
Numa publishes an official status page at status.numa.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: 417 ms average, 73–720 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 Numa incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
417 ms on average over the last 24 hours (73–720 ms).
Yes, at https://status.numa.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 Numa here at once, the problem is on Numa'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 Numa. 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.