ThinkOn experienced a notice incident on October 29, 2025 affecting Compass and NUBAV Object Storage and 1 more component, lasting 6h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.