Caregility Outage History

Caregility is up right now

Caregility had 2 outages in the last 2 years — averaging 0.1 incidents per month.

There were 2 Caregility outages since July 8, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.caregility.com

Minor January 8, 2026

IMPORTANT: Platform Disruption

Detected by Pingoru
Jan 08, 2026, 08:26 PM UTC
Resolved
Jan 08, 2026, 06:50 PM UTC
Duration
Affected: Admin PortalP2P 2.0
Timeline · 2 updates
  1. investigating Jan 08, 2026, 05:20 PM UTC

    Service Update Announcement Dear Valued Customer, We are continuing to receive reports of intermittent issues related to this morning’s outage. Our team is actively investigating and will provide an update within the next 30 minutes. If you are still experiencing any issues, please contact Technical Support at 1-866-300-0884. Sincerely, The Caregility Team 1-866-300-0884 [email protected]

  2. resolved Jan 08, 2026, 08:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 8, 2025

iConsult 2.0 & iObserver Service Disruption

Detected by Pingoru
Jul 08, 2025, 07:30 PM UTC
Resolved
Jul 08, 2025, 07:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 09, 2025, 09:34 PM UTC

    On July 8th, 2025, between 3:30PM and 3:50PM ET, some users had trouble starting new iConsult 2.0 and iObserver calls. They saw a message saying, “the device cannot be started”. Ongoing sessions were not impacted. The disruption was caused by a delay in the Cloud vendor’s replication service into the read datastore, which provides the device status information. This delay caused the system to incorrectly determine the APS device as offline, preventing new calls from being placed using that APS device. he issue was resolved on its own once the replication delay in the datastore returned to normal. We have identified the root cause and implemented new safeguards to prevent this from happening again and developed plans for long term resolution.

Read the full incident report →