Caregility Outage History

Caregility is up right now

Pingoru has recorded 10 incidents for Caregility: 3 in the last 12 months and 0 in the last 90 days.

Source: status.caregility.com

10incidents recorded
3last 12 months
0last 90 days
52 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Caregility in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202610 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 515 (0%)

Incidents, newest first

Major July 15, 2026 IMPORTANT: Platform Disruption –

Started Jul 15, 2026, 10:00 AM UTC· resolved Jul 15, 2026, 10:00 AM UTC

  1. resolved Aug 11, 2026, 06:16 PM UTC

    Dear Valued Customer, We are writing to inform you that our platform is currently experiencing a service disruption. Our team is actively investigating the issue and will provide updates as soon as more information becomes available. Sincerely, The Caregility Team 1-866-300-0884 [email protected] __________________________________________________________________________________________ Caregility 1350 Campus Parkway, Suite 201, Wall Township NJ 07753 732-440-7810

Read the full incident report →

Notice July 8, 2025 iConsult 2.0 & iObserver Service Disruption –

Started Jul 08, 2025, 07:30 PM UTC· resolved Jul 08, 2025, 07:30 PM UTC

  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 →

Notice March 20, 2025 iConsult 2.0 Service Disruption –

Started Mar 20, 2025, 12:30 AM UTC· resolved Mar 20, 2025, 12:30 AM UTC

  1. resolved Mar 20, 2025, 12:37 AM UTC

    We encountered a brief disruption in iConsult 2.0 services. Services were quickly restored, following the restart of a backend service. All systems are now operational and we will continue to monitor overall platform health and functionality.

Read the full incident report →

Notice February 7, 2025 APS Registration Service Disruption –

Started Feb 07, 2025, 03:30 PM UTC· resolved Feb 07, 2025, 03:30 PM UTC

  1. resolved Feb 07, 2025, 05:07 PM UTC

    One of the Caregility platform components (APS registration service) experienced a brief disruption from 9:49 AM - 9:55 AM ET. During the outage, existing calls would not have been impacted, but new calls would have failed. Services were fully restored at 9:55 AM ET.

Read the full incident report →

Notice November 25, 2024 iObserver 3.0 Service Disruption 1d 15h iObserver 3.0

Started Nov 25, 2024, 09:09 AM UTC· resolved Nov 27, 2024, 12:30 AM UTC

  1. investigating Nov 25, 2024, 09:09 AM UTC

    We are continuing to investigate this issue.

  2. investigating Nov 25, 2024, 09:11 AM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 25, 2024, 09:12 AM UTC

    We are currently investigating this issue.

  4. resolved Nov 27, 2024, 12:30 AM UTC

    RCA Pending

Read the full incident report →