Quest incident

Cloud Provider Resources Issue - On Demand Impacted

Major Resolved View vendor source →

Quest experienced a major incident on January 25, 2023 affecting US Region and Australia Region and 1 more component, lasting 2h 56m. The incident has been resolved; the full update timeline is below.

Started
Jan 25, 2023, 08:17 AM UTC
Resolved
Jan 25, 2023, 11:14 AM UTC
Duration
2h 56m
Detected by Pingoru
Jan 25, 2023, 08:17 AM UTC

Affected components

US RegionAustralia RegionCanada RegionEU RegionUK Region

Update timeline

  1. investigating Jan 25, 2023, 08:17 AM UTC

    Our cloud provider has confirmed that they are experiencing intermittent issues that could impact On Demand customers when accessing the On Demand Portal and impair the functionality of the On Demand products. We are monitoring the situation and will update as soon as we know more.

  2. investigating Jan 25, 2023, 09:15 AM UTC

    Our cloud provider is actively investigating the issue and will share updates as soon as more is known. Please refer to https://azure.status.microsoft/en-us/status for more information on this issue. We are continuing to monitor the situation and will update as soon as we know more.

  3. identified Jan 25, 2023, 09:51 AM UTC

    Our cloud provider has identified a recent WAN update as the likely underlying cause, and has taken steps to roll back this update. Their latest telemetry shows signs of recovery across multiple regions and services, and they are continuing to actively monitor the situation. We are continuing to monitor the situation and will update as soon as we know more.

  4. monitoring Jan 25, 2023, 10:24 AM UTC

    Our cloud provider has confirmed that with WAN networking, they are now seeing recovery, and they are actively working to ensure full recovery for impacted services. Please refer to https://azure.status.microsoft/en-us/status for more information on this issue. We are continuing to monitor the situation and will update as soon as we know more.

  5. resolved Jan 25, 2023, 11:14 AM UTC

    This incident has been resolved by our cloud provider.