HealthSherpa Outage History

18 incidents recorded over the last 365 days, 1 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live HealthSherpa status100.00% uptime history

Every Recorded HealthSherpa Incident

HealthSherpa incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Maintenance Reservation [Potential Hold]HealthSherpa is reserving this time slot for a potential after-hours maintenance. The time slot will be updated with details of the maintenance event ahead of time if HealthSherpa decides to use it. If the time slot…4h 0mScheduled
Oct 25, 2026Maintenance Reservation [Potential Hold]HealthSherpa is reserving this time slot for a potential after-hours maintenance. The time slot will be updated with details of the maintenance event ahead of time if HealthSherpa decides to use it. If the time slot…4h 0mScheduled
Oct 19, 2026Maintenance Reservation [Potential Hold]HealthSherpa is reserving this time slot for a potential after-hours maintenance. The time slot will be updated with details of the maintenance event ahead of time if HealthSherpa decides to use it. If the time slot…4h 0mScheduled
Oct 18, 2026Scheduled Maintenance - DatabaseVerification is currently underway for the maintenance items.4h 0mScheduled
Oct 12, 2026Scheduled Maintenance - DatabaseScheduled maintenance is currently in progress. We will provide updates as necessary.4h 0mScheduled
Oct 11, 2026Scheduled Maintenance - DatabaseScheduled maintenance is currently in progress. We will provide updates as necessary.4h 0mScheduled
Oct 5, 2026Maintenance Reservation [Potential Hold]HealthSherpa is reserving this time slot for a potential after-hours maintenance. The time slot will be updated with details of the maintenance event ahead of time if HealthSherpa decides to use it. If the time slot…4h 0mScheduled
Oct 4, 2026Maintenance Reservation [Potential Hold]HealthSherpa is reserving this time slot for a potential after-hours maintenance. The time slot will be updated with details of the maintenance event ahead of time if HealthSherpa decides to use it. If the time slot…4h 0mScheduled
Sep 21, 2026Scheduled Maintenance - DatabaseScheduled maintenance is currently in progress. We will provide updates as necessary.4h 0mScheduled
Aug 17, 2026Scheduled Maintenance - DatabaseThe scheduled maintenance has been completed.4h 0mScheduled
Jun 23, 2026Issue with Client List and SearchThis incident has been resolved.32 minResolved
Feb 2, 2026Maintenance Reservation [Potential Hold]The scheduled maintenance has been completed.4h 0mScheduled
Feb 1, 2026Maintenance Reservation [Potential Hold]The scheduled maintenance has been completed.4h 0mScheduled
Jan 26, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jan 26, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jan 25, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jan 19, 2026Maintenance Reservation [Potential Hold]The scheduled maintenance has been completed.4h 0mScheduled
Jan 18, 2026Maintenance Reservation [Potential Hold]The scheduled maintenance has been completed.4h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next HealthSherpa incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This HealthSherpa Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before HealthSherpa acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single HealthSherpa outage in this window ran 4h, against a mean recovery of 3h 48m. If you depend on HealthSherpa in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.