Caresquare Outage History

Caresquare is up right now

Caresquare had 3 outages in the last 2 years totaling 2h 27m of downtime, averaging 0.1 incidents per month.

There were 3 Caresquare outages since May 19, 2026 totaling 2h 27m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.caresquare.au

Minor August 10, 2026

NDIA Connection Disruption

Detected by Pingoru
Aug 10, 2026, 03:21 AM UTC
Resolved
Aug 10, 2026, 03:21 AM UTC
Duration
–
Affected: Current status by service (NDIS API)
Timeline · 1 update
  1. resolved Aug 10, 2026, 03:21 AM UTC

    Claim submissions as well as budget updates are experiencing intermittent disruptions.

Read the full incident report →

Major May 26, 2026

Possible NDIA API outage

Detected by Pingoru
May 26, 2026, 03:34 AM UTC
Resolved
May 26, 2026, 03:48 AM UTC
Duration
14m
Affected: Current status by service (NDIS API)
Timeline · 2 updates
  1. investigating May 26, 2026, 03:34 AM UTC

    Initial reports have been received of issues using functionality relating to the NDIA API. We are investigating to confirm the incident and will provide an update by 2pm AEST

  2. resolved May 26, 2026, 03:48 AM UTC

    We have re-enabled NDIA API functionality as the incidents reported have been confirmed to be isolated.

Read the full incident report →

Major May 19, 2026

Service disruption

Detected by Pingoru
May 19, 2026, 11:28 PM UTC
Resolved
May 20, 2026, 01:41 AM UTC
Duration
2h 13m
Affected: Current status by service (Web Application)
Timeline · 2 updates
  1. investigating May 19, 2026, 11:28 PM UTC

    One of our upstream cloud server providers is experiencing an outage that is affecting some functionality in the Caresquare application. They have advised the issue has been identified and they are rolling out a fix. We are monitoring and will advise once normal service is restored.

  2. resolved May 20, 2026, 01:41 AM UTC

    Service has been fully restored. We are in the process of rerunning all failed document processing executions. ETA for completion is 15 minutes. We will provide further information about the cause of the incident, and future mitigations we plan to implement ASAP.

Read the full incident report →