ThinkOn Outage History

Started Oct 28, 2026, 02:00 PM UTC· resolved Oct 28, 2026, 05:21 PM UTC

1. investigating Oct 28, 2026, 02:00 PM UTC

   We are currently investigating a service degradation affecting the NUBAV vCloud environment. Customers can continue to access vCloud; however, certain management functions, including virtual machine modifications, may be unavailable. Our Engineering team is actively working to restore full functionality. We will provide further updates as information becomes available.

2. resolved Oct 28, 2026, 05:21 PM UTC

   This incident has been resolved. vCloud has been restored to full functionality. The team is monitoring the environment closely.

Read the full incident report →

Started Oct 27, 2026, 06:06 PM UTC· resolved Oct 30, 2026, 01:15 PM UTC

1. investigating Oct 27, 2026, 06:06 PM UTC

   We are currently experiencing a service disruption affecting Veeam Cloud Connect (VCC) in the GUBOV environment. Customers may experience connectivity issues impacting backup copy, replication, and restore operations that rely on VCC. Our Engineering team is actively investigating the issue and working to restore service as quickly as possible. We will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

2. investigating Oct 27, 2026, 11:28 PM UTC

   Investigations are ongoing, Veeam has been engaged and our engineers are working with them to resolve the issue.

3. monitoring Oct 28, 2026, 12:00 AM UTC

   We will continue monitoring the environment and reviewing backup job results. Veeam Support will keep the support case on hold for 24 hours while we monitor the environment and determine whether additional troubleshooting is required.

4. resolved Oct 30, 2026, 01:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 26, 2026, 05:01 PM UTC· resolved Oct 27, 2026, 12:00 PM UTC

1. investigating Oct 26, 2026, 05:01 PM UTC

   We are currently investigating multiple issues affecting the CMB1 Data Centre, including intermittent I/O performance degradation and Virtual Cloud Director networking functionality. Customers may experience degraded workload performance or difficulties creating, starting, or modifying virtual machines and networks. Our Engineering team is actively investigating these issues and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

2. monitoring Oct 26, 2026, 11:51 PM UTC

   CMB1 VDC Environment – Service Update The underlying issue affecting the CMB1 VDC environment has been identified, and our Engineering teams are implementing a resolution. At this time, we do not anticipate further service impacts while remediation is underway. Our teams continue to closely monitor the environment to ensure service stability. We will provide additional updates as remediation progresses and confirm once the issue has been fully resolved. Thank you for your continued patience and understanding.

3. monitoring Oct 27, 2026, 12:05 AM UTC

   CMB1 VDC Environment – Emergency Maintenance Update Our Engineering teams are actively performing emergency maintenance to address an underlying infrastructure issue affecting the CMB1 environment. While no service interruptions are currently anticipated, customers may experience brief or intermittent impacts during the maintenance activity. Our teams are taking precautions to minimize potential disruptions and are closely monitoring the environment to ensure service stability. We will provide further updates as maintenance progresses and confirm once the work has been completed. Thank you for your continued patience and understanding.

4. resolved Oct 27, 2026, 12:00 PM UTC

   CMB1 VDC Environment – Service Restored The emergency maintenance within the CMB1 environment has been successfully completed, and all affected services have been restored to normal operation. Our Engineering teams have completed validation activities and confirmed that services are operating as expected. No further customer impact is anticipated. We will continue monitoring the environment to ensure ongoing stability and performance. Thank you for your patience and understanding throughout this incident.

Read the full incident report →

Started Oct 22, 2026, 03:55 AM UTC· resolved Oct 24, 2026, 05:16 PM UTC

1. investigating Oct 22, 2026, 03:55 AM UTC

   Our Operations and Security teams have reviewed the advisory and assessed the potentially affected environments. and have performed remediation. At this time, no service disruption has been confirmed in connection with these vulnerabilities. Any required security updates will be coordinated through our established change management processes. We will provide further updates as our assessment progresses or if any customer impact is identified. No components were marked as affected by this incident.

2. monitoring Oct 22, 2026, 03:56 AM UTC

   ThinkOn continues to monitor the recently disclosed critical security vulnerabilities affecting certain versions of PHP. Our Operations and Security teams have reviewed the advisory and communicated recommended security measures to customers for potentially affected environments. At this time, no service disruption or customer impact has been confirmed in connection with these vulnerabilities. ThinkOn will continue to monitor the situation and provide additional communication if any significant developments or customer impacts are identified.

3. monitoring Oct 22, 2026, 12:03 PM UTC

   ThinkOn continues to closely monitor the recently disclosed critical security vulnerabilities affecting certain versions of PHP. Our Operations and Security teams remain vigilant and continue to exercise caution while monitoring for any potential risks to customer environments. At this time, no service disruption or customer impact has been identified or confirmed in connection with these vulnerabilities. While there is currently no indication of an impact to ThinkOn services, we continue to encourage customers to review their environments and ensure any potentially affected systems are appropriately secured and remediated. ThinkOn will continue to monitor the situation and provide further updates should any significant developments or potential customer impacts be identified.

4. monitoring Oct 22, 2026, 06:34 PM UTC

   ThinkOn continues to closely monitor the recently disclosed critical PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Our Operations and Security teams remain vigilant, and at this time, no service disruption or customer impact has been identified or confirmed in connection with these vulnerabilities. As part of our ongoing communications, we would like to highlight that Netgate has released updated PHP packages and remediation guidance for supported pfSense firewall versions. Customers utilizing pfSense firewalls are strongly encouraged to review the advisory, assess their configurations, and apply applicable security updates. Particular attention should be given to systems with administrative interfaces or Captive Portal services accessible from untrusted networks. Netgate Security Advisory: https://www.netgate.com/blog/critical-php-security-update We continue to encourage all customers to review their environments, address potentially vulnerable PHP-based applications and services, and maintain appropriate security precautions. ThinkOn will continue monitoring the situation and provide further updates should any significant developments or potential customer impacts be identified.

5. monitoring Oct 23, 2026, 10:37 PM UTC

   ThinkOn continues to monitor the recently disclosed critical PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Following our assessment, ThinkOn has implemented appropriate security measures, including applying available security updates and restricting administrative access where applicable. At this time, no service disruption or customer impact has been identified or confirmed in connection with these vulnerabilities. Customers utilizing pfSense firewalls or other potentially vulnerable PHP-based applications and services within their own managed environments are strongly encouraged to review their configurations and apply the appropriate security updates. For additional information regarding pfSense remediation, please refer to Netgate's security advisory: https://www.netgate.com/blog/critical-php-security-update ThinkOn will continue monitoring for further developments and will provide additional updates should any new security concerns or potential customer impacts be identified.

6. resolved Oct 24, 2026, 05:16 PM UTC

   ThinkOn has completed its assessment of the recently disclosed critical PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Appropriate security updates and mitigation measures have been implemented across ThinkOn-managed infrastructure where applicable. No service disruptions or customer impacts have been identified in connection with these vulnerabilities. Customers managing their own pfSense firewalls or PHP-based applications are encouraged to ensure the necessary security updates are applied. For pfSense remediation guidance, please refer to Netgate's advisory: https://www.netgate.com/blog/critical-php-security-update ThinkOn will continue monitoring through its regular security operations. This incident is now considered resolved.

Read the full incident report →

Started Oct 15, 2026, 06:41 PM UTC· resolved Oct 16, 2026, 11:00 AM UTC

1. investigating Oct 15, 2026, 06:41 PM UTC

   Our ThinkOn engineers are currently investigating the issue.

2. identified Oct 15, 2026, 08:26 PM UTC

   Our engineering teams have identified an issue affecting the underlying storage infrastructure, impacting service availability for workloads in the affected environment. We are working with our storage provider under a priority escalation to restore services as quickly as possible. Network and compute infrastructure checks have been completed, and recovery efforts remain focused on storage. Impact: Service availability may be affected for workloads in the impacted environment. Next Update: As significant progress or recovery milestones are reached. Customer Action: No action required at this time.

3. identified Oct 16, 2026, 12:10 AM UTC

   We have identified an issue in one of our storage arrays and are working with our vendor to fix it. There is currently no ETA for completion. Updates will be provided on any significant progress.

4. monitoring Oct 16, 2026, 03:40 AM UTC

   The impacted storage array and the associated infra has been restored to stability. Our team is performing health checks and monitoring. Customers can reach out to our service desk team for any issues being observed

5. monitoring Oct 16, 2026, 10:54 AM UTC

   The affected storage environment remains accessible and stable. Our engineering team continues to monitor the environment and perform health checks to ensure ongoing stability. Customers experiencing any issues are encouraged to contact our Service Desk at [email protected] or 1-877-787-0306. We will provide further updates as necessary.

6. monitoring Oct 16, 2026, 10:58 AM UTC

   The affected storage environment remains accessible and stable. Our engineering team continues to monitor the environment and perform health checks to ensure ongoing stability. Customers experiencing any issues are encouraged to contact our Service Desk at [email protected] or 1-877-787-0306. We will provide further updates as necessary.

7. resolved Oct 16, 2026, 11:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2026, 06:25 PM UTC· resolved Oct 07, 2026, 02:00 PM UTC

1. investigating Oct 06, 2026, 06:25 PM UTC

   We are currently investigating a potential issue affecting our storage (Hot) infrastructure in coordination with our hardware provider. Storage ingest may be impacted or experience delays while we investigate and work to resolve the issue. We will provide further updates as more information becomes available.

2. resolved Oct 07, 2026, 02:00 PM UTC

   The issue affecting Storage Services (Hot) at CMB1 has been resolved. Storage ingest has returned to normal operation. Thank you for your patience while we investigated and resolved the issue.

Read the full incident report →

Started Sep 02, 2026, 02:40 PM UTC· resolved Sep 02, 2026, 02:49 PM UTC

1. identified Sep 02, 2026, 02:40 PM UTC

   KMS server crash, causing VM creation/manipulation operations to error out. ThinkOn engineers are working to resolve the issue

2. resolved Sep 02, 2026, 02:49 PM UTC

   Increased KMS server disk size and restart. This incident is now resolved.

Read the full incident report →

Started Sep 02, 2026, 12:14 AM UTC· resolved Sep 02, 2026, 09:05 AM UTC

1. identified Sep 02, 2026, 12:14 AM UTC

   Please be advised that we are experiencing the following service interruption: MEL3 - VBO jobs are failing. Our team has identified the issue and is working on resolving the issue, in conjunction with escalated Veeam technical support.

2. identified Sep 02, 2026, 02:14 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Sep 02, 2026, 09:05 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 29, 2026, 08:00 PM UTC· resolved Jul 29, 2026, 10:11 PM UTC

1. identified Jul 29, 2026, 08:00 PM UTC

   Our vendor had experienced a connectivity issue within the Data Centre and are working to resolve the issue.

2. monitoring Jul 29, 2026, 09:18 PM UTC

   The connection has returned, ThinkOn is monitoring the connection to ensure stability.

3. resolved Jul 29, 2026, 10:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 10, 2026, 04:13 PM UTC· resolved Jul 24, 2026, 01:43 PM UTC

1. investigating Jul 10, 2026, 04:13 PM UTC

   We are investigating an issue causing intermittent service interruptions. Customers may experience periods where the service is unavailable before connectivity is restored. Our teams are actively investigating and working to stabilize the service.

2. resolved Jul 24, 2026, 01:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 07:44 PM UTC· resolved Jun 29, 2026, 08:29 PM UTC

1. identified Jun 29, 2026, 07:44 PM UTC

   Dear valued customer: Please note our Ottawa data center is currently running on generator power due to a HydroOttawa power outage. There is no impact to customers services. We will provide an update once utility power is restored.

2. resolved Jun 29, 2026, 08:29 PM UTC

   HydroOttawa power has been restored to the data center Generator has also stopped running. Site has successfully been transferred back to utility power.

Read the full incident report →

Started Jun 14, 2026, 06:30 AM UTC· resolved Jun 14, 2026, 08:44 AM UTC

1. investigating Jun 14, 2026, 08:10 AM UTC

   CGY4 is currently experiencing network connectivity issues.

Read the full incident report →

Started Jun 14, 2026, 05:00 AM UTC· resolved Jun 14, 2026, 07:30 AM UTC

1. investigating Jun 14, 2026, 05:00 AM UTC

   vCloud Access is Unavailable

2. resolved Jun 14, 2026, 07:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 03:57 PM UTC· resolved Jun 13, 2026, 12:10 AM UTC

1. investigating Jun 12, 2026, 03:57 PM UTC

   We are currently investigating this issue.

2. investigating Jun 13, 2026, 12:08 AM UTC

   We are continuing to investigate this issue.

3. resolved Jun 13, 2026, 12:10 AM UTC

   This issue has been resolved. We are observing successful job completions.

Read the full incident report →

Started May 30, 2026, 03:31 AM UTC· resolved May 31, 2026, 12:05 PM UTC

1. investigating May 30, 2026, 03:31 AM UTC

   We are currently investigating the issue. ThinkOn engineers are working with the vendor (veeam support) to resolve the issue.

2. investigating May 30, 2026, 03:34 AM UTC

   We are continuing to investigate this issue.

3. investigating May 31, 2026, 12:14 AM UTC

   We are continuing to investigate the issue. ThinkOn engineers are working with the vendor (Veeam support) to resolve the issue.

4. resolved May 31, 2026, 12:05 PM UTC

   Our engineering team has successfully resolved the issue. If you notice failures after today please reach out to the ThinkOn Service Desk.

Read the full incident report →

Started May 25, 2026, 08:39 PM UTC· resolved May 27, 2026, 08:12 PM UTC

1. investigating May 25, 2026, 08:39 PM UTC

   We are currently experiencing a service disruption affecting our Veeam M365 service hosted in the CGY4 data centre. Our engineering team is actively investigating the issue and working to restore services as quickly as possible. At this time, you may experience interruptions or delays when accessing or using the service. We understand the importance of this service to your operations and appreciate your patience while we work toward resolution. Thank you for your understanding."

2. investigating May 26, 2026, 04:11 AM UTC

   We are continuing to investigate a service disruption affecting our Veeam M365 service in the CGY4 data center. Service interruptions or delays may persist. We appreciate your continued patience as we work toward resolution.

3. investigating May 26, 2026, 04:10 PM UTC

   We are continuing to investigate a service disruption affecting our Veeam M365 service in the CGY4 data center. Service interruptions or delays may persist. We appreciate your continued patience as we work toward resolution.

4. identified May 26, 2026, 05:58 PM UTC

   We have isolated the issue and are currently working toward a solution. We’ll provide further updates as soon as we have more information.

5. identified May 27, 2026, 12:27 PM UTC

   We are continuing to work towards a resolution.

6. resolved May 27, 2026, 08:12 PM UTC

   Our team has confirmed the issue has been resolved and systems are now operational.

Read the full incident report →

Started Apr 26, 2026, 01:15 AM UTC· resolved Apr 26, 2026, 03:25 AM UTC

1. investigating Apr 26, 2026, 01:15 AM UTC

   We are currently investigating an issue affecting vCloud accessibility. At this time, we do not believe any workloads are impacted. Our team is working diligently to restore access as quickly as possible.

2. resolved Apr 26, 2026, 03:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 20, 2026, 02:18 PM UTC· resolved Apr 20, 2026, 02:53 PM UTC

1. investigating Apr 20, 2026, 02:18 PM UTC

   We are currently experiencing connectivity issues at our Ottawa Data Center. As a result, some customers may be experiencing service disruptions at this time. Our technical teams are actively investigating and working to restore full service as quickly as possible. We will continue to provide updates as more information becomes available. We appreciate your patience and understanding.

2. resolved Apr 20, 2026, 02:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 15, 2026, 10:42 PM UTC· resolved Apr 17, 2026, 09:37 PM UTC

1. investigating Apr 15, 2026, 10:42 PM UTC

   Dear Customers, We are currently experiencing a widespread outage at the GUBOV data centre, which is also impacting our Service Desk operations. As a result, response times for both new and existing tickets may be delayed while our teams work to manage and resolve the situation. Next Update We are actively investigating the issue and will provide further updates as more information becomes available. We appreciate your patience and understanding.

2. investigating Apr 15, 2026, 11:24 PM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our technicians are currently on-site and actively investigating the underlying physical hardware. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

3. investigating Apr 15, 2026, 11:44 PM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our on-site technicians are actively assessing the physical hardware, while our networking engineers are working in tandem to troubleshoot any potential hardware or network-related issues. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

4. investigating Apr 16, 2026, 12:12 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. At this time, we believe the root cause has been identified and are currently working to confirm our findings. Our on-site technicians and networking engineers remain actively engaged in validating the issue and determining the appropriate remediation steps. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

5. identified Apr 16, 2026, 12:23 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. We have identified the underlying issue and are currently working to validate and implement corrective actions. Our teams are actively engaged in restoring services as quickly as possible. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

6. identified Apr 16, 2026, 12:56 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our teams have identified the issue and are currently performing corrective actions, including controlled reboots of affected equipment, to restore services. Our technicians and engineers remain actively engaged in resolving the issue as quickly as possible. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

7. identified Apr 16, 2026, 01:22 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. The corrective actions performed thus far have not yet resolved the issue, and our teams are continuing to investigate and implement additional remediation steps. Our technicians and engineers remain fully engaged and are working to restore services as quickly as possible. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

8. identified Apr 16, 2026, 01:56 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our teams are actively performing both physical (on-site) and logical inspections to further isolate the issue and determine the appropriate remediation steps. At this time, there are no significant changes to report; however, our technicians and engineers remain fully engaged and are continuing their investigation. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

9. identified Apr 16, 2026, 02:35 AM UTC

   Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our teams are actively performing both physical (on-site) and logical inspections, reviewing each device to further isolate the issue and determine the appropriate remediation steps. At this time, there are no significant changes to report; however, our technicians and engineers remain fully engaged and continue their detailed investigation. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

10. identified Apr 16, 2026, 03:09 AM UTC

    Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. Our teams are actively performing detailed manual checks and verifying configurations across both primary and secondary network paths to further isolate the issue. At this time, there are no significant changes to report; however, our technicians and engineers remain fully engaged and continue their investigation. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

11. identified Apr 16, 2026, 03:56 AM UTC

    Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. At this time, replacement hardware is being brought on-site. Our teams will be working to install, configure, and perform validation checks as part of the recovery effort. This process will take some time to complete, and our technicians and engineers remain fully engaged in restoring services as quickly and safely as possible. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

12. identified Apr 16, 2026, 04:48 AM UTC

    Dear Customers, We continue to investigate the widespread outage at the GUBOV data centre. At this time, we are proceeding with the next remediation step, which involves replacing the affected hardware. A technician is expected to be on-site with replacement equipment within the next 20 minutes. Once on-site, our team will begin racking, cabling, installing, and configuring the devices, followed by validation checks. This process will take some time to complete. We understand the significant impact this incident is having on your production environments and your customers, and we want to assure you that our teams are working with urgency to restore services as quickly as possible. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

13. identified Apr 16, 2026, 05:27 AM UTC

    Dear Customers, We continue to work on restoring services at the GUBOV data centre. As part of the recovery effort, our teams are proceeding with the installation and configuration of replacement network equipment. The following activities are currently underway: Installation and racking of replacement switches Firmware updates on the new devices Application of site-specific configurations Migration of existing cabling from the affected devices to the new equipment Testing of connections and dependent systems Ongoing monitoring and validation to ensure services are fully restored This process will take some time to complete, and our technicians and engineers remain fully engaged to ensure a safe and stable recovery. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

14. identified Apr 16, 2026, 06:35 AM UTC

    Dear Customers, We are currently in the final stages of configuring the replacement equipment at the GUBOV data centre. If no issues are encountered, we expect to restore site connectivity shortly and begin verification testing. Our teams remain actively engaged to ensure a stable restoration of services. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

15. identified Apr 16, 2026, 10:14 AM UTC

    Dear Customers, We are currently validating the recent changes and completing the reconnection of all systems at the GUBOV data centre to confirm full restoration of connectivity. Our teams are actively monitoring the environment to ensure services are stable as they come back online. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

16. identified Apr 16, 2026, 10:41 AM UTC

    Dear Customers, As we continue to stabilize the environment at the GUBOV data centre, you may experience brief, intermittent periods of connectivity while we complete the restoration of site services. Our teams are actively monitoring and working to ensure a full and stable recovery. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

17. identified Apr 16, 2026, 10:59 AM UTC

    Dear Customers, We are currently completing core system validation as site connectivity is being restored at the GUBOV data centre. Our teams are working to confirm that all services are functioning as expected. Service Desk operations may still experience delays, and response times for new and existing tickets may be impacted during this time. Next Update We will provide further updates as more information becomes available. We appreciate your continued patience and understanding.

18. monitoring Apr 16, 2026, 11:30 AM UTC

    Dear Customers, Site connectivity has been restored, and we are continuing to validate all services at the GUBOV data centre. At this time, we ask that you please attempt to connect to your environments and confirm that your services are functioning as expected. If you encounter any issues, please contact ThinkOn Support so our teams can assist promptly. Service Desk operations may still experience minor delays as we complete final validations. Next Update We will provide further updates as needed. We appreciate your continued patience and support.

19. monitoring Apr 16, 2026, 11:45 AM UTC

    We are continuing to monitor for any further issues.

20. monitoring Apr 16, 2026, 11:52 AM UTC

    Dear Customers, Services have been restored, and we are currently monitoring the environment to ensure ongoing network stability at the GUBOV data centre. We kindly ask that customers continue their validation efforts and confirm that services are operating as expected. If you encounter any issues, please contact ThinkOn Support so our teams can assist promptly. Service Desk operations may still experience minor delays as we complete final monitoring and validation. Next Update We will provide further updates as needed. We appreciate your continued patience and support.

21. monitoring Apr 16, 2026, 12:54 PM UTC

    Dear Customers, We are continuing to monitor the environment at the GUBOV data centre to ensure ongoing stability and to identify any residual issues. We kindly ask that customers continue to verify their services and confirm that everything is operating as expected. If you encounter any issues, please contact ThinkOn Support so our teams can assist promptly. Service Desk operations may still experience minor delays as we complete final monitoring and validation. Next Update We will provide further updates as needed. We appreciate your continued patience and support.

22. monitoring Apr 16, 2026, 10:46 PM UTC

    Dear Customers, We continue to actively monitor the environment at the GUBOV data centre to ensure ongoing stability and confirm that all services remain fully operational. At this time, there are no new issues identified; however, our teams remain engaged and vigilant in observing the environment. We kindly ask that customers continue to validate their services and confirm that everything is functioning as expected. If you encounter any issues, please contact ThinkOn Support so our teams can assist promptly. Service Desk operations may still experience minor delays as we complete final monitoring and validation activities. Next Update We will provide further updates as needed. We appreciate your continued patience and support.

23. monitoring Apr 17, 2026, 03:10 PM UTC

    Dear Customers, Most outstanding issues related to the GUBOV data centre incident have now been resolved. Our teams remain actively engaged and will continue to closely monitor the network to ensure ongoing stability. Monitoring systems are fully functional and operational. We kindly ask that customers continue to report any issues they may encounter so our teams can investigate and assist promptly. Next Update We will provide further updates as needed. We appreciate your continued patience and support.

24. resolved Apr 17, 2026, 09:37 PM UTC

    Dear Customers, All services at the GUBOV data centre have been restored, and there are currently no known outstanding customer issues. While services are stable, our teams will continue to perform follow-up work, including the replacement of certain hardware components, as part of the full remediation process. This work is not expected to impact customer services. We will continue to closely monitor the environment throughout the weekend to ensure ongoing stability and proactively address any potential issues. If you experience any service disruptions or have concerns, please contact ThinkOn Support for assistance. Next Update This incident will be considered resolved, and no further updates are planned unless new issues arise. We appreciate your patience and support throughout this incident.

Read the full incident report →

Started Apr 04, 2026, 03:47 PM UTC· resolved Apr 04, 2026, 05:42 PM UTC

1. investigating Apr 04, 2026, 03:47 PM UTC

   We are currently experiencing an issue affecting access to our Critical Compute environment, which may impact connectivity to vCloud services. At this time, there is no indication that customer workloads are impacted. Our team is actively investigating and working to restore full functionality as quickly as possible. We understand the importance of these services and appreciate your patience while we resolve the issue. Further updates will be provided as more information becomes available. If you have any urgent concerns, please reach out to our support team.

2. resolved Apr 04, 2026, 05:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 01, 2026, 02:34 PM UTC· resolved Apr 01, 2026, 04:49 PM UTC

1. investigating Apr 01, 2026, 02:34 PM UTC

   We are currently experiencing an issue accessing the vCloud portal. Our team is actively investigating the problem.

2. monitoring Apr 01, 2026, 02:38 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 01, 2026, 04:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 24, 2026, 03:19 PM UTC· resolved Apr 01, 2026, 05:30 PM UTC

1. identified Mar 24, 2026, 03:19 PM UTC

   We are currently experiencing a network issue impacting Zerto replication, Veeam backup operations, and overall system performance. Engineering teams are actively investigating and working to mitigate the issue.

2. identified Mar 25, 2026, 06:34 PM UTC

   We are still experiencing slowness with Zerto, VCC, VBO and we are still investigating. Engineering teams are actively investigating and working to mitigate the issue.

3. monitoring Mar 30, 2026, 03:00 PM UTC

   Performance has improved across affected services, including Zerto, VCC, VBO, and overall system operations. Customer reports and system metrics indicate services are stabilizing. ThinkOn engineers will continue to monitor closely to ensure stability is maintained. Updates will be provided if required.

4. resolved Apr 01, 2026, 05:30 PM UTC

   This incident has been resolved

Read the full incident report →

Started Mar 17, 2026, 05:07 PM UTC· resolved Mar 17, 2026, 06:42 PM UTC

1. investigating Mar 17, 2026, 05:07 PM UTC

   We are currently experiencing an issue accessing the Data Protect portal. Our team is actively investigating the problem.

2. resolved Mar 17, 2026, 06:42 PM UTC

   The service disruption with the Data protect portal is now resolved.

Read the full incident report →

Started Feb 20, 2026, 09:20 PM UTC· resolved Feb 21, 2026, 12:11 AM UTC

1. investigating Feb 20, 2026, 09:20 PM UTC

   Please be advised that we are currently troubleshooting a network situation: We are currently investigating a network issue at CGY4. While we troubleshoot and address the root cause, the connection to a few services may become intermittently, such as the vCloud portal and Zerto replications. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the problem. Further updates will be provided as they become available.

2. resolved Feb 21, 2026, 12:11 AM UTC

   This Incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 06:57 PM UTC· resolved Feb 09, 2026, 10:52 PM UTC

1. investigating Feb 09, 2026, 06:57 PM UTC

   We are receiving multiple reports of service issues at the MTL2 site. Our team is actively working to identify the scope and root cause. Updates to follow.

2. investigating Feb 09, 2026, 07:06 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 09, 2026, 09:34 PM UTC

   We are working on resolving the issue.

4. resolved Feb 09, 2026, 10:52 PM UTC

   Services have been restored.

Read the full incident report →