Vitally had 20 outages in the last 2 years totaling 323h 35m of downtime — averaging 0.8 incidents per month.
There were 20 Vitally outages since July 18, 2025 totaling 323h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
The Analytics API in our EU region had elevated error rates for approximately four minutes, from 11:59 UTC to 12:03 UTC. During this time, requests to this API may have failed. We have identified the cause and resolved the issue.
Yesterday, on May 7, 2026, we experienced roughly a 20 minute window where we failed to ingest real-time data from our integrations. Roughly 5% of requests during this time period failed for a subset of our customers. The root cause is identified and our engineering team is implementing measures to prevent such incidents in the future.
We have been notified of an issue causing timeouts loading the app for some specific customers. We are working diligently to find and alleviate the cause of the issue.
We're seeing logins begin to succeed for affected customers. We are further investigating root cause and completing our remediations.
We have identified the root cause and we are no longer seeing any issues with logins. We will be closely monitoring for any further degradations as we fully resolve the issue.
Login issues have been resolved and we'll continue to monitor as we work to fix the underlying cause going forward.
We are currently investigating a blip in errors impacting the ability to use Vitally for about 60 seconds starting at 1:04PM Eastern Time (about 12 minutes ago)
We have not seen additional spikes in errors across our platform outside of 1:04-1:05pm ET today, we continue with an internal investigation into the root cause
We identified an issue causing the AI Copilot to be unavailable. A fix has been implemented and is currently being deployed. We expect the service to be restored shortly and will provide an update once the deployment is complete.
We are continuing to work on a fix for this issue.
The issue affecting the AI Copilot has been resolved. The service is fully operational. Thank you for your patience.
We were notified that for about five minutes, our auto-scaler did not scale quickly enough to handle a very severe burst of messages. Messages will not have been received during this time period for a portion of our US customers. The downtime was roughly from 18:14 to 18:19 UTC (1:14-1:19pm ET).
Earlier today, some users may have experienced issues with pages in Vitally not loading correctly. The root cause has been identified, and the issue has been resolved. If you are still experiencing loading issues, please refresh the page.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This has been resolved, reloading external docs will clear the error. Apologies for the inconvenience
We are currently investigating reports of unexpected changes to behavior for marking accounts as Tracked or Churned, where churned accounts are being considered as Tracked
We have identified the source of the Revenue Config updates in a backfill job ran yesterday. We are working to restore prior versions of this configuration from our nightly backup before this backfill ran and correct the data in Vitally
We have restored Revenue Configs which were modified when our backfill ran, but not undone updates users may have made since then. If your revenue config continues to be out of alignment with your expectation, write in to support. We are now beginning to reprocess Vitally data to correctly set churned/tracked status of Customer records
We have finished backfilling data for impacted customers. If you have a revenue config that still does not look right or historical revenue numbers on your customer records that are still adrift for 1/22, do reach out and we'll follow up. We're sorry for the impact this has had and will be conducting a full root cause analysis to prevent incidents like this in the future
We are currently investigating reports of failed SSO logins in our EU data center
At this moment, EU customers can login to vitally via `vitally.io` domains instead of `vitally-eu.io` and still access their EU data
This incident has been resolved.
Our analytics API is currently rate limiting at a high rate than normal. We are currently investigating and will provide an update shortly
Our analytics API incorrectly applied rate limits between 2025-12-17T14:36:48 and 2025-12-17T14:45:29. During this time exceeding 1,000 requests in a minute resulted in a 429 response. This was caused by an incorrect configuration which was quickly corrected.
This incident has been resolved. During the period where incorrect rate limits were applied, we were correctly returning 429 status codes. Any request that received a 429 response can be safely resent at this time.
An issue with saving CustomObject traits has been identified and a fix is being deployed
The fix has been deployed. Any users still experiencing issues should make sure they have the latest version by refreshing all browser pages.
We've seen some issues with loading times and occasional timeouts across the Vitally app. Identifying and resolving these issues is our top priority.
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.
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
We have broadly observed recovery and are closing this incident
When navigating to a publicly shared doc via the shared link, an error will occur and the doc will not be viewable. We have identified the issue and are quickly working to resolve it.
The issue has been resolved. Public docs now load properly again.
The Vitally Call Recorder may be intermittently failing to join meetings due to the ongoing AWS outage. We're continuing to monitor the situation and will provide an update when available
We're starting to see some Vitally Call Recorder instances successfully join meetings. We'll continue to monitor as AWS recovers from their outage
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Data backfills for missed events are ongoing and will be completed within a number of hours.
We are investigating performance issues causing elevated server response times. Playbook execution and formula field calculation is delayed.
We are continuing to investigate the issue. Playbook execution may be delayed. Formula field calculation is delayed.
We've identified the issue and server response times have normalized. Some queues, including formula field calculation and some integrations, are continuing to catch up.
We are continuing to monitor for any further issues.
This incident has been resolved.
The custom survey submission page won't load when accessed via generic link instead of a personalized email invite link We have identified the cause and are working on a fix
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are seeing elevated failure rate of processes depending on Google for SSO login. If you utilize Google SSO to log in to Vitally, you may experience issues in doing so. We are not yet seeing errors in Google for Calendar or Mail syncs and are still waiting for Google to publicly acknowledge this outage but the internet is containing many other reports
Google has identified their incident and will publish updates publicly here: https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J
google has closed their incident