TechnologyOne Outage History

TechnologyOne is up right now

TechnologyOne had 7 outages in the last 2 years totaling 58h 6m of downtime — averaging 0.3 incidents per month.

There were 7 TechnologyOne outages since October 29, 2025 totaling 58h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.t1cloud.com

Minor October 1, 2026

Service Disruption for a subset of customers in ANZ

Detected by Pingoru
Oct 01, 2026, 02:52 AM UTC
Resolved
Oct 01, 2026, 05:07 AM UTC
Duration
2h 15m
Affected: Batch Services (DP Jobs)Ci Anywhere
Timeline · 3 updates
  1. identified Oct 01, 2026, 02:52 AM UTC

    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.

  2. monitoring Oct 01, 2026, 04:14 AM UTC

    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.

  3. resolved Oct 01, 2026, 05:07 AM UTC

    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.

Read the full incident report →

Notice June 9, 2026

SFTP Service Disruption for a subset of customers / ANZ Region

Detected by Pingoru
Jun 09, 2026, 03:15 PM UTC
Resolved
Jun 09, 2026, 08:28 PM UTC
Duration
5h 13m
Affected: Ci Anywhere
Timeline · 6 updates
  1. investigating Jun 09, 2026, 03:15 PM UTC

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

  2. identified Jun 09, 2026, 04:21 PM UTC

    Our team has identified a fix which is being implemented now for ANZ Region. We anticipate the implementation of the fix to take ~120 minutes to complete and verify.

  3. identified Jun 09, 2026, 05:19 PM UTC

    Our team continue to deploy a fix which is being implemented now for ANZ Region, impacting SFTP. We anticipate the implementation of the fix to take 60 minutes to complete and verify.

  4. monitoring Jun 09, 2026, 06:21 PM UTC

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

  5. resolved Jun 09, 2026, 08:28 PM UTC

    After 2 hours 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.

  6. postmortem Jun 23, 2026, 12:27 AM UTC

    **Issue Summary** A subset of customers in the ANZ region experienced issues connecting to the SFTP service. **Root Cause** The service interruption was caused by an infrastructure deployment issue. During scheduled maintenance, an incomplete infrastructure configuration attempted to reconcile and rebuild components, resulting in the temporary unavailability of the SFTP service. **Corrective Action** To restore service, additional infrastructure capacity was provisioned in the ANZ region. A new SFTP host was deployed, the database was restored, and traffic routing was re-established to return customers to normal service. **Preventative Measures** As part of our ongoing resilience and reliability program, we have implemented additional monitoring and alerting, enhanced backup and recovery procedures, and are introducing Blue-Green deployment practices for the SFTP service to reduce the risk of future service disruptions.

Read the full incident report →

Critical February 10, 2026

Service Disruption for ANZ Customers

Detected by Pingoru
Feb 10, 2026, 09:41 PM UTC
Resolved
Feb 11, 2026, 04:35 AM UTC
Duration
6h 53m
Affected: Ci in the CloudCi AnywhereCi Anywhere
Timeline · 6 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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."

Read the full incident report →

Notice November 8, 2025

TechnologyOne Customer Community Unavailable

Detected by Pingoru
Nov 08, 2025, 09:01 PM UTC
Resolved
Nov 09, 2025, 05:14 AM UTC
Duration
8h 13m
Timeline · 3 updates
  1. investigating Nov 08, 2025, 09:01 PM UTC

    The TechnologyOne Customer Community is currently unavailable. Should you need to contact support please phone on: Australia: 1300 735 130 New Zealand (free call): 0800 174 091 Malaysia (free call): 1800 818 451 United Kingdom: +44 (1223) 607860 Fiji +61 7 3167 7714 Papua New Guinea: +61 7 3167 7714 We will provide an update when the site is available again.

  2. monitoring Nov 09, 2025, 03:09 AM UTC

    The Customer Community is available again. We will monitor for a few hours before setting this to resolved.

  3. resolved Nov 09, 2025, 05:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 29, 2025

Azure Service Degradation – Possible Impact to Login Access

Detected by Pingoru
Oct 29, 2025, 07:26 PM UTC
Resolved
Oct 30, 2025, 12:50 AM UTC
Duration
5h 24m
Timeline · 2 updates
  1. monitoring Oct 29, 2025, 07:26 PM UTC

    We are aware of a service incident currently affecting Microsoft Azure, which may cause intermittent issues with authentication (SSO) if you are using this service to authenticate into your environment. While not all customers will be impacted, you may experience slower login times or temporary connection issues. We are actively monitoring the situation and will provide updates as more information becomes available. For real-time updates from Microsoft, please refer to the official Azure Status page: https://azure.status.microsoft/en-us/status

  2. resolved Oct 30, 2025, 12:50 AM UTC

    This incident has been resolved.

Read the full incident report →