Vitally incident

Degraded performance in US

Minor Resolved View vendor source →

Vitally experienced a minor incident on February 15, 2025 affecting Product, lasting 8h 31m. The incident has been resolved; the full update timeline is below.

Started
Feb 15, 2025, 07:28 PM UTC
Resolved
Feb 16, 2025, 03:59 AM UTC
Duration
8h 31m
Detected by Pingoru
Feb 15, 2025, 07:28 PM UTC

Affected components

Product

Update timeline

  1. investigating Feb 15, 2025, 07:28 PM UTC

    Vitally is actively monitoring performance following some database maintenance in one of our US data centers

  2. identified Feb 15, 2025, 09:07 PM UTC

    We have identified the cause of increased latencies and are in the process of mitigating the issue. We do expect some background job delays in the meantime

  3. resolved Feb 16, 2025, 03:59 AM UTC

    We have identified and resolved the cause of the deadlocking which caused increased latencies for customers in our Virginia data center and now consider the incident resolved