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 54 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 496 ms | 0 |
| Nov 7 | 0 | 0.0 | 504 ms | 0 |
| Nov 7 | 0 | 0.0 | 831 ms | 0 |
| Nov 7 | 0 | 0.0 | 469 ms | 0 |
| Nov 7 | 0 | 0.0 | 1038 ms | 0 |
| Nov 8 | 0 | 0.0 | 340 ms | 0 |
| Nov 8 | 0 | 0.0 | 433 ms | 0 |
| Nov 8 | 0 | 0.0 | 477 ms | 0 |
| Nov 8 | 0 | 0.0 | 591 ms | 0 |
| Nov 9 | 0 | 0.0 | 428 ms | 0 |
| Nov 9 | 0 | 0.0 | 434 ms | 0 |
| Nov 9 | 0 | 0.0 | 575 ms | 0 |
| Nov 9 | 0 | 0.0 | 535 ms | 0 |
| Nov 10 | 0 | 0.0 | 440 ms | 0 |
| Nov 10 | 0 | 0.0 | 392 ms | 0 |
| Nov 10 | 0 | 0.0 | 264 ms | 0 |
| Nov 10 | 0 | 0.0 | 471 ms | 0 |
| Nov 11 | 0 | 0.0 | 489 ms | 0 |
| Nov 11 | 0 | 0.0 | 651 ms | 0 |
| Nov 11 | 0 | 0.0 | 544 ms | 0 |
| Nov 11 | 0 | 0.0 | 504 ms | 0 |
| Nov 12 | 0 | 0.0 | 488 ms | 0 |
| Nov 12 | 0 | 0.0 | 461 ms | 0 |
| Nov 12 | 0 | 0.0 | 404 ms | 0 |
| Nov 12 | 0 | 0.0 | 446 ms | 0 |
| Nov 13 | 0 | 0.0 | 454 ms | 0 |
| Nov 13 | 0 | 0.0 | 322 ms | 0 |
| Nov 13 | 0 | 0.0 | 452 ms | 0 |
| Nov 13 | 0 | 0.0 | 441 ms | 0 |
| Nov 14 | 0 | 0.0 | 454 ms | 0 |
| Nov 14 | 0 | 0.0 | 543 ms | 0 |
| Nov 14 | 0 | 0.0 | 478 ms | 0 |
| Nov 14 | 0 | 0.0 | 537 ms | 0 |
| Nov 15 | 0 | 0.0 | 549 ms | 0 |
| Nov 15 | 0 | 0.0 | 461 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.