May <var data-var='date'>19</var>, <var data-var='time'>12:00</var> UTC Resolved - 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.

Analytics API Degraded Performance in EU

May <var data-var='date'> 7</var>, <var data-var='time'>23:00</var> UTC Resolved - 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.

Short period of real-time data ingestion failures for subset of customers

May <var data-var='date'> 4</var>, <var data-var='time'>19:17</var> UTC Resolved - Login issues have been resolved and we'll continue to monitor as we work to fix the underlying cause going forward. May <var data-var='date'> 4</var>, <var data-var='time'>18:20</var> UTC Monitoring - 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. May <var data-var='date'> 4</var>, <var data-var='time'>18:12</var> UTC Identified - We're seeing logins begin to succeed for affected customers. We are further investigating root cause and completing our remediations. May <var data-var='date'> 4</var>, <var data-var='time'>17:38</var> UTC Investigating - 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.

Login issues for subset of customers

Mar <var data-var='date'>24</var>, <var data-var='time'>18:24</var> UTC Resolved - 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 Mar <var data-var='date'>24</var>, <var data-var='time'>17:16</var> UTC Investigating - 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)

Unexpected Error Volume

Mar <var data-var='date'>15</var>, <var data-var='time'>02:39</var> UTC Completed - The scheduled maintenance has been completed Mar <var data-var='date'>15</var>, <var data-var='time'>02:27</var> UTC Verifying - Verification is currently underway for the maintenance items. Mar <var data-var='date'>14</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 9</var>, <var data-var='time'>19:47</var> UTC Scheduled - We will be undergoing scheduled database maintenance on 2026-03-14. During this time Vitally will remain available but some U.S. users may experience delays in data ingestion and formula calculations.

Scheduled database maintenance

Mar <var data-var='date'>12</var>, <var data-var='time'>20:27</var> UTC Resolved - The issue affecting the AI Copilot has been resolved. The service is fully operational. Thank you for your patience. Mar <var data-var='date'>12</var>, <var data-var='time'>20:26</var> UTC Update - We are continuing to work on a fix for this issue. Mar <var data-var='date'>12</var>, <var data-var='time'>18:03</var> UTC Identified - 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.

AI Copilot — Service Disruption

Feb <var data-var='date'>25</var>, <var data-var='time'>18:29</var> UTC Resolved - 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).

Temporary outage in Analytics API ingestion in one US data center

Feb <var data-var='date'>25</var>, <var data-var='time'>14:03</var> UTC Resolved - 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.

Pages Failing to Load in Vitally

Feb <var data-var='date'>21</var>, <var data-var='time'>16:30</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>21</var>, <var data-var='time'>15:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>18</var>, <var data-var='time'>14:37</var> UTC Scheduled - We will be doing infrastructure maintenance this Saturday at 15:00 UTC (10am US Eastern Time). We expect general site availability during this time but there may be brief moments of unavailability during failovers

Infrastructure Maintenance

Feb <var data-var='date'>11</var>, <var data-var='time'>19:31</var> UTC Resolved - This has been resolved, reloading external docs will clear the error. Apologies for the inconvenience Feb <var data-var='date'>11</var>, <var data-var='time'>18:13</var> UTC Identified - The issue has been identified and a fix is being implemented. Feb <var data-var='date'>11</var>, <var data-var='time'>17:26</var> UTC Investigating - We are currently investigating this issue.

External docs not accessible

Jan <var data-var='date'>25</var>, <var data-var='time'>17:46</var> UTC Resolved - 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 Jan <var data-var='date'>23</var>, <var data-var='time'>20:28</var> UTC Update - 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 Jan <var data-var='date'>23</var>, <var data-var='time'>17:12</var> UTC Identified - 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 Jan <var data-var='date'>23</var>, <var data-var='time'>15:30</var> UTC Investigating - 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

Unexpected Changes to Account Lifecycle Config

Dec <var data-var='date'>23</var>, <var data-var='time'>15:20</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'>23</var>, <var data-var='time'>14:12</var> UTC Update - At this moment, EU customers can login to vitally via `vitally.io` domains instead of `vitally-eu.io` and still access their EU data Dec <var data-var='date'>23</var>, <var data-var='time'>14:10</var> UTC Investigating - We are currently investigating reports of failed SSO logins in our EU data center

SSO Login Failures in EU

Dec <var data-var='date'>17</var>, <var data-var='time'>20:28</var> UTC Resolved - 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. Dec <var data-var='date'>17</var>, <var data-var='time'>19:57</var> UTC Monitoring - 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. Dec <var data-var='date'>17</var>, <var data-var='time'>19:56</var> UTC Investigating - Our analytics API is currently rate limiting at a high rate than normal. We are currently investigating and will provide an update shortly

Analytics API Rate Limiting Spike

Nov <var data-var='date'>17</var>, <var data-var='time'>17:45</var> UTC Resolved - We have broadly observed recovery and are closing this incident Nov <var data-var='date'>12</var>, <var data-var='time'>20:00</var> UTC Update - 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 Nov <var data-var='date'>11</var>, <var data-var='time'>20:21</var> UTC Monitoring - 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. Nov <var data-var='date'>10</var>, <var data-var='time'>20:43</var> UTC Identified - We've seen some issues with loading times and occasional timeouts across the Vitally app. Identifying and resolving these issues is our top priority.

Issues with loading times across Vitally

Nov <var data-var='date'>14</var>, <var data-var='time'>14:48</var> UTC Resolved - The fix has been deployed. Any users still experiencing issues should make sure they have the latest version by refreshing all browser pages. Nov <var data-var='date'>13</var>, <var data-var='time'>23:08</var> UTC Identified - An issue with saving CustomObject traits has been identified and a fix is being deployed

Issues saving Custom Object traits

Nov <var data-var='date'> 6</var>, <var data-var='time'>22:42</var> UTC Resolved - The issue has been resolved. Public docs now load properly again. Nov <var data-var='date'> 6</var>, <var data-var='time'>21:29</var> UTC Identified - 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.

Docs viewed from shareable links failing to load

Nov <var data-var='date'> 5</var>, <var data-var='time'>01:30</var> UTC Completed - The scheduled maintenance has been completed. Nov <var data-var='date'> 5</var>, <var data-var='time'>01:16</var> UTC Update - Scheduled maintenance is still in progress. We will provide updates as necessary. Nov <var data-var='date'> 5</var>, <var data-var='time'>01:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'> 3</var>, <var data-var='time'>20:12</var> UTC Scheduled - Vitally will be performing routine database maintenance on 11/5/25 between 01:00 and 02:30 UTC. Vitally will remain accessible throughout this time. You may notice some delays in data ingestion or Vitally automations during this period.

Oct <var data-var='date'>20</var>, <var data-var='time'>20:33</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>19:45</var> UTC Monitoring - We're starting to see some Vitally Call Recorder instances successfully join meetings. We'll continue to monitor as AWS recovers from their outage Oct <var data-var='date'>20</var>, <var data-var='time'>14:24</var> UTC Investigating - 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

Vitally Call Recorder impacted by AWS outage

Sep <var data-var='date'>13</var>, <var data-var='time'>01:13</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>13</var>, <var data-var='time'>00:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>10</var>, <var data-var='time'>13:30</var> UTC Scheduled - We will be upgrading our database instances in all regions. The Vitally application may be intermittently unavailable during this time and jobs may take longer to process than usual.

Database upgrade

Aug <var data-var='date'>29</var>, <var data-var='time'>02:48</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>29</var>, <var data-var='time'>20:18</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>28</var>, <var data-var='time'>16:46</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>28</var>, <var data-var='time'>15:54</var> UTC Investigating - We are currently investigating this issue.

Some custom object syncs from Jira are delayed

Aug <var data-var='date'> 7</var>, <var data-var='time'>21:58</var> UTC Resolved - This incident has been resolved. Data backfills for missed events are ongoing and will be completed within a number of hours. Aug <var data-var='date'> 7</var>, <var data-var='time'>15:22</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:39</var> UTC Identified - The issue has been identified and a fix is being implemented.

Product events are not syncing from Intercom

Aug <var data-var='date'> 6</var>, <var data-var='time'>22:29</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'> 6</var>, <var data-var='time'>14:16</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'> 5</var>, <var data-var='time'>22:04</var> UTC Monitoring - 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. Aug <var data-var='date'> 5</var>, <var data-var='time'>15:33</var> UTC Update - We are continuing to investigate the issue. Playbook execution may be delayed. Formula field calculation is delayed. Aug <var data-var='date'> 5</var>, <var data-var='time'>11:25</var> UTC Investigating - We are investigating performance issues causing elevated server response times. Playbook execution and formula field calculation is delayed.

Elevated Server Response Times

Jul <var data-var='date'>24</var>, <var data-var='time'>17:42</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>24</var>, <var data-var='time'>15:47</var> UTC Update - We are continuing to work on a fix for this issue. Jul <var data-var='date'>24</var>, <var data-var='time'>15:46</var> UTC Identified - 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

Custom surveys outage

Jul <var data-var='date'>18</var>, <var data-var='time'>18:59</var> UTC Resolved - google has closed their incident Jul <var data-var='date'>18</var>, <var data-var='time'>15:55</var> UTC Identified - Google has identified their incident and will publish updates publicly here: https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J Jul <var data-var='date'>18</var>, <var data-var='time'>15:39</var> UTC Investigating - 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 Outage

Jun <var data-var='date'> 3</var>, <var data-var='time'>18:02</var> UTC Resolved - Our vendor has resolved this and the page loads on refresh Jun <var data-var='date'> 3</var>, <var data-var='time'>16:54</var> UTC Identified - Our marketing vendor is experiencing an outage (https://status.webflow.com) which is causing `vitally.io` to not load. In order to login, you can directly navigate to https://login.vitally.io. No Vitally Product experiences are currently impacted

Is Vitally down?

Vitally status is UP

Lastest published events

Analytics API Degraded Performance in EU

Short period of real-time data ingestion failures for subset of customers

Login issues for subset of customers

Vitally Services, Components and Regions

Recent Vitally events

Analytics API Degraded Performance in EU

Short period of real-time data ingestion failures for subset of customers

Login issues for subset of customers

Unexpected Error Volume

Scheduled database maintenance

AI Copilot — Service Disruption

Get your FREE account now,
5 monitors included!

Is Vitally down?

Vitally status is UP

Lastest published events

Analytics API Degraded Performance in EU

Short period of real-time data ingestion failures for subset of customers

Login issues for subset of customers

Vitally Services, Components and Regions

Recent Vitally events

Analytics API Degraded Performance in EU

Short period of real-time data ingestion failures for subset of customers

Login issues for subset of customers

Unexpected Error Volume

Scheduled database maintenance

AI Copilot — Service Disruption

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!