Candid Health logo

Is Candid Health Down?

SaaSLive status, outages, and incident history

No. Candid Health is up right now.

Every monitored Candid Health system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 5m agoLive · every 60s

Know the moment Candid Health breaks

Candid Health is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Candid Health status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Candid Health Status Summary

As of 08:10 UTC on 14 November 2026, Candid Health is operational. PulsAPI checked Candid Health's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "App Latency and Intermittent API Outages", was on Oct 27, 2026 and lasted 2h 51m.

Cite as: PulsAPI, “Candid Health status”, checked 14 November 2026, 08:10 UTC. https://www.pulsapi.com/services/candid-health

Candid Health Component Status

The main Candid Health systems on this page. All 8 are operational right now.

8operational
API » Availity Eligibility API
Operational
API » Change Healthcare Eligibility API
Operational
API » Encounters & Coded Encounters APIs
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking App, Claim Submission, ERA processing pipeline, Exports, Reports.

See all of them free

Component statuses may change independently during partial outages.

Recent Candid Health Outages & Incidents

Incident history from the official Candid Health status page, including resolution updates.

App Latency and Intermittent API OutagesResolved Oct 27, 2026 · 2h 51mResolved

This incident has been resolved. --- [2026-10-27T09:40:00.211-07:00] (monitoring) We shipped a fix ~an hour ago and performance has stabilized -- we will continue to monitor. --- [2026-10-27T06:59:41.296-07:00] (investigating) We are currently experiencing app latency and intermittent outages on our APIs. The team is actively investigating the issue

Some in-app reports slow to load or failing to loadResolved Oct 5, 2026 · 7h 59mResolved

This incident has been resolved. --- [2026-10-05T15:30:34.218-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-05T14:53:58.259-07:00] (investigating) We are currently investigating this issue. Impact is limited to a subset of in-app reports and dashboards.

Delayed claim submissions and responses via WaystarResolved Oct 1, 2026 · 2h 22mResolved

Connectivity between Candid and Waystar was restored at approximately 11:30 AM ET on October 1. Claims queued during the disruption (September 30, ~5:45 PM ET to October 1, ~11:30 AM ET) have been sent to Waystar, and claim submission and responses via Waystar are operating normally. No data was lost and no action is needed. Please do not resubmit affected claims. --- [2026-10-01T08:36:55.857-07:00] (monitoring) Connectivity between Candid and Waystar was restored at approximately 11:30 AM ET. Claims that were queued during the disruption are now being sent to Waystar automatically, and delayed Waystar response files (999 acknowledgments and 277 claim status) are being received and processed. No data was lost and no action is needed on your part. Please do not resubmit affected claims. --- [2026-10-01T08:10:23.216-07:00] (investigating) Since approximately 5:45 PM ET on September 30, claims routed through the Waystar clearinghouse have not been delivered. Since approximately 5:35 PM ET, we have also not received Waystar response files (999 acknowledgments and 277 claim status). We have traced the issue to connectivity between Candid and Waystar and are working with Waystar to restore it. Claims sent through other clearinghouses are not affected. No data has been lost: affected claims are safely queued and will be sent automatically once connectivity is restored, so you do not need to resubmit.

Candid Health Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Candid Health incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Candid Health Outage Reports

Problems reported by engineers using Candid Health. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Candid Health problems reported yet.

Something wrong with Candid Health on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Candid Health

Candid Health posts its status at status.joincandidhealth.com. The page covers 8 components, among them Availity Eligibility API, Change Healthcare Eligibility API and Encounters & Coded Encounters APIs. Past incidents and uptime for Candid Health stay on this page, which helps when you want to know how often it has trouble.

Candid Health Status FAQ

Is Candid Health down right now?

The verdict at the top of this page comes from the latest poll of the official Candid Health status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Candid Health is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Candid Health recovers.

How do I check Candid Health uptime history?

PulsAPI tracks Candid Health uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Candid Health changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Candid Health outages?

PulsAPI reads the official Candid Health status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Candid Health components?

Yes. PulsAPI monitors 8 individual Candid Health components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Candid Health goes down?

Yes. Create a free account and subscribe to Candid Health: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Candid Health to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Candid Health problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Candid Health?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Candid Health plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Candid Health with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services