Findhelp Outage History

26 incidents recorded over the last 365 days, 23 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 Findhelp status100.00% uptime history

Every Recorded Findhelp Incident

Findhelp incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 2026Outage for SMART® on FHIR® Launch VendorThis incident has been resolved.1h 32mResolved
Oct 7, 2026Non-disruptive maintenanceWe will be performing scheduled maintenance on Tuesday 10/6 starting at 7:00 PM CDT and lasting for approximately one hour. No disruption to existing services is expected, but some users may experience higher latency…1h 0mScheduled
Sep 1, 2026Upstream Service Provider AvailabilityThis incident has been resolved.2h 40mResolved
Aug 31, 2026Some customers may be experiencing difficulties accessing the Referral APIThis incident has been resolved.2h 14mResolved
Aug 18, 2026Email delivery issuesThis incident has been resolved.18h 45mResolved
Aug 11, 2026Performance issues on CoalitionsThis incident has been resolved.1h 34mResolved
Jul 17, 2026Partial Outage Due to Third-Party ProviderThe outage with our third-party provider has been resolved. All affected services are now fully operational.48 minResolved
Jul 15, 2026Degraded Form ProcessingThis incident has been resolved.1h 14mResolved
Jul 3, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jun 26, 2026SMS Delivery IssuesThis incident has been resolved.15h 7mResolved
Jun 25, 2026Performance issues for coalition usersThis issue has been resolved.24h 36mResolved
Jun 1, 2026Reduced availability of Findhelp servicesSome customers will have experienced a brief interruption in functionality when accessing their custom sites or using our integrations. This has been rectified and we are continuing to monitor.-47 minResolved
May 27, 2026Performance issues for social care workflowsSocial care workflows experienced a performance degradation from 4:22am through 4:44am Central. The situation is now resolved.-60 minResolved
May 27, 2026Performance issues for social care workflowsSocial care workflows experienced a performance degradation from 4:22am through 4:44am Central. The situation is now resolved.-60 minResolved
Apr 22, 2026Statuspage reporting a non-existent incidentThis incident has been resolved.0 minResolved
Apr 21, 2026Impaired functionality for program claiming and suggestionsThis incident has been resolved.25 minResolved
Apr 15, 2026Native+ synchronization issuesThis incident has been resolved.3h 21mResolved
Mar 30, 2026Connectivity Issues Affecting findhelp.orgThis incident has been resolved.5h 50mResolved
Mar 21, 2026Forms Performance DegradationWe are observed elevated latency and degraded performance for Forms. Users may experience slow response times or timeouts. Our engineering team has investigated the issue and resolved.-566 minResolved
Mar 11, 2026Performance slowdowns for user workflowsThis incident has been resolved.24h 10mResolved
Mar 5, 2026Performance issues for social care workflowsIssue has been identified and resolved.24 minResolved
Feb 18, 2026Certain Seeker Profiles Not LoadingThis incident has been resolved.50 minResolved
Jan 17, 2026Scheduled MaintenanceThe scheduled maintenance has been completed. All operations are operating as normal.2h 0mScheduled
Jan 6, 2026Degraded Database PerformanceThis issue has been resolved.1h 20mResolved
Jan 6, 2026Reporting Outage Due to Third-Party ProviderThis issue has been resolved.2h 23mResolved
Nov 18, 2025Outage Due to Third-Party ProviderThe vendor has confirmed resolution of the outage. We have seen service health restored.4h 36mResolved

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 Findhelp 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 Findhelp 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 Findhelp 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 Findhelp outage in this window ran 1d, against a mean recovery of 5h 16m. If you depend on Findhelp 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.