Healthie incident

Slow response times, pages failing to load

Critical Resolved View vendor source →

Healthie experienced a critical incident on February 13, 2026 affecting Healthie (Production), lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2026, 08:09 PM UTC
Resolved
Feb 13, 2026, 08:42 PM UTC
Duration
33m
Detected by Pingoru
Feb 13, 2026, 08:09 PM UTC

Affected components

Healthie (Production)

Update timeline

  1. investigating Feb 13, 2026, 07:35 PM UTC

    We're investigating slow response times and increased error rates. In some cases, Healthie might not load at all.

  2. investigating Feb 13, 2026, 07:50 PM UTC

    Our team is actively working to resolve this issue. Healthie may be inaccessible via web and mobile apps at this time. We'll post another update as soon as we have more information.

  3. investigating Feb 13, 2026, 08:01 PM UTC

    We have seen performance continue to degrade and most queries are now not returning successfully. Our team believes we've identified the issue with our infrastructure, and are working to resolve as fast as possible.

  4. investigating Feb 13, 2026, 08:09 PM UTC

    We identified the issue to be a sudden failure to be able to connect to an underlying AWS database. We were able to route around that connection for now and service was restored at ~3:03pm eastern. We saw slow performance between ~2:20-2:35pm eastern, and then downtime from ~2:35pm to 3:03pm eastern.

  5. investigating Feb 13, 2026, 08:09 PM UTC

    Healthie is back online. We're continuing to monitor for any remaining issues.

  6. investigating Feb 13, 2026, 08:10 PM UTC

    Please see prior message.

  7. resolved Feb 13, 2026, 08:42 PM UTC

    Performance is stable across the board. This incident is now resolved.