- Detected by Pingoru
- May 30, 2026, 03:31 AM UTC
- Resolved
- May 31, 2026, 12:05 PM UTC
- Duration
- 1d 8h
Affected: MEL3 Veeam M365
Timeline · 4 updates
-
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.
-
investigating May 30, 2026, 03:34 AM UTC
We are continuing to investigate this issue.
-
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.
-
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 →
- Detected by Pingoru
- May 25, 2026, 08:39 PM UTC
- Resolved
- May 27, 2026, 08:12 PM UTC
- Duration
- 1d 23h
Affected: CGY4 Veeam M365
Timeline · 6 updates
-
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."
-
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.
-
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.
-
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.
-
identified May 27, 2026, 12:27 PM UTC
We are continuing to work towards a resolution.
-
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 →
- Detected by Pingoru
- Apr 26, 2026, 01:15 AM UTC
- Resolved
- Apr 26, 2026, 03:25 AM UTC
- Duration
- 2h 9m
Affected: OTT2 Virtual Compute
Timeline · 2 updates
-
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.
-
resolved Apr 26, 2026, 03:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 02:18 PM UTC
- Resolved
- Apr 20, 2026, 02:53 PM UTC
- Duration
- 34m
Affected: OTT2 Virtual Compute
Timeline · 2 updates
-
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.
-
resolved Apr 20, 2026, 02:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 10:42 PM UTC
- Resolved
- Apr 17, 2026, 09:37 PM UTC
- Duration
- 1d 22h
Affected: GUBOV Internet ConnectivityGUBOV Object StorageGUBOV Virtual ComputeGUBOV Veeam Cloud ConnectGUBOV Veeam for O365GUBOV Virtual Compute BackupsGUBOV Commvault Endpoint BackupGUBOV Zerto Virtual ReplicationGUBOV Veeam M365
Timeline · 24 updates
Read the full incident report →
- Detected by Pingoru
- Apr 04, 2026, 03:47 PM UTC
- Resolved
- Apr 04, 2026, 05:42 PM UTC
- Duration
- 1h 55m
Affected: TOR10 Internet ConnectivityTOR10 Virtual ComputeOTT2 Virtual Compute
Timeline · 2 updates
-
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.
-
resolved Apr 04, 2026, 05:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 02:34 PM UTC
- Resolved
- Apr 01, 2026, 04:49 PM UTC
- Duration
- 2h 14m
Affected: NUBAV Virtual Compute
Timeline · 3 updates
-
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.
-
monitoring Apr 01, 2026, 02:38 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 01, 2026, 04:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 03:19 PM UTC
- Resolved
- Apr 01, 2026, 05:30 PM UTC
- Duration
- 8d 2h
Affected: CGY4 Virtual ComputeCGY4 Zerto Virtual ReplicationCGY4 Veeam M365
Timeline · 4 updates
-
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.
-
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.
-
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.
-
resolved Apr 01, 2026, 05:30 PM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 05:07 PM UTC
- Resolved
- Mar 17, 2026, 06:42 PM UTC
- Duration
- 1h 35m
Affected: CMH1 Veeam M365
Timeline · 2 updates
-
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.
-
resolved Mar 17, 2026, 06:42 PM UTC
The service disruption with the Data protect portal is now resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:20 PM UTC
- Resolved
- Feb 21, 2026, 12:11 AM UTC
- Duration
- 2h 50m
Affected: NUBAV Internet ConnectivityNUBAV Virtual ComputeNUBAV Veeam Cloud ConnectNUBAV Zerto Virtual Replication
Timeline · 2 updates
-
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.
-
resolved Feb 21, 2026, 12:11 AM UTC
This Incident has been resolved.
Read the full incident report →
Critical February 9, 2026 - Detected by Pingoru
- Feb 09, 2026, 06:57 PM UTC
- Resolved
- Feb 09, 2026, 10:52 PM UTC
- Duration
- 3h 54m
Affected: MTL2 Virtual ComputeMTL2 Virtual Compute Backups
Timeline · 4 updates
-
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.
-
investigating Feb 09, 2026, 07:06 PM UTC
We are continuing to investigate this issue.
-
identified Feb 09, 2026, 09:34 PM UTC
We are working on resolving the issue.
-
resolved Feb 09, 2026, 10:52 PM UTC
Services have been restored.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 02:07 AM UTC
- Resolved
- Jan 22, 2026, 09:34 PM UTC
- Duration
- 19h 26m
Affected: CMH1 Virtual Compute
Timeline · 3 updates
-
monitoring Jan 22, 2026, 02:07 AM UTC
We are currently aware of an issue that has caused network instability within our vCloud environments Our team believes they have resolved this issue - but we are monitoring to ensure stability and performance is as expected.
-
monitoring Jan 22, 2026, 02:10 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jan 22, 2026, 09:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 14, 2025, 09:44 AM UTC
- Resolved
- Dec 14, 2025, 11:30 AM UTC
- Duration
- 1h 46m
Affected: DFW1 Internet ConnectivityDFW1 Virtual ComputeDFW1 Virtual Compute BackupsDFW1 Zerto
Timeline · 3 updates
-
investigating Dec 14, 2025, 09:44 AM UTC
We are currently investigating this issue.
-
investigating Dec 14, 2025, 11:29 AM UTC
We are continuing to investigate this issue.
-
resolved Dec 14, 2025, 11:30 AM UTC
Primary link connectivity came back. An investigation has begun as to why the fail over did not function as intended.
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 07:24 PM UTC
- Resolved
- Dec 01, 2025, 08:48 PM UTC
- Duration
- 1h 23m
Affected: TOR10 Internet ConnectivityTOR10 Virtual ComputeTOR10 Veeam M365
Timeline · 2 updates
-
investigating Dec 01, 2025, 07:24 PM UTC
We are currently experiencing network connectivity issues that may impact service availability and performance for some customers. Our engineering and operations teams are actively troubleshooting the issue and working to restore normal service levels as quickly as possible. We will continue to provide updates as more information becomes available. Thank you for your patience while we work to resolve this.
-
resolved Dec 01, 2025, 08:48 PM UTC
The Network service degradation has been resolved.
Read the full incident report →
Critical November 29, 2025 - Detected by Pingoru
- Nov 29, 2025, 04:45 AM UTC
- Resolved
- Dec 01, 2025, 05:34 AM UTC
- Duration
- 2d
Affected: MEL3 Object Storage
Timeline · 3 updates
-
investigating Dec 01, 2025, 12:28 AM UTC
Object Storage is currently inaccessible.
-
investigating Dec 01, 2025, 12:55 AM UTC
We are continuing to investigate this issue.
-
resolved Dec 01, 2025, 05:34 AM UTC
Issue has been resolved. All the OBJECT STORAGE in MEL3 is accessible.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 04:43 AM UTC
- Resolved
- Nov 24, 2025, 05:28 AM UTC
- Duration
- 45m
Affected: MEL3 Veeam M365
Timeline · 2 updates
-
investigating Nov 24, 2025, 04:43 AM UTC
We are currently experiencing an issue where the Data Protect Portal is inaccessible. Our engineering team is actively investigating the root cause and working to restore access as quickly as possible.
-
resolved Nov 24, 2025, 05:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 02:26 PM UTC
- Resolved
- Nov 05, 2025, 03:51 PM UTC
- Duration
- 1h 24m
Affected: OTT2 Virtual Compute
Timeline · 2 updates
-
identified Nov 05, 2025, 02:26 PM UTC
We’ve identified an issue in the underlying infrastructure that is currently causing Virtual Machine creation to fail. Our team is actively working on a fix, and we expect the issue to be resolved shortly. We will provide an update within the next hour.
-
resolved Nov 05, 2025, 03:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 31, 2025, 04:11 PM UTC
- Resolved
- Nov 01, 2025, 12:41 AM UTC
- Duration
- 8h 30m
Affected: OTT2 Object StorageOTT1 RubrikOTT3 Object StorageOTT2 Virtual ComputeOTT2 Virtual Compute BackupsOTT2 Veeam Cloud ConnectOTT2 ZertoOTT2 Veeam VBO
Timeline · 3 updates
-
investigating Oct 30, 2025, 04:30 PM UTC
We are currently Investigating a Burning Smell coming from our Electrical Rooms. Contractors are currently onsite and are investigating this issue. We have Transferred the Critical Loads to Generator Power. Electricians are being dispatched to review the issue. NO customer equipment or services are impacted and our team will monitor the activity closely.
-
identified Oct 31, 2025, 04:11 PM UTC
**UPDATE** The faulty breaker has been replaced successfully. Site loads have been transferred back to hydro power. There was no impact to customer equipment or services during the process.
-
resolved Nov 01, 2025, 12:41 AM UTC
Normal operations have been fully restored.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 06:57 PM UTC
- Resolved
- Oct 30, 2025, 12:59 AM UTC
- Duration
- 6h 1m
Affected: CompassNUBAV Object StorageNUBAV Virtual ComputeNUBAV Zerto Virtual Replication
Timeline · 7 updates
-
investigating Oct 29, 2025, 06:55 PM UTC
We are currently working with a vendor to resolve this issue.
-
investigating Oct 29, 2025, 06:57 PM UTC
We are currently working with a vendor to resolve this issue.
-
identified Oct 29, 2025, 08:06 PM UTC
Update: We are actively collaborating with our vendor to resolve the ongoing issue. The following services are currently impacted: - Virtual Compute & vCloud - Zerto Virtual Replication - Object Storage - Compass Portal We appreciate your patience and will provide further updates as progress is made.
-
identified Oct 29, 2025, 08:42 PM UTC
We are actively collaborating with our vendor to resolve the ongoing issue. The following services are currently impacted: - Virtual Compute & vCloud - Zerto Virtual Replication - Object Storage - Compass Portal We appreciate your patience and will provide further updates as progress is made.
-
identified Oct 29, 2025, 10:20 PM UTC
We are currently in the process of restoring object storage, vCloud, and other affected services. Our teams are actively working to bring systems back online as quickly and safely as possible. Next Update: Scheduled in 90 minutes Thank you for your continued patience. We’ll share further details as progress continues.
-
identified Oct 30, 2025, 12:06 AM UTC
- Storage for dedicated blades has been successfully restored. However, some dedicated blades may require a manual reboot to fully reconnect to storage services. - All affected tenant VMs are now back online and operational. - Our teams are continuing work to restore vCloud access, and we will provide updates as progress continues. Thank you for your patience as we work toward full service recovery.
-
resolved Oct 30, 2025, 12:59 AM UTC
We’re pleased to report that all systems are now back online, including storage, vCloud, and all affected virtual machines (VMs) and physical servers. What You Should Know: -Some virtual machines and dedicated blades may require a manual reboot to reconnect fully to storage. -If you experience any issues accessing your systems, please contact the Service Desk. We sincerely apologize for the inconvenience and appreciate your patience throughout the recovery process.
Read the full incident report →
- Detected by Pingoru
- Sep 05, 2025, 01:48 PM UTC
- Resolved
- Sep 05, 2025, 08:45 PM UTC
- Duration
- 6h 57m
Affected: CGY3 Internet ConnectivityCGY5 Virtual ComputeCGY3 Virtual ComputeCGY3 Object StorageCGY3 Veeam Cloud ConnectCGY3 Zerto ReplicationCGY3 Veeam M365
Timeline · 4 updates
-
investigating Sep 05, 2025, 01:48 PM UTC
We are currently experiencing a network outage at our CGY3 & CGY5 site. Our ThinkOn engineers are working with the vendor to find a resolution for this issue.
-
investigating Sep 05, 2025, 03:08 PM UTC
Thinkon Team is continuing to troubleshoot with the Vendor.
-
investigating Sep 05, 2025, 08:37 PM UTC
Thinkon Team continues troubleshooting the issue with the Vendor
-
resolved Sep 05, 2025, 08:45 PM UTC
ThinkOn engineer worked with the vendor to resolve the issue.
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 07:01 PM UTC
- Resolved
- Aug 23, 2025, 08:20 PM UTC
- Duration
- 1d 1h
Affected: CMB1 Internet ConnectivityCMB1 Virtual ComputeCMB1 Veeam Cloud ConnectCMB1 ZertoCMB1 Object Storage
Timeline · 8 updates
-
investigating Aug 22, 2025, 07:01 PM UTC
We are currently investigating the issue.
-
identified Aug 22, 2025, 07:17 PM UTC
We are currently working with a vendor to resolve the issue.
-
identified Aug 22, 2025, 09:00 PM UTC
We continue working with a vendor to resolve the issue.
-
identified Aug 22, 2025, 10:17 PM UTC
Our ThinkOn engineers are continuing to work with the vendor to resolve the issue.
-
identified Aug 22, 2025, 10:35 PM UTC
Our vendor has dispatched field technicians to the site, and repair work is underway.
-
identified Aug 23, 2025, 12:24 PM UTC
Fibre teams have successfully lashed the damaged fibers on both ends One cable has been fully spliced The fibres on the other end are currently being spliced
-
monitoring Aug 23, 2025, 01:35 PM UTC
The fibre has been repaired and services have come back online. We are currently monitoring the network.
-
resolved Aug 23, 2025, 08:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 03:33 PM UTC
- Resolved
- Aug 20, 2025, 05:01 PM UTC
- Duration
- 1h 28m
Affected: KLP1 Internet ConnectivityKLP1 Virtual Compute
Timeline · 2 updates
-
investigating Aug 20, 2025, 03:33 PM UTC
The DC team is currently investigating the power disturbance at the Data Centre.
-
resolved Aug 20, 2025, 05:01 PM UTC
We would like to inform you that the recent power disturbance at our Kamloops Data Centre has been fully resolved. All systems are now stable and operational.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2025, 07:20 AM UTC
- Resolved
- Aug 13, 2025, 05:25 PM UTC
- Duration
- 10h 5m
Affected: MEL3 Virtual Compute Backups
Timeline · 5 updates
-
investigating Aug 13, 2025, 07:20 AM UTC
We are currently investigating the issue.
-
investigating Aug 13, 2025, 12:18 PM UTC
We are continuing to investigate this issue.
-
investigating Aug 13, 2025, 02:15 PM UTC
We are continuing to investigate this issue.
-
identified Aug 13, 2025, 04:06 PM UTC
Our team has identified the issue and is working on resolving the issue.
-
resolved Aug 13, 2025, 05:25 PM UTC
The incident has now resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 06:15 PM UTC
- Resolved
- Jul 23, 2025, 09:38 PM UTC
- Duration
- 3h 22m
Affected: CGY4 Virtual Compute
Timeline · 3 updates
-
investigating Jul 23, 2025, 06:15 PM UTC
We are currently investigating this issue.
-
investigating Jul 23, 2025, 08:14 PM UTC
We are continue to investigate the issue.
-
resolved Jul 23, 2025, 09:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2025, 02:30 PM UTC
- Resolved
- Jul 16, 2025, 03:08 PM UTC
- Duration
- 38m
Affected: CMB1 Object Storage
Timeline · 2 updates
-
investigating Jul 16, 2025, 02:30 PM UTC
We are currently investigating this issue.
-
resolved Jul 16, 2025, 03:08 PM UTC
This incident has been resolved.
Read the full incident report →