Document360 incident

Service disruption in US environment

Minor Resolved View vendor source →

Document360 experienced a minor incident on July 18, 2024, lasting 585d 13h. The incident has been resolved; the full update timeline is below.

Started
Jul 18, 2024, 11:25 PM UTC
Resolved
Feb 24, 2026, 12:50 PM UTC
Duration
585d 13h
Detected by Pingoru
Jul 18, 2024, 11:25 PM UTC

Update timeline

  1. investigating Jul 18, 2024, 11:25 PM UTC

    We are currently facing downtime in the Portal and User Authentication applications within our US environment, caused by a disruption in Azure services in the Central US region. Our team is actively investigating this issue.

  2. monitoring Jul 19, 2024, 03:16 AM UTC

    We have worked with azure and brought our services back online. We are currently monitoring the situation. Status from azure: https://azure.status.microsoft/en-in/status Impact Statement: Starting at 21:56 UTC on 18 Jul 2024, you have been identified as a customer using Virtual Machines in Central US who may experience connection failures when trying to access some Virtual Machines hosted in the region. These Virtual Machines may have also restarted unexpectedly. Current Status: We are aware of this issue and have engaged multiple teams. We have determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks. We are currently applying mitigation. Customers should see signs of recovery at this time as mitigation applies across resources in the region. The next update will be provided in 60 minutes, or as events warrant.

  3. resolved Feb 24, 2026, 12:50 PM UTC

    Services are stable now and closing this issue. Will continue to monitor the application health.