Druva inSync incident

Potential Intermittent Backup/Restore disruption

Major Resolved View vendor source →

Druva inSync experienced a major incident on September 18, 2026 affecting inSync Cloud and inSync Cloud (Northern Virginia (us-east-1)) and 1 more component, lasting 25m. The incident has been resolved; the full update timeline is below.

Started
Sep 18, 2026, 11:43 AM UTC
Resolved
Sep 18, 2026, 12:09 PM UTC
Duration
25m
Detected by Pingoru
Sep 18, 2026, 11:43 AM UTC

Affected components

inSync CloudinSync Cloud (Northern Virginia (us-east-1))inSync Cloud (Northern California (us-west-1))inSync Cloud (Oregon (us-west-2))inSync Cloud (Cape Town (af-south-1))inSync Cloud (Hong Kong (ap-east-1))inSync Cloud (Mumbai (ap-south-1))inSync Cloud (Tokyo (ap-northeast-1))inSync Cloud (Seoul (ap-northeast-2))inSync Cloud (Singapore (ap-southeast-1))

Update timeline

  1. identified Sep 18, 2026, 11:43 AM UTC

    We want to proactively inform you that we are performing a backend maintenance at our end. You may experience backup/restore disruption during this time. Our teams are closely monitoring system performance to mitigate any potential delays and ensure background tasks complete successfully. We will keep you updated with the progress. Please feel free to contact the Druva support team at support.druva.com. Druva Support