TechnologyOne incident

Intermittent Service Disruption for a subset of customers / ANZ Region / All Releases

Major Resolved View vendor source →

TechnologyOne experienced a major incident on September 30, 2025 affecting Ci in the Cloud and Ci Anywhere, lasting 2h 28m. The incident has been resolved; the full update timeline is below.

Started
Sep 30, 2025, 06:36 AM UTC
Resolved
Sep 30, 2025, 09:05 AM UTC
Duration
2h 28m
Detected by Pingoru
Sep 30, 2025, 06:36 AM UTC

Affected components

Ci in the CloudCi Anywhere

Update timeline

  1. investigating Sep 30, 2025, 06:36 AM UTC

    We are investigating an issue impacting service for ANZ Region / All Releases. A subset of customers in ANZ Region for All Releases are experiencing intermittent login issue Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

  2. identified Sep 30, 2025, 07:10 AM UTC

    Our team has identified a fix which is being implemented now for ANZ Region / All Releases. This impacted non-production environments predominantly, with various errors observed such as 503 and service unavailable messages.

  3. monitoring Sep 30, 2025, 07:59 AM UTC

    Our team has verified the implementation of a fix is complete for ANZ Region / All Releases. We will monitor the logs for the next 1 hour to ensure no further customers are impacted.

  4. resolved Sep 30, 2025, 09:05 AM UTC

    After an hour monitoring this incident is now resolved. We will perform a post incident review to identify underlying cause, and preventive action to avoid a repeat in the future and post here on completion. We apologise for how you and your business may have been affected by this incident.

  5. postmortem Oct 13, 2025, 05:58 AM UTC

    Issue Summary: On Tuesday, September 30, 2025, a subset of customers in the ANZ Region experienced sub-optimal performance and connection errors in Ci Anywhere / Ci. Root Cause: The degradation was caused by an upstream server going offline due to high resource usage. Corrective Action: Affected customers were migrated to alternative infrastructure to restore the service and the upstream provider fixed the impaired server Preventive Measure: As part of our ongoing resilience program, there is a focus to optimise resource efficiency.