Vitally incident

Degraded performance in US

Minor Resolved View vendor source →

Vitally experienced a minor incident on February 17, 2025 affecting Product, lasting 2d 11h. The incident has been resolved; the full update timeline is below.

Started
Feb 17, 2025, 06:19 AM UTC
Resolved
Feb 19, 2025, 06:00 PM UTC
Duration
2d 11h
Detected by Pingoru
Feb 17, 2025, 06:19 AM UTC

Affected components

Product

Update timeline

  1. investigating Feb 17, 2025, 06:19 AM UTC

    Vitally is experiencing an unusual amount of server timeouts. We are looking into the incident.

  2. identified Feb 17, 2025, 06:43 AM UTC

    We have mitigated the issue, though background jobs may experience delays.

  3. resolved Feb 19, 2025, 06:00 PM UTC

    Due to the database maintenance we performed on Feb 15, our database was struggling to handle operational load. We rolled back some of those changes and have prioritized work to optimize our database usage to prevent incidents like this in the future.