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 54 min ago. Last stored result reached it in 467 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 06 | 0 | 0.0 | 458 ms | 0 |
| Mon 08 | 0 | 0.0 | 609 ms | 0 |
| Mon 10 | 0 | 0.0 | 281 ms | 0 |
| Mon 12 | 0 | 0.0 | 343 ms | 0 |
| Mon 14 | 0 | 0.0 | 547 ms | 0 |
| Mon 16 | 0 | 0.0 | 473 ms | 0 |
| Mon 18 | 0 | 0.0 | 303 ms | 0 |
| Mon 20 | 0 | 0.0 | 309 ms | 0 |
| Mon 22 | 0 | 0.0 | 487 ms | 0 |
| Tue 01 | 0 | 0.0 | 661 ms | 0 |
| Tue 03 | 0 | 0.0 | 410 ms | 0 |
| Tue 05 | 0 | 0.0 | 443 ms | 0 |
| Tue 07 | 0 | 0.0 | 490 ms | 0 |
| Tue 09 | 0 | 0.0 | 393 ms | 0 |
| Tue 11 | 0 | 0.0 | 519 ms | 0 |
| Tue 13 | 0 | 0.0 | 599 ms | 0 |
| Tue 16 | 0 | 0.0 | 589 ms | 0 |
| Tue 18 | 0 | 0.0 | 577 ms | 0 |
| Tue 20 | 0 | 0.0 | 407 ms | 0 |
| Tue 22 | 0 | 0.0 | 1381 ms | 0 |
| Wed 00 | 0 | 0.0 | 580 ms | 0 |
| Wed 03 | 0 | 0.0 | 604 ms | 0 |
| Wed 05 | 0 | 0.0 | 383 ms | 0 |
| Wed 07 | 0 | 0.0 | 287 ms | 0 |
| Wed 09 | 0 | 0.0 | 544 ms | 0 |
| Wed 12 | 0 | 0.0 | 405 ms | 0 |
| Wed 14 | 0 | 0.0 | 391 ms | 0 |
| Wed 16 | 0 | 0.0 | 574 ms | 0 |
| Wed 18 | 0 | 0.0 | 404 ms | 0 |
| Wed 20 | 0 | 0.0 | 401 ms | 0 |
| Wed 22 | 0 | 0.0 | 396 ms | 0 |
| Thu 01 | 0 | 0.0 | 326 ms | 0 |
| Thu 03 | 0 | 0.0 | 447 ms | 0 |
| Thu 05 | 0 | 0.0 | 450 ms | 0 |
| Thu 07 | 0 | 0.0 | 391 ms | 0 |
| Thu 09 | 0 | 0.0 | 405 ms | 0 |
| Thu 11 | 0 | 0.0 | 478 ms | 0 |
| Thu 13 | 0 | 0.0 | 308 ms | 0 |
| Thu 15 | 0 | 0.0 | 675 ms | 0 |
| Thu 16 | 0 | 0.0 | 577 ms | 0 |
| Thu 19 | 0 | 0.0 | 612 ms | 0 |
| Thu 21 | 0 | 0.0 | 406 ms | 0 |
| Thu 22 | 0 | 0.0 | 730 ms | 0 |
| Fri 01 | 0 | 0.0 | 299 ms | 0 |
| Fri 03 | 0 | 0.0 | 409 ms | 0 |
| Fri 05 | 0 | 0.0 | 319 ms | 0 |
| Fri 07 | 0 | 0.0 | 588 ms | 0 |
| Fri 09 | 0 | 0.0 | 467 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 CertifyOS 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 CertifyOS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CertifyOS alerts to Slack, Discord or a webhook — free.
We track CertifyOS (certifyos.com) as part of the Health group. Get frictionless, API first credentialing, licensing, enrollment, and network monitoring for payers, providers, health systems and rapidly scaling digital health companies.
CertifyOS publishes an official status page at status.certifyos.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 474 ms average, 285–730 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CertifyOS incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
474 ms on average over the last 24 hours (285–730 ms).
Yes, at https://status.certifyos.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 CertifyOS here at once, the problem is on CertifyOS'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 CertifyOS. 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.