TechnologyOne incident
Non-Production Service Disruption for a subset of customers / ANZ Region / 2025A and 2024B Releases
TechnologyOne experienced a major incident on July 21, 2025 affecting Ci in the Cloud and Ci Anywhere, lasting 2h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 21, 2025, 05:27 AM UTC
We are investigating an issue impacting service for a subset of customers’ non-production environments in the ANZ region, related to the 2025A release. Impact/Error/How to verify: Service Unavailable or 503 Errors on non-production environments for 2025A. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.
- monitoring Jul 21, 2025, 05:39 AM UTC
Our team has verified the implementation of a fix is complete. We will monitor the logs for the next 1 hour to ensure no further customers are impacted.
- identified Jul 21, 2025, 05:55 AM UTC
We can see some errors still present. Our team has identified the fix was only partially applied and are continuing to implement this now. We anticipate the implementation of the fix to take 30 minutes to complete and verify.
- identified Jul 21, 2025, 06:25 AM UTC
Our team has confirmed that 2025A non-production environments that were affected are now operational. We have, since the start of the incident, identified that a subset of 2024B non-production environments are experiencing the same 503 and service offline errors. We are in the process of applying the mitigation to these impacted environments on 2024B and expect this to be completed in the next 30 minutes.
- monitoring Jul 21, 2025, 06:53 AM UTC
Our team has verified the implementation of a fix is now complete for 2024B affected environments. We will monitor the logs for the next 1 hour to ensure no further customers are impacted.
- resolved Jul 21, 2025, 07:57 AM UTC
After 1 hour monitoring this incident is now resolved. We apologise for how you and your business may have been affected by this incident.
- postmortem Aug 07, 2025, 05:20 AM UTC
Issue Summary: On July 21 at 03:18 PM, customers reported service unavailability and 503 errors on the non-production environments. Root Cause: The incident was caused by failure in upstream service. Corrective actions: Affected customers were migrated to alternative infrastructure to restore the service and the upstream provider fixed the impaired service. Preventative Measures: We are enhancing the platform architecture to strengthen resilience and ensure more reliable integration with upstream services, reducing the risk of disruption from system-level processes.