Healthie Outage History

Healthie is up right now

Pingoru has recorded 85 incidents for Healthie: 81 in the last 12 months and 15 in the last 90 days.

Source: status.gethealthie.com

85incidents recorded
81last 12 months
15last 90 days
11 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Healthie in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026555 of 720 (8%)
May 202673 of 744 (0%)
June 202686 of 720 (1%)
July 2026844 of 744 (6%)
August 202668 of 744 (1%)
September 20264165 of 720 (23%)
October 202633 of 593 (1%)

Incidents, newest first

Critical October 20, 2025 Healthie is unavailable due to AWS incident 4h 58m Healthie (Production), Healthie (Sandbox)

Started Oct 20, 2025, 07:21 AM UTC· resolved Oct 20, 2025, 12:19 PM UTC

  1. investigating Oct 20, 2025, 07:21 AM UTC

    Our hosting provider, AWS, is currently experiencing a substantial incident with multiple services. This is causing the Healthie platform to become unavailable. The AWS incident can be followed here: https://health.aws.amazon.com/health/status The most recent update from AWS is: "Oct 20 12:11 AM PDT We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region"

  2. resolved Oct 20, 2025, 12:19 PM UTC

    AWS has recovered most services and Healthie became available again at ~5 AM eastern. We are continuing to monitor.

Read the full incident report →

Notice October 17, 2025 Possible Delay in ChangeHealth Lab Results 6d 4h Healthie (Production)

Started Oct 17, 2025, 05:24 PM UTC· resolved Oct 23, 2025, 10:17 PM UTC

  1. investigating Oct 17, 2025, 05:24 PM UTC

    We are investigating possible delays in pulling results from ChangeHealth. This is specific to Change Health. eLabs Direct by Healthie, Rupa, etc are not impacted.

  2. investigating Oct 20, 2025, 12:20 PM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 23, 2025, 10:17 PM UTC

    This is now resolved.

Read the full incident report →