TechnologyOne incident

Service Disruption for a subset of customers in ANZ Region for 2024 Release

Major Resolved View vendor source →

TechnologyOne experienced a major incident on July 15, 2025 affecting Ci in the Cloud and Ci Anywhere, lasting 1h 57m. The incident has been resolved; the full update timeline is below.

Started
Jul 15, 2025, 01:09 AM UTC
Resolved
Jul 15, 2025, 03:06 AM UTC
Duration
1h 57m
Detected by Pingoru
Jul 15, 2025, 01:09 AM UTC

Affected components

Ci in the CloudCi Anywhere

Update timeline

  1. investigating Jul 15, 2025, 01:09 AM UTC

    We are investigating an issue impacting service for ANZ Region / 2024B Release. Impact/Error/How to verify: A subset of customers in ANZ Region for 2024B Releases are experiencing sub-optimal performance / connection errors in Ci Anywhere / Ci. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

  2. monitoring Jul 15, 2025, 01:52 AM UTC

    Our team has verified that errors have reduced, and navigation has improved across impacted areas such as Student Management, Timesheets, App Builder, Expense Management, Cash Receipting, Performance Planning and P&R for ANZ Region / 2024B Release. We will monitor the logs for the next 1 hour to ensure no further customers are impacted.

  3. resolved Jul 15, 2025, 03:06 AM UTC

    After 1 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.

  4. postmortem Jul 29, 2025, 05:46 AM UTC

    Issue Summary: On July 15 at 10:48 AM, customers reported slow response time and 504 gateway timeouts within Student Management, Timesheets, App Builder, Expense Management, Cash Receipting, Performance Planning and P&R in CiA. Root Cause: The issue was caused by a significant increase in system requests, combined with a database conflict that temporarily blocked key processes. Corrective actions: High-traffic requests were isolated to a separate processing path, and the affected servers were recycled to restore normal service. Preventative Measures: Software changes are being implemented to better manage peak in request volumes.