Vitally Outage History
Vitally is up right nowPingoru has recorded 50 incidents for Vitally: 14 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 3 | 2 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 547 (0%) |
Incidents, newest first
Minor May 19, 2026 Analytics API Degraded Performance in EU 4m
Started May 19, 2026, 11:59 AM UTC· resolved May 19, 2026, 12:03 PM UTC
- resolved May 19, 2026, 12:17 PM UTC
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.
Minor May 7, 2026 Short period of real-time data ingestion failures for subset of customers –
Started May 07, 2026, 11:00 PM UTC· resolved May 07, 2026, 11:00 PM UTC
- resolved May 08, 2026, 05:20 PM UTC
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.
Major May 4, 2026 Login issues for subset of customers 1h 38m Product
Started May 04, 2026, 05:38 PM UTC· resolved May 04, 2026, 07:17 PM UTC
- investigating May 04, 2026, 05:38 PM UTC
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.
- identified May 04, 2026, 06:12 PM UTC
We're seeing logins begin to succeed for affected customers. We are further investigating root cause and completing our remediations.
- monitoring May 04, 2026, 06:20 PM UTC
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.
- resolved May 04, 2026, 07:17 PM UTC
Login issues have been resolved and we'll continue to monitor as we work to fix the underlying cause going forward.
Notice March 24, 2026 Unexpected Error Volume 1h 7m Product
Started Mar 24, 2026, 05:16 PM UTC· resolved Mar 24, 2026, 06:24 PM UTC
- investigating Mar 24, 2026, 05:16 PM UTC
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)
- resolved Mar 24, 2026, 06:24 PM UTC
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
Notice March 12, 2026 AI Copilot — Service Disruption 2h 23m
Started Mar 12, 2026, 06:03 PM UTC· resolved Mar 12, 2026, 08:27 PM UTC
- identified Mar 12, 2026, 06:03 PM UTC
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.
- identified Mar 12, 2026, 08:26 PM UTC
We are continuing to work on a fix for this issue.
- resolved Mar 12, 2026, 08:27 PM UTC
The issue affecting the AI Copilot has been resolved. The service is fully operational. Thank you for your patience.
Notice February 25, 2026 Temporary outage in Analytics API ingestion in one US data center 19h 5m Analytics Data Processing
Started Feb 25, 2026, 06:14 PM UTC· resolved Feb 26, 2026, 01:19 PM UTC
- resolved Feb 25, 2026, 06:29 PM UTC
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).
Notice February 25, 2026 Pages Failing to Load in Vitally – Product
Started Feb 25, 2026, 02:03 PM UTC· resolved Feb 25, 2026, 02:03 PM UTC
- resolved Feb 25, 2026, 02:03 PM UTC
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.
Major February 11, 2026 External docs not accessible 2h 5m Product
Started Feb 11, 2026, 05:26 PM UTC· resolved Feb 11, 2026, 07:31 PM UTC
- investigating Feb 11, 2026, 05:26 PM UTC
We are currently investigating this issue.
- identified Feb 11, 2026, 06:13 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Feb 11, 2026, 07:31 PM UTC
This has been resolved, reloading external docs will clear the error. Apologies for the inconvenience
Notice January 23, 2026 Unexpected Changes to Account Lifecycle Config 2d 2h Product
Started Jan 23, 2026, 03:30 PM UTC· resolved Jan 25, 2026, 05:46 PM UTC
- investigating Jan 23, 2026, 03:30 PM UTC
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
- identified Jan 23, 2026, 05:12 PM UTC
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
- identified Jan 23, 2026, 08:28 PM UTC
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
- resolved Jan 25, 2026, 05:46 PM UTC
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
Minor December 23, 2025 SSO Login Failures in EU 1h 9m Product
Started Dec 23, 2025, 02:10 PM UTC· resolved Dec 23, 2025, 03:20 PM UTC
- investigating Dec 23, 2025, 02:10 PM UTC
We are currently investigating reports of failed SSO logins in our EU data center
- investigating Dec 23, 2025, 02:12 PM UTC
At this moment, EU customers can login to vitally via `vitally.io` domains instead of `vitally-eu.io` and still access their EU data
- resolved Dec 23, 2025, 03:20 PM UTC
This incident has been resolved.
Notice December 17, 2025 Analytics API Rate Limiting Spike 32m Analytics Data Processing
Started Dec 17, 2025, 07:56 PM UTC· resolved Dec 17, 2025, 08:28 PM UTC
- investigating Dec 17, 2025, 07:56 PM UTC
Our analytics API is currently rate limiting at a high rate than normal. We are currently investigating and will provide an update shortly
- monitoring Dec 17, 2025, 07:57 PM UTC
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.
- resolved Dec 17, 2025, 08:28 PM UTC
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.
Notice November 13, 2025 Issues saving Custom Object traits 15h 39m Product
Started Nov 13, 2025, 11:08 PM UTC· resolved Nov 14, 2025, 02:48 PM UTC
- identified Nov 13, 2025, 11:08 PM UTC
An issue with saving CustomObject traits has been identified and a fix is being deployed
- resolved Nov 14, 2025, 02:48 PM UTC
The fix has been deployed. Any users still experiencing issues should make sure they have the latest version by refreshing all browser pages.
Minor November 10, 2025 Issues with loading times across Vitally 6d 21h Product
Started Nov 10, 2025, 08:43 PM UTC· resolved Nov 17, 2025, 05:45 PM UTC
- 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.
- 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.
- 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
- resolved Nov 17, 2025, 05:45 PM UTC
We have broadly observed recovery and are closing this incident
Major November 6, 2025 Docs viewed from shareable links failing to load 1h 12m Product
Started Nov 06, 2025, 09:29 PM UTC· resolved Nov 06, 2025, 10:42 PM UTC
- identified Nov 06, 2025, 09:29 PM UTC
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.
- resolved Nov 06, 2025, 10:42 PM UTC
The issue has been resolved. Public docs now load properly again.
Notice October 20, 2025 Vitally Call Recorder impacted by AWS outage 6h 9m Product
Started Oct 20, 2025, 02:24 PM UTC· resolved Oct 20, 2025, 08:33 PM UTC
- investigating Oct 20, 2025, 02:24 PM UTC
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
- monitoring Oct 20, 2025, 07:45 PM UTC
We're starting to see some Vitally Call Recorder instances successfully join meetings. We'll continue to monitor as AWS recovers from their outage
- resolved Oct 20, 2025, 08:33 PM UTC
This incident has been resolved.
Minor August 28, 2025 Some custom object syncs from Jira are delayed 10h 54m Product
Started Aug 28, 2025, 03:54 PM UTC· resolved Aug 29, 2025, 02:48 AM UTC
- investigating Aug 28, 2025, 03:54 PM UTC
We are currently investigating this issue.
- identified Aug 29, 2025, 02:46 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 29, 2025, 02:47 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 29, 2025, 02:48 AM UTC
This incident has been resolved.
Minor August 6, 2025 Product events are not syncing from Intercom 1d 4h Product
Started Aug 06, 2025, 05:39 PM UTC· resolved Aug 07, 2025, 09:58 PM UTC
- identified Aug 06, 2025, 05:39 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 07, 2025, 03:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 07, 2025, 09:58 PM UTC
This incident has been resolved. Data backfills for missed events are ongoing and will be completed within a number of hours.
Minor August 5, 2025 Elevated Server Response Times 1d 11h Product
Started Aug 05, 2025, 11:25 AM UTC· resolved Aug 06, 2025, 10:29 PM UTC
- investigating Aug 05, 2025, 11:25 AM UTC
We are investigating performance issues causing elevated server response times. Playbook execution and formula field calculation is delayed.
- investigating Aug 05, 2025, 03:33 PM UTC
We are continuing to investigate the issue. Playbook execution may be delayed. Formula field calculation is delayed.
- monitoring Aug 05, 2025, 10:04 PM UTC
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.
- monitoring Aug 06, 2025, 02:16 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 06, 2025, 10:29 PM UTC
This incident has been resolved.
Minor July 24, 2025 Custom surveys outage 1h 55m Product
Started Jul 24, 2025, 03:46 PM UTC· resolved Jul 24, 2025, 05:42 PM UTC
- identified Jul 24, 2025, 03:46 PM UTC
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
- identified Jul 24, 2025, 03:47 PM UTC
We are continuing to work on a fix for this issue.
- resolved Jul 24, 2025, 05:42 PM UTC
This incident has been resolved.
Notice July 18, 2025 Google Outage 3h 20m Product
Started Jul 18, 2025, 03:39 PM UTC· resolved Jul 18, 2025, 06:59 PM UTC
- investigating Jul 18, 2025, 03:39 PM UTC
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
- identified Jul 18, 2025, 03:55 PM UTC
Google has identified their incident and will publish updates publicly here: https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J
- resolved Jul 18, 2025, 06:59 PM UTC
google has closed their incident
Notice June 3, 2025 External vitally.io Site Down 1h 7m
Started Jun 03, 2025, 04:54 PM UTC· resolved Jun 03, 2025, 06:02 PM UTC
- identified Jun 03, 2025, 04:54 PM UTC
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
- resolved Jun 03, 2025, 06:02 PM UTC
Our vendor has resolved this and the page loads on refresh
Minor May 27, 2025 Feature flags not evaluating, 360s reverting for some users 2h 46m Product
Started May 27, 2025, 02:01 PM UTC· resolved May 27, 2025, 04:48 PM UTC
- identified May 27, 2025, 02:01 PM UTC
Our feature flag provider, LaunchDarkly, is experiencing an incident which is causing feature flags not to evaluate for some users. Users who have switched to the new 360 may see a regression to the old 360. Additionally, calendar views and meetings may be unavailable.
- monitoring May 27, 2025, 02:22 PM UTC
Our feature flag provider, LaunchDarkly, has identified the issue. Access to the new 360s, calendar views, and meetings should now be restored for users. We are continuing to monitor the situation to ensure stability.
- resolved May 27, 2025, 04:48 PM UTC
LaunchDarkly has resolved the incident affecting our feature flags. Access to the new 360s, calendar views, and meetings should be fully operational.
Notice April 30, 2025 CSV Upload Errors 18h 4m Product
Started Apr 30, 2025, 07:04 PM UTC· resolved May 01, 2025, 01:09 PM UTC
- investigating Apr 30, 2025, 07:04 PM UTC
We are seeing a high rate of CSV uploads failing, we are investigating the root cause now
- identified Apr 30, 2025, 07:35 PM UTC
We've identified why CSV upload requests are failing and are preparing a fix now
- monitoring Apr 30, 2025, 08:47 PM UTC
The fix has shipped to restore CSV upload ability and we are monitoring for additional errors
- resolved May 01, 2025, 01:09 PM UTC
We have not seen errors since shipping a fix yesterday and consider this incident resolved
Notice April 21, 2025 Degraded Search Performance 1d 1h Product, Analytics Data Processing
Started Apr 21, 2025, 04:46 PM UTC· resolved Apr 22, 2025, 05:53 PM UTC
- investigating Apr 21, 2025, 04:46 PM UTC
Certain searches in the product will be significantly slower. Some searches may error. We are currently investigating this issue.
- identified Apr 21, 2025, 04:50 PM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 21, 2025, 06:20 PM UTC
Search clusters are currently reindexing. Playbooks are paused until complete. Analytics tracks not currently ingesting.
- identified Apr 21, 2025, 06:44 PM UTC
Playbooks have been resumed. We are monitoring as the system recovers from delays.
- monitoring Apr 21, 2025, 06:44 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 22, 2025, 05:53 PM UTC
We are continuing to monitor for any further issues.
- resolved Apr 22, 2025, 05:53 PM UTC
This incident has been resolved.
Critical March 7, 2025 Unexpected playbook behavior 1d 12h Product
Started Mar 07, 2025, 05:02 AM UTC· resolved Mar 08, 2025, 05:25 PM UTC
- investigating Mar 07, 2025, 05:02 AM UTC
Due to a bug, we are experiencing unexpected playbook behavior. We have identified the root cause and are currently working to correct these unexpected behaviors. Playbooks are paused in the meantime.
- identified Mar 07, 2025, 12:35 PM UTC
The incident has been isolated to playbooks that contain an “is not set” filter. Playbooks that do not contain an “is not set” filter have been resumed. Playbooks that contain an “is not set” filter remain paused. Targets in playbooks with an “is not set” filter were incorrectly removed and may have had actions undone. We are working to restore those playbooks to the state they were before the bug shipped before resuming execution.
- identified Mar 07, 2025, 02:21 PM UTC
All playbooks remain paused while we work to correct the state of data to avoid propagation of unintended effects by partially restoring playbook execution. The team is working through this and apologizes for this disruption to your workflows
- identified Mar 08, 2025, 12:59 AM UTC
We are continuing to work towards recovery. At this point, we have restored data for most misapplied playbooks and are continuing to work towards resolving the remaining ones. Once we finish this portion of the incident response, we will be resuming all playbook execution. We will continue to do everything possible to expedite the resolution of this incident.
- monitoring Mar 08, 2025, 02:54 AM UTC
At approximately 1:30pm ET Thursday, March 6th, we shipped a bug to production that caused all “is not set” filters to evaluate to “false”. This caused a number of systemic issues: - Lifecycle tracking rules may have been incorrectly applied. - Many views and widgets were not showing accurate data. - Playbooks with an “is not set” rule would have all of their enrollees unmatched and undone. At 4pm ET, our Support team escalated widespread reports of these issues and an incident was declared. The team identified the pull request with the bug and reverted it. We also paused playbook execution pre-revert to evaluate impact. That revert finished at 5pm ET, at which point views & widgets started working again. At that point, the team also forced a reprocess of lifecycle tracking rules, which corrected incorrectly tracked accounts and organizations. However, the impact of re-enrolling entities into playbooks was potentially dangerous. So, the team started writing a restore job to reset playbooks to their prior place within the playbook run and re-do actions wherever possible. Writing and testing that job took until about 10pm ET Friday, March 7th. We have since run those jobs for all affected playbooks. As things stand now, we have reverted all undone playbooks to the best of our ability. For playbooks with an “is not set” rule, enrollees would have seen the following action behavior: - Assign a Key Role: *if* assignment strategy is “unassign”, would have unassigned affected enrollees. Those have been restored. - Create an Indicator: would have ended the indicator. Those have been restored. - Add to Segment: would have exited the segment. Those have been added back into the segment. - Start a conversation, reply to a conversation: *if* undo strategy is “delete if unset” *and* messages had been created but not yet sent, they would have been deleted. This is unrecoverable. - Create a task: *if* undo strategy is “delete the task”, tasks would have been deleted. Those have been restored. - Update a task: *if* undo strategy is “revert the updates”, task updates would have been reverted. Those have been restored. - Create a project: *if* undo strategy is “delete the project”, projects and incomplete tasks would have been deleted. Those have been restored. - Create a doc: *if* undo strategy is “delete the doc”, docs would have been deleted. Those have been restored. - Set a goal: *if* undo strategy is “delete the goal”, goals would have been deleted. Those have been restored. - Update a trait: *if* undo strategy is “delete the trait’s value”, traits would have been set to null. Those values have been restored. - Send a segment track: unaffected - Ping a webhook: unaffected - Show an NPS survey: NPS surveys would not have been shown to enrollees previously matching affected playbooks until they were restore. However, there may have been second-order effects throughout the system that are difficult to identify. If one playbook was responsible for maintaining customer segmentation had an “is set” filter, it would have removed customers from segments. If a second playbook had filters on those segments, it may have also run incorrectly. All playbooks have since been re-run and should be reset to the most accurate state we’re able to attain right now. If you still see systemic issues with any of your playbooks, please report them to our Support team via in-app chat or at [email protected]. We have a dedicated internal channel for these issues and will work to the best of our ability to minimize the impact on your business and customers. We deeply apologize for the impact this has caused you in managing your customer relationships and will continue to dedicate resources to ensure continuity of your business operations.
- resolved Mar 08, 2025, 05:25 PM UTC
This incident has been resolved. Please contact support if you see any remaining issues.