Vitally incident

Issues with loading times across Vitally

Minor Resolved View vendor source →

Vitally experienced a minor incident on November 10, 2025 affecting Product, lasting 6d 21h. The incident has been resolved; the full update timeline is below.

Started
Nov 10, 2025, 08:43 PM UTC
Resolved
Nov 17, 2025, 05:45 PM UTC
Duration
6d 21h
Detected by Pingoru
Nov 10, 2025, 08:43 PM UTC

Affected components

Product

Update timeline

  1. identified Nov 10, 2025, 08:43 PM UTC

    We've seen some issues with loading times and occasional timeouts across the Vitally app. Identifying and resolving these issues is our top priority.

  2. monitoring Nov 11, 2025, 08:21 PM UTC

    We've identified the root cause which induced unexpected load on our servers. We've remediated the root cause and are working on long-term solutions. In addition, we've scaled up our servers to ensure that loading times are back to normal. User-facing disruptions seem to be resolved, and we are monitoring closely to ensure continued performance improvements.

  3. monitoring Nov 12, 2025, 08:00 PM UTC

    As part of monitoring, we have observed slow uptake of our latest client version which resolves the load issues. So, we are now relegating the heavier traffic from old clients onto a dedicated server pool, isolating their load to allow our existing servers to better provide Vitally's app experience. We expect this to further reduce load times of pages in Vitally across our customers. If you are still having a poor experience, please refresh your Vitally tabs in order to use the latest version of our application

  4. resolved Nov 17, 2025, 05:45 PM UTC

    We have broadly observed recovery and are closing this incident