Live  /  CareCloud  /  Incident

CareCloud: Claims Not Automatically Generating

CareCloud · carecloud.comMinor incidentResolved2026-10-14 14:20 UTC
Public — what happened

Summary

CareCloud said a scheduled overnight job failed, so claims that should have been created automatically were not generated; it did not say which customers were affected. The company began investigating on 2026-10-13 at 12:20 UTC, and by 15:47 UTC its team was manually working through the missed claims, with many already handled. At 18:05 UTC CareCloud said all affected claims should now be taken care of and that it would watch that night's scheduled jobs, and it marked the incident resolved on 2026-10-14 at 14:20. The company did not publicly state what caused the job to fail.

Affected

Claims

As listed on CareCloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach CareCloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for CareCloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the CareCloud report →

More from CareCloud

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the CareCloud status & history page.

Related: CareCloud status & history. SquidGrid is not affiliated with CareCloud.