User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
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 27 min ago. Last stored result reached it in 614 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1965 ms | 0 |
| Nov 7 | 0 | 0.0 | 646 ms | 0 |
| Nov 7 | 0 | 0.0 | 572 ms | 0 |
| Nov 7 | 0 | 0.0 | 601 ms | 0 |
| Nov 7 | 0 | 0.0 | 518 ms | 0 |
| Nov 8 | 0 | 0.0 | 604 ms | 0 |
| Nov 8 | 0 | 0.0 | 552 ms | 0 |
| Nov 8 | 0 | 0.0 | 563 ms | 0 |
| Nov 8 | 0 | 0.0 | 559 ms | 0 |
| Nov 9 | 0 | 0.0 | 588 ms | 0 |
| Nov 9 | 0 | 0.0 | 552 ms | 0 |
| Nov 9 | 0 | 0.0 | 618 ms | 0 |
| Nov 9 | 0 | 0.0 | 641 ms | 0 |
| Nov 10 | 0 | 0.0 | 585 ms | 0 |
| Nov 10 | 0 | 0.0 | 595 ms | 0 |
| Nov 10 | 0 | 0.0 | 653 ms | 0 |
| Nov 10 | 0 | 0.0 | 548 ms | 0 |
| Nov 11 | 0 | 0.0 | 584 ms | 0 |
| Nov 11 | 0 | 0.0 | 552 ms | 0 |
| Nov 11 | 0 | 0.0 | 604 ms | 0 |
| Nov 11 | 0 | 0.0 | 794 ms | 0 |
| Nov 12 | 0 | 0.0 | 596 ms | 0 |
| Nov 12 | 0 | 0.0 | 619 ms | 0 |
| Nov 12 | 0 | 0.0 | 715 ms | 0 |
| Nov 12 | 0 | 0.0 | 544 ms | 0 |
| Nov 13 | 0 | 0.0 | 510 ms | 0 |
| Nov 13 | 0 | 0.0 | 613 ms | 0 |
| Nov 13 | 0 | 0.0 | 641 ms | 0 |
| Nov 13 | 0 | 0.0 | 614 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 Adit 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 Adit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Adit alerts to Slack, Discord or a webhook — free.
Adit is listed in our Health category and checked at adit.com. Adit is an all-in-one AI-powered patient communication and engagement platform for dental practices, combining calls, messaging, scheduling, forms, payments, and automation.
Adit publishes an official status page at status.adit.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
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: 578 ms average, 463–692 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 Adit incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
578 ms on average over the last 24 hours (463–692 ms).
Yes, at https://status.adit.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Adit here at once, the problem is on Adit'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 Adit. 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.