Hint Health Outage History

Hint Health is up right now

Pingoru has recorded 50 incidents for Hint Health: 1 in the last 12 months and 0 in the last 90 days.

Source: status.hint.com

50incidents recorded
1last 12 months
0last 90 days
39 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Hint Health 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 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 572 (0%)

Incidents, newest first

Major October 29, 2025 Authentication service degradation 39m Authentication

Started Oct 29, 2025, 04:19 PM UTC· resolved Oct 29, 2025, 04:58 PM UTC

  1. investigating Oct 29, 2025, 04:19 PM UTC

    Some users are currently experiencing a login issue due to degraded performance from our authentication provider, FrontEgg. This may prevent some users from accessing our application. FrontEgg is actively investigating and working to resolve the issue. We will continue to monitor the situation and provide updates as we learn more.

  2. monitoring Oct 29, 2025, 04:45 PM UTC

    Our auth provider mitigated the issue by switching our CDN provider. We are monitoring.

  3. resolved Oct 29, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 23, 2025 Authentication Full Outage — Resolved –

Started May 23, 2025, 05:00 PM UTC· resolved May 23, 2025, 05:00 PM UTC

  1. resolved May 23, 2025, 05:35 PM UTC

    Between 09:52 PT and 10:18 PT, our authentication vendor experienced an issue that resulted in errors during login attempts as well as session refreshes. As a result, customers were unable to sign in or continue using the app once their session tokens expired after the standard 15-minute window. At 10:18 PT, our vendor deployed a fix that restored normal authentication functionality. We are working with the vendor to understand the root cause and will provide a detailed update shortly on our status page.

Read the full incident report →

Notice April 24, 2025 Authentication Partial Outage — Resolved –

Started Apr 24, 2025, 12:00 PM UTC· resolved Apr 24, 2025, 12:00 PM UTC

  1. resolved Apr 24, 2025, 06:15 PM UTC

    Between 08:15 ET and 10:50 ET today, a subset of authentication edge servers maintained by our vendor in the Chicago region began returning errors. During this window, customers routed to one of these faulty nodes were unable to sign in or continue using the app—their session tokens failed to refresh after the standard 15-minute window. We estimate fewer than 200 users—primarily in Missouri, Wisconsin, Iowa, Indiana, Michigan, and Illinois—were affected. At 10:50 ET, we deployed a fix to restore full service. Monitoring confirms all authentication services are now operating normally. We apologize for the disruption and are working with our vendor to enhance fail-over and token-refresh resilience across their edge clusters.

Read the full incident report →

Notice November 19, 2024 Inability to use the app for current users 27m

Started Nov 19, 2024, 06:56 PM UTC· resolved Nov 19, 2024, 07:23 PM UTC

  1. resolved Nov 19, 2024, 08:30 PM UTC

    During a recent release aimed at performance improvement, we observed an unexpected disruption at 10:56 AM PT. Active users with expired authentication tokens were affected and redirected to a 401 error page, temporarily limiting their ability to use our app. This issue was an unintended side effect of the new release, which inadvertently overlooked the automatic refresh of expired tokens for these users. Our team has since addressed and rectified this problem by 11:23 AM PST.

Read the full incident report →