User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
healthsherpa.com · Cloud & developer
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 16 min ago. Last stored result reached it in 464 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 12 | 0 | 0.0 | 587 ms | 0 |
| Wed 14 | 0 | 0.0 | 483 ms | 0 |
| Wed 16 | 0 | 0.0 | 544 ms | 0 |
| Wed 18 | 0 | 0.0 | 281 ms | 0 |
| Wed 21 | 0 | 0.0 | 504 ms | 0 |
| Wed 23 | 0 | 0.0 | 520 ms | 0 |
| Thu 01 | 0 | 0.0 | 488 ms | 0 |
| Thu 03 | 0 | 0.0 | 453 ms | 0 |
| Thu 05 | 0 | 0.0 | 602 ms | 0 |
| Thu 07 | 0 | 0.0 | 461 ms | 0 |
| Thu 09 | 0 | 0.0 | 484 ms | 0 |
| Thu 11 | 0 | 0.0 | 242 ms | 0 |
| Thu 13 | 0 | 0.0 | 353 ms | 0 |
| Thu 15 | 0 | 0.0 | 477 ms | 0 |
| Thu 17 | 0 | 0.0 | 278 ms | 0 |
| Thu 20 | 0 | 0.0 | 446 ms | 0 |
| Thu 22 | 0 | 0.0 | 312 ms | 0 |
| Fri 00 | 0 | 0.0 | 418 ms | 0 |
| Fri 02 | 0 | 0.0 | 454 ms | 0 |
| Fri 04 | 0 | 0.0 | 555 ms | 0 |
| Fri 06 | 0 | 0.0 | 258 ms | 0 |
| Fri 08 | 0 | 0.0 | 386 ms | 0 |
| Fri 10 | 0 | 0.0 | 431 ms | 0 |
| Fri 11 | 0 | 0.0 | 229 ms | 0 |
| Fri 13 | 0 | 0.0 | 474 ms | 0 |
| Fri 15 | 0 | 0.0 | 277 ms | 0 |
| Fri 17 | 0 | 0.0 | 452 ms | 0 |
| Fri 18 | 0 | 0.0 | 418 ms | 0 |
| Fri 20 | 0 | 0.0 | 436 ms | 0 |
| Fri 21 | 0 | 0.0 | 463 ms | 0 |
| Fri 22 | 0 | 0.0 | 449 ms | 0 |
| Fri 23 | 0 | 0.0 | 441 ms | 0 |
| Sat 01 | 0 | 0.0 | 454 ms | 0 |
| Sat 03 | 0 | 0.0 | 385 ms | 0 |
| Sat 05 | 0 | 0.0 | 585 ms | 0 |
| Sat 07 | 0 | 0.0 | 768 ms | 0 |
| Sat 09 | 0 | 0.0 | 617 ms | 0 |
| Sat 11 | 0 | 0.0 | 268 ms | 0 |
| Sat 14 | 0 | 0.0 | 492 ms | 0 |
| Sat 16 | 0 | 0.0 | 464 ms | 0 |
| Sat 18 | 0 | 0.0 | 471 ms | 0 |
| Sat 21 | 0 | 0.0 | 606 ms | 0 |
| Sat 23 | 0 | 0.0 | 537 ms | 0 |
| Sun 01 | 0 | 0.0 | 434 ms | 0 |
| Sun 03 | 0 | 0.0 | 663 ms | 0 |
| Sun 06 | 0 | 0.0 | 528 ms | 0 |
| Sun 08 | 0 | 0.0 | 457 ms | 0 |
| Sun 10 | 0 | 0.0 | 446 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for HealthSherpa 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 HealthSherpa goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track HealthSherpa (healthsherpa.com) as part of the Cloud & developer group. Optimize your business with the largest ACA quoting and enrollment platform for agents and agencies.
HealthSherpa publishes an official status page at status.healthsherpa.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 468 ms average, 67–663 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 HealthSherpa incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
468 ms on average over the last 24 hours (67–663 ms).
Yes, at https://status.healthsherpa.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report HealthSherpa here at once, the problem is on HealthSherpa'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 HealthSherpa. 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.