TechnologyOne experienced a critical incident on February 10, 2026 affecting Ci in the Cloud and Ci Anywhere and 1 more component, lasting 6h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 10, 2026, 09:41 PM UTC
We are investigating an issue impacting service for ANZ customers where environments are not available. The next update will be provided in 60 minutes, or sooner if new information becomes available.
- identified Feb 10, 2026, 09:59 PM UTC
We have engaged with our upstream provider as this disruption is the result of an AWS outage. We are continuing to work with them to restore services. The next update will be provided in 60 minutes, or sooner if new information becomes available.
- monitoring Feb 10, 2026, 10:12 PM UTC
Our upstream provider has implemented a fix and noted that recovery is underway. We have noted that environments appear to be back online and operational. Please try accessing them again if you have not already. We will continue to monitor for the next 2 hours.
- monitoring Feb 11, 2026, 12:17 AM UTC
Our upstream provider has implemented a fix and confirmed that recovery is underway. We’re seeing environments come back online and operate normally. Full recovery efforts are still in progress to ensure there is no additional impact. Please try accessing the environments again if you haven’t already. We will continue to monitor for the next 2 hours.
- monitoring Feb 11, 2026, 02:22 AM UTC
Our upstream provider has advised the complete restoration globally continues. We have not observed any further issues however we will continue to monitor until the upstream provider confirms full restoration.
- resolved Feb 11, 2026, 04:35 AM UTC
The upstream provider has confirmed complete restoration and provided these details: "We experienced elevated DNS resolution errors for CloudFront distributions served from a subset of edge locations globally. During this time, customers may have received NXDOMAIN responses. Engineers were automatically engaged, immediately began investigating in multiple parallel paths and mitigated errors by taking the affected fleet of DNS servers out of service. We are confident this issue will not reoccur."