Is TechnologyOne down?

Our team has identified an issue affecting DP background jobs and slow performance for a subset of customers in ANZ Region. A fix is currently underway We anticipate the implementation of the fix to take 20 minutes to complete and verify. Users should see improvement within the next hour. We will provide a further update in 90 minutes or less.

Our team has verified the implementation of a fix is complete for the ANZ region and subset of customers. We will monitor the logs for the next 2 hours to ensure no further customers are impacted.

After 1 hour monitoring, we have confirmed this incident is now resolved and services impacted are back to normal for the subset of impacted customers. We apologise for how you and your business may have been affected by this incident.

**Issue Summary:** At 12:55 PM on 01 October 2026, some customers reported experiencing significant delays in data processing \(DP\) jobs. This resulted in degraded system performance and a large backlog of submitted actions remaining in a 'pending' or 'submitted' state for several hours. **Root Cause Analysis:** The issue was caused by an overload of underlying platform components due to a sudden, very high volume of simultaneous requests, which temporarily exceeded available processing capacity. **Corrective Action:** Technology1 observed the delays occurring and the system automatically scaled up the background job processor's capacity to handle the increased load. While the auto-scaling mechanisms successfully provisioned the necessary resources, the sheer volume of the accumulated backlog required significant time to clear. The system continuously processed the jobs at this expanded capacity until all pending actions were resolved and the queue returned to normal levels. **Preventative Measures** * Optimize auto-scaling thresholds and improve monitoring to react even faster to unexpected spikes in demand. * Implement additional flow controls to manage high processing volumes and ensure system settings remain within safe operating limits.

We are investigating an issue impacting service for a subset of ANZ customers. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

A subset of customers across multiple releases in the ANZ region are experiencing Null Token errors and degraded access to CI and CI Anywhere. Our team is currently investigating and troubleshooting the issue. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We are continuing to investigate the issue affecting a subset of customers across multiple releases in the ANZ region. Impacted users may continue to intermittently experience Null Token errors when accessing CI. Access to CiA has improved. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We are continuing to investigate the issue related to Null Token errors that a subset of users may be intermittently experiencing when accessing CI across multiple releases in the ANZ region. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We are still continuing to investigate the issue related to Null Token errors that a subset of users may be intermittently experiencing when accessing CI across multiple releases in the ANZ region. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We are continuing to investigate the issue related to Null Token errors that a subset of users may be intermittently experiencing when accessing CI and Time tabling & Scheduling across multiple releases in the ANZ and UK region. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We are working with the upstream provider to investigate the issue related to Null Token errors that a subset of users may be intermittently experiencing when accessing CI and Time tabling & Scheduling across multiple releases in the ANZ and UK region. Due to the investigation, the next update will be provided in 60 minutes, or sooner if new information becomes available.

We have seen error rates reduce significantly and are continuing to monitor the platform closely. Current indicators show improved service stability, and our teams remain engaged to ensure performance continues to trend in the right direction. We will maintain enhanced monitoring through tomorrow and provide our next update by 9:00 AM AEST, or earlier if required.

We continue to observe very low error rates and stable performance. Monitoring remains in place, and our teams are continuing to closely observe the environment to ensure service stability is maintained. We will provide our next update by 2:00 PM AEST, or earlier if required.

Following an extended period of stable performance and continued monitoring, this incident has now been resolved. Error rates have remained at expected levels, and no further customer impact has been observed. Our teams will continue to review the incident and implement any identified improvements as part of our standard post-incident process. We appreciate your patience and understanding while we worked to restore and validate service stability.

### Incident Summary Between **31 August 2026 and 2 September 2026**, some customers experienced intermittent service disruptions, including slow application responsiveness, connection timeouts, and periods of Ci unavailability. The issue was caused by internal DNS resolution failures within an underlying CiA cluster, which affected communication between application services and backend caching components. Service stability has been restored and all affected environments are operating normally. ### Root Cause A significant increase in internal DNS requests related to Redis caching placed unexpected demand on the cluster's DNS service \(CoreDNS\). This resulted in memory exhaustion within CoreDNS, preventing it from scaling effectively to meet demand. As a result, some application services experienced delayed or failed DNS lookups, leading to connection timeouts and degraded application performance. ### Corrective Actions Taken To restore service and stabilise the platform, we: * Increased CoreDNS capacity by scaling the service. * Rebalanced workloads by moving affected environments to alternative CiA clusters. * Restarted impacted DNS services and closely monitored DNS performance until normal operation was confirmed. ### Preventative Actions * Optimising Redis connection management and DNS resolution behaviour to reduce DNS query volumes. * Reviewing and refining CoreDNS autoscaling policies, resource limits, and capacity thresholds. * Assessing long-term cluster capacity and workload distribution strategies. * Enhancing monitoring and alerting to identify and respond to DNS-related issues before customer impact occurs.

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

Our team has verified the implementation of a fix is complete for ANZ Region. We will monitor the logs for the next 2 hours to ensure no further customers are impacted.

We are continuing to monitor for any further issues.

We are continuing to monitor for another 2 hours to ensure no further customers are impacted.

After considerable monitoring, this incident is now resolved. We will undertake a Post Incident Review and findings will be posted here on completion. We apologise for how you and your business may have been affected by this incident. Please contact the TechnologyOne Support team if you continue to experience issues.

### Incident Summary Between **31 August 2026 and 2 September 2026**, some customers experienced intermittent service disruptions, including slow application responsiveness, connection timeouts, and periods of Ci unavailability. The issue was caused by internal DNS resolution failures within an underlying CiA cluster, which affected communication between application services and backend caching components. Service stability has been restored and all affected environments are operating normally. ### Root Cause A significant increase in internal DNS requests related to Redis caching placed unexpected demand on the cluster's DNS service \(CoreDNS\). This resulted in memory exhaustion within CoreDNS, preventing it from scaling effectively to meet demand. As a result, some application services experienced delayed or failed DNS lookups, leading to connection timeouts and degraded application performance. ### Corrective Actions Taken To restore service and stabilise the platform, we: * Increased CoreDNS capacity by scaling the service. * Rebalanced workloads by moving affected environments to alternative CiA clusters. * Restarted impacted DNS services and closely monitored DNS performance until normal operation was confirmed. ### Preventative Actions * Optimising Redis connection management and DNS resolution behaviour to reduce DNS query volumes. * Reviewing and refining CoreDNS autoscaling policies, resource limits, and capacity thresholds. * Assessing long-term cluster capacity and workload distribution strategies. * Enhancing monitoring and alerting to identify and respond to DNS-related issues before customer impact occurs.