User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
Is Incode down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → incode.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 35 min ago. Last stored result reached it in 425 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 331 ms | 0 |
| Mon 15 | 0 | 0.0 | 413 ms | 0 |
| Mon 17 | 0 | 0.0 | 303 ms | 0 |
| Mon 19 | 0 | 0.0 | 389 ms | 0 |
| Mon 21 | 0 | 0.0 | 380 ms | 0 |
| Mon 23 | 0 | 0.0 | 411 ms | 0 |
| Tue 01 | 0 | 0.0 | 506 ms | 0 |
| Tue 03 | 0 | 0.0 | 325 ms | 0 |
| Tue 05 | 0 | 0.0 | 312 ms | 0 |
| Tue 08 | 0 | 0.0 | 357 ms | 0 |
| Tue 10 | 0 | 0.0 | 358 ms | 0 |
| Tue 12 | 0 | 0.0 | 282 ms | 0 |
| Tue 14 | 0 | 0.0 | 279 ms | 0 |
| Tue 16 | 0 | 0.0 | 323 ms | 0 |
| Tue 18 | 0 | 0.0 | 275 ms | 0 |
| Tue 21 | 0 | 0.0 | 361 ms | 0 |
| Tue 23 | 0 | 0.0 | 432 ms | 0 |
| Wed 01 | 0 | 0.0 | 439 ms | 0 |
| Wed 03 | 0 | 0.0 | 288 ms | 0 |
| Wed 06 | 0 | 0.0 | 297 ms | 0 |
| Wed 08 | 0 | 0.0 | 288 ms | 0 |
| Wed 10 | 0 | 0.0 | 216 ms | 0 |
| Wed 12 | 0 | 0.0 | 302 ms | 0 |
| Wed 14 | 0 | 0.0 | 421 ms | 0 |
| Wed 16 | 0 | 0.0 | 292 ms | 0 |
| Wed 19 | 0 | 0.0 | 268 ms | 0 |
| Wed 21 | 0 | 0.0 | 325 ms | 0 |
| Wed 23 | 0 | 0.0 | 352 ms | 0 |
| Thu 01 | 0 | 0.0 | 333 ms | 0 |
| Thu 03 | 0 | 0.0 | 373 ms | 0 |
| Thu 05 | 0 | 0.0 | 324 ms | 0 |
| Thu 07 | 0 | 0.0 | 300 ms | 0 |
| Thu 09 | 0 | 0.0 | 281 ms | 0 |
| Thu 12 | 0 | 0.0 | 232 ms | 0 |
| Thu 14 | 0 | 0.0 | 445 ms | 0 |
| Thu 16 | 0 | 0.0 | 313 ms | 0 |
| Thu 17 | 0 | 0.0 | 243 ms | 0 |
| Thu 19 | 0 | 0.0 | 257 ms | 0 |
| Thu 21 | 0 | 0.0 | 313 ms | 0 |
| Thu 23 | 0 | 0.0 | 358 ms | 0 |
| Fri 01 | 0 | 0.0 | 402 ms | 0 |
| Fri 04 | 0 | 0.0 | 280 ms | 0 |
| Fri 06 | 0 | 0.0 | 324 ms | 0 |
| Fri 08 | 0 | 0.0 | 367 ms | 0 |
| Fri 10 | 0 | 0.0 | 407 ms | 0 |
| Fri 12 | 0 | 0.0 | 292 ms | 0 |
| Fri 14 | 0 | 0.0 | 412 ms | 0 |
| Fri 16 | 0 | 0.0 | 381 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Incode badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Incode yet. Outages of 10 minutes or more get their own page here.
Having trouble with Incode?
One report per service every 10 minutes from this network. No account.
Follow Incode
Get an email when Incode goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Incode alerts to Slack, Discord or a webhook — free.
About Incode
Incode, at incode.com, is one of the Health services we monitor. Identity verification software that checks documents, biometrics, and government records in one platform. Named a Leader in the 2026 Gartner Magic Quadrant.
Incode publishes an official status page at status.incode.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 344 ms average, 243–438 ms range across 14 successful checks.
Questions
Is Incode down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Incode last down?
We have not recorded a public Incode incident since monitoring began 8 days ago.
What is Incode's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Incode respond?
344 ms on average over the last 24 hours (243–438 ms).
Does Incode have an official status page?
Yes, at https://status.incode.com.
Incode not working for me but the status is fine. What now?
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 Incode here at once, the problem is on Incode'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 Incode. 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.