ThinkOn incident

Service Outage: Probax Hive Object Storage

Notice Resolved View vendor source →

ThinkOn experienced a notice incident on May 8, 2025, lasting 1d 16h. The incident has been resolved; the full update timeline is below.

Started
May 08, 2025, 02:07 AM UTC
Resolved
May 09, 2025, 06:26 PM UTC
Duration
1d 16h
Detected by Pingoru
May 08, 2025, 02:07 AM UTC

Update timeline

  1. investigating May 08, 2025, 02:07 AM UTC

    Please be advised that the Probax Hive Object Storage service is currently experiencing an outage. ThinkOn is actively working with the vendor to investigate and resolve the issue. Impact: This outage affects clients’ ability to perform backups to Object Storage provisioned through Hive. All other services remain unaffected at this time. There is currently no estimated time for resolution (ETA). We will continue to provide updates as new information becomes available. Thank you for your patience.

  2. investigating May 08, 2025, 02:08 AM UTC

    Please be advised that the Probax Hive Object Storage service is currently experiencing an outage. ThinkOn is actively working with the vendor to investigate and resolve the issue. Impact: This outage affects clients’ ability to perform backups to Object Storage provisioned through Hive. All other services remain unaffected at this time. There is currently no estimated time for resolution (ETA). We will continue to provide updates as new information becomes available. Thank you for your patience.

  3. investigating May 08, 2025, 02:27 PM UTC

    Please be advised that the Probax Hive Object Storage service is currently experiencing an outage. ThinkOn is actively working with the vendor to investigate and resolve the issue. Impact: This outage affects clients’ ability to perform backups to Object Storage provisioned through Hive. All other services remain unaffected at this time. There is currently no estimated time for resolution (ETA). We will continue to provide updates as new information becomes available. Thank you for your patience.

  4. resolved May 09, 2025, 06:26 PM UTC

    This incident has been resolved.