- Detected by Pingoru
- Jun 16, 2026, 02:59 PM UTC
- Resolved
- Jun 16, 2026, 03:05 PM UTC
- Duration
- 6m
Timeline · 2 updates
-
identified Jun 16, 2026, 02:59 PM UTC
We are aware of an error message appearing in production this should be resolved shortly.
-
resolved Jun 16, 2026, 03:05 PM UTC
We have rolled out a fix for this error and refreshing the application should resolve the error.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 04:55 PM UTC
- Resolved
- Jun 15, 2026, 05:48 PM UTC
- Duration
- 52m
Timeline · 2 updates
-
investigating Jun 15, 2026, 04:55 PM UTC
We are seeing delays of a few minutes with sending some webhooks. Our team is investigating.
-
resolved Jun 15, 2026, 05:48 PM UTC
This has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 09:39 PM UTC
- Resolved
- Jun 05, 2026, 07:15 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 05, 2026, 09:39 PM UTC
Between June 3 and June 5, some appointments intermittently did not generate Zoom transcripts or AI Scribe notes. The issue was caused by exceeding Zoom's API rate limits, which can prevent transcription from starting at the beginning of a call. An earlier status update indicated this was resolved; the conditions that triggered the issue subsequently re-emerged on June 4 and June 5. We have since deployed a safeguard to prevent this from recurring, increased our integration capacity, and added monitoring to detect the condition proactively. We are actively monitoring to confirm stability. Where Zoom cloud recording was enabled, transcripts were preserved. For appointments where transcripts could not be recovered, impacted providers will be notified directly.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 04:50 PM UTC
- Resolved
- Jun 05, 2026, 04:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 05, 2026, 04:50 PM UTC
Some users are experienced errors when generating or regenerating session recordings and transcript notes. We have taken steps to both immediately mitigate this issue as well as prevent this going forward.
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 06:09 PM UTC
- Resolved
- May 16, 2026, 06:18 PM UTC
- Duration
- 9m
Timeline · 2 updates
-
identified May 16, 2026, 06:09 PM UTC
We have identified the issue and are working on a fix.
-
resolved May 16, 2026, 07:09 PM UTC
The incident has been resolved and background jobs are being processed normally
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 11:09 PM UTC
- Resolved
- May 14, 2026, 10:48 PM UTC
- Duration
- —
Timeline · 2 updates
-
resolved May 14, 2026, 11:09 PM UTC
This has been resolved.
-
investigating May 14, 2026, 11:09 PM UTC
A Javascript error is causing some Healthie front-ends to fail to load, which is manifesting as an infinite loading circle. This should be resolved in the next few minutes. Backend and API based actions are not affected.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 06:55 PM UTC
- Resolved
- May 14, 2026, 07:29 PM UTC
- Duration
- 34m
Affected: Healthie (Production)
Timeline · 2 updates
-
identified May 14, 2026, 06:55 PM UTC
We have identified an issue currently affecting our connection with Zus. We have isolated the issue and are deploying a fix.
-
resolved May 14, 2026, 07:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 11:24 PM UTC
- Resolved
- May 11, 2026, 11:39 PM UTC
- Duration
- 15m
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating May 11, 2026, 11:24 PM UTC
We are investigating reports of 403 errors when accessing Healthie. We'll post updates as we know more.
-
resolved May 11, 2026, 11:39 PM UTC
This issue is now resolved. If you're still seeing errors, refresh the page and you should be able to access Healthie again without error.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 09:21 PM UTC
- Resolved
- May 08, 2026, 10:48 PM UTC
- Duration
- 1h 27m
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating May 08, 2026, 09:21 PM UTC
We are currently investigating an issue causing 502 errors when loading embedded dashboards in the Visualize section of Healthie. Other areas of the platform are unaffected. Our engineering team is actively working to identify the root cause and restore service.
-
resolved May 08, 2026, 10:48 PM UTC
The root cause has been identified and resolved. All embedded reports have been restored and fully operational.
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 09:51 PM UTC
- Resolved
- Apr 29, 2026, 09:53 PM UTC
- Duration
- 2d
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating Apr 27, 2026, 09:51 PM UTC
The Provider Utilization Dashboard is disable right now due to an issue with our Business Insights tool Metabase. The Appointments report is also affected - the Provider Name, Appointment Type, and Status filters are not working correctly at the moment. We're working with the vendor on a fix and we'll update you as soon as it's resolved.
-
resolved Apr 29, 2026, 09:53 PM UTC
Fix is live. The Provider Utilization Dashboard and Appointments Report filters are back to fully functional.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 11:51 AM UTC
- Resolved
- Apr 25, 2026, 02:01 PM UTC
- Duration
- 2h 10m
Affected: Healthie (Production)
Timeline · 3 updates
-
investigating Apr 25, 2026, 11:51 AM UTC
We are currently investigating an issue causing unresponsiveness in the site.
-
monitoring Apr 25, 2026, 12:04 PM UTC
At this time the site is operational, we are monitoring to ensure that the issue is fully resolved.
-
resolved Apr 25, 2026, 02:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 07:06 PM UTC
- Resolved
- Apr 22, 2026, 08:33 PM UTC
- Duration
- 1h 27m
Affected: Healthie (Sandbox)
Timeline · 2 updates
-
investigating Apr 22, 2026, 07:06 PM UTC
We are investigating an issue causing difficulties in loading our staging environment, we will update as we have more information available.
-
resolved Apr 22, 2026, 08:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 06:53 PM UTC
- Resolved
- Apr 16, 2026, 07:23 PM UTC
- Duration
- 30m
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating Apr 16, 2026, 06:53 PM UTC
We are investigating reports of errors when booking appointments.
-
resolved Apr 16, 2026, 07:23 PM UTC
This issue has been resolved. Patients and providers can now book appointments without errors.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 02:34 PM UTC
- Resolved
- Apr 16, 2026, 05:09 PM UTC
- Duration
- 2h 34m
Affected: Healthie (Sandbox)
Timeline · 2 updates
-
identified Apr 16, 2026, 02:34 PM UTC
We have identified an issue causing delays in processing webhooks and background jobs in our staging environment. We will update as we roll out a fix.
-
resolved Apr 16, 2026, 05:09 PM UTC
We have identified and fixed the cause of the issue, operations should be back to normal.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 07:13 PM UTC
- Resolved
- Mar 30, 2026, 11:40 PM UTC
- Duration
- 4h 26m
Affected: DoseSpot
Timeline · 2 updates
-
monitoring Mar 30, 2026, 07:13 PM UTC
DoseSpot has confirmed they are experiencing a performance issue and are working on a fix. The platform may be slow to load or, in some cases, may not load at all. We will update this page once DoseSpot reports a resolution. https://status.dosespot.com/posts/details/P04ONBJ
-
resolved Mar 30, 2026, 11:40 PM UTC
This incident has been resolved. DoseSpot performance is back to normal.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 06:53 PM UTC
- Resolved
- Mar 16, 2026, 07:59 PM UTC
- Duration
- 1h 5m
Timeline · 2 updates
-
investigating Mar 16, 2026, 06:53 PM UTC
We are seeing an increase in Zoom transcription errors which appears to be due to a server incident on Zoom's side. We have reached out to them to escalate. This is specific to Zoom transcriptions and Zoom calls (and Healthie more broadly) are not otherwise affected.
-
resolved Mar 16, 2026, 07:59 PM UTC
Zoom validated this as an issue on their end which has now been resolved - https://www.zoomstatus.com/incidents/r5swflw3b537
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 02:35 PM UTC
- Resolved
- Mar 11, 2026, 03:56 PM UTC
- Duration
- 1h 20m
Affected: Healthie (Production)
Timeline · 3 updates
-
investigating Mar 11, 2026, 02:35 PM UTC
We're currently aware of an issue where 2FA SMS codes are delayed or not delivered. We are actively investigating. We'll provide an update as soon as we have more information.
-
monitoring Mar 11, 2026, 02:39 PM UTC
The issue affecting 2FA SMS code delivery has been resolved. The root cause was an upstream issue with our SMS service provider: https://status.twilio.com/incidents/frcp4hcsfvrq Performance is back to normal. We'll continue monitoring before closing this incident out.
-
resolved Mar 11, 2026, 03:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 03:29 PM UTC
- Resolved
- Mar 02, 2026, 04:09 PM UTC
- Duration
- 40m
Affected: Healthie (Production)
Timeline · 2 updates
-
monitoring Mar 02, 2026, 03:29 PM UTC
Bridge is unable to sync Healthie customer data to S3 and Snowflake destinations. The issue started at 9:30am ET and is caused by an outage at Confluent, the third-party data connector behind Bridge. Customers using Bridge will not receive data updates to their S3 or Snowflake destinations until this is resolved. No other Healthie products or services are affected. We're in touch with the Confluent team and they are actively investigating. We'll share updates as we have them.
-
resolved Mar 02, 2026, 04:09 PM UTC
Confluent has confirmed the issue is resolved. Bridge data syncs to S3 and Snowflake destinations are running again as expected. Data feeds may take until noon ET to fully catch up. We're following up with Confluent to understand the root cause and their mitigation plans going forward.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:04 PM UTC
- Resolved
- Feb 27, 2026, 05:04 PM UTC
- Duration
- —
Affected: Healthie (Sandbox)
Timeline · 1 update
-
resolved Feb 27, 2026, 05:55 PM UTC
We saw internal server errors temporarily in staging that prevented access for a brief period. The issue had been identified and addressed and there was no impact on API calls and no production impact.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 04:04 PM UTC
- Resolved
- Feb 25, 2026, 04:15 PM UTC
- Duration
- 11m
Affected: Healthie (Production)
Timeline · 3 updates
-
investigating Feb 25, 2026, 04:04 PM UTC
Healthie is currently unavailable. Some users may see blank screens or pages that fail to load. We are investigating and will post updates here.
-
monitoring Feb 25, 2026, 04:10 PM UTC
Healthie is back up and running. We are continuing to monitor.
-
resolved Feb 25, 2026, 04:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 06:17 PM UTC
- Resolved
- Feb 23, 2026, 08:43 PM UTC
- Duration
- 2h 26m
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating Feb 23, 2026, 06:17 PM UTC
We're investigating reports of delays in processing Google Calendar sync updates. As soon as we have more details, we'll post another update.
-
resolved Feb 23, 2026, 08:43 PM UTC
Google Calendar sync processing returned to normal as of 3:30 PM ET. Syncs initially started to be delayed at around 10:30 AM ET, with fixes being deployed at 1:40 PM and 2:45 PM. Queues are now fully caught up and we're marking this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 10:41 PM UTC
- Resolved
- Feb 18, 2026, 10:56 PM UTC
- Duration
- 14m
Affected: Healthie (Sandbox)
Timeline · 2 updates
-
investigating Feb 18, 2026, 10:41 PM UTC
We are seeing issues with signing in to Staging. This may also potentially be impacting API calls. There is no impact to production.
-
resolved Feb 18, 2026, 10:56 PM UTC
This has been resolved.
Read the full incident report →
Critical February 13, 2026 - Detected by Pingoru
- Feb 13, 2026, 08:09 PM UTC
- Resolved
- Feb 13, 2026, 08:42 PM UTC
- Duration
- 33m
Affected: Healthie (Production)
Timeline · 7 updates
-
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.
-
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.
-
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.
-
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.
-
investigating Feb 13, 2026, 08:09 PM UTC
Healthie is back online. We're continuing to monitor for any remaining issues.
-
investigating Feb 13, 2026, 08:10 PM UTC
Please see prior message.
-
resolved Feb 13, 2026, 08:42 PM UTC
Performance is stable across the board. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 08:21 PM UTC
- Resolved
- Feb 19, 2026, 10:22 PM UTC
- Duration
- 10d 2h
Affected: Healthie (Production)
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 05:45 PM UTC
- Resolved
- Jan 31, 2026, 06:10 PM UTC
- Duration
- 1d
Affected: Healthie (Production)
Timeline · 2 updates
-
investigating Jan 30, 2026, 05:45 PM UTC
We're investigating new reports of errors occurring when attempting to use the Zus integration. This may prevent patient and provider syncing with Zus. Our team has raised the issue with Zus and they're investigating.
-
resolved Jan 31, 2026, 06:10 PM UTC
We've seen error rates return to normal.
Read the full incident report →