Oct <var data-var='date'> 4</var>, <var data-var='time'>21:07</var> UTC Completed - The scheduled maintenance has been completed. Oct <var data-var='date'> 4</var>, <var data-var='time'>20:57</var> UTC Verifying - Verification is currently underway for the maintenance items. Oct <var data-var='date'> 4</var>, <var data-var='time'>20:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'> 2</var>, <var data-var='time'>02:38</var> UTC Scheduled - We will be performing a version upgrade on one of our core data stores, commencing Sunday 4 October at 20:00 UTC (Sun 1pm PDT / 4pm EDT / 9pm BST / 10pm CEST, Mon 5 October 7am AEDT). The aim of this maintenance is to improve system performance, reliability and security. We expect the maintenance to be completed within one hour, but depending on how long the data migration takes, it could take up to two hours. This system is used for message delivery, so email, push and SMS sending, as well as webhooks, will be paused during the maintenance period. Once the upgrade is complete, delivery will resume and catch up. All other services, including the Vero API, event and data processing will continue to operate as normal. Existing data stored in Vero will not be affected. Messages queued before or during the maintenance window will not be lost and will be delivered once maintenance is complete.

Database upgrades and maintenance

Sep <var data-var='date'>27</var>, <var data-var='time'>20:15</var> UTC Completed - We've postponed today's scheduled maintenance. No action is needed on your end, and we'll announce the new maintenance window later this week. Sep <var data-var='date'>27</var>, <var data-var='time'>20:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>25</var>, <var data-var='time'>03:25</var> UTC Scheduled - We will be performing a version upgrade on one of our core data stores, commencing Sunday 27 September at 20:00 UTC (Sun 1pm PDT / 4pm EDT / 9pm BST / 10pm CEST, Mon 28 September 6am AEST). The aim of this maintenance is to improve system performance, reliability and security. We expect the maintenance to be completed within one hour, but depending on how long the data migration takes, it could take up to two hours. This system is used for message delivery, so email, push and SMS sending, as well as webhooks, will be paused during the maintenance period. Once the upgrade is complete, delivery will resume and catch up. All other services, including the Vero API, event and data processing will continue to operate as normal. Existing data stored in Vero will not be affected. Messages queued before or during the maintenance window will not be lost and will be delivered once maintenance is complete.

Sep <var data-var='date'>13</var>, <var data-var='time'>21:08</var> UTC Completed - All maintenance tasks have been completed. Our API and background processing infrastructure is functioning normally. There is still a small backlog of tasks from the maintenance period which should processed within the next 30 minutes. Sep <var data-var='date'>13</var>, <var data-var='time'>20:48</var> UTC Update - Our API is now accepting requests successfully. We're still working to bring back our background processing infrastructure, so there will be a delay in processing the API data (profile updates, event tracking, etc) as well as message delivery. Sep <var data-var='date'>13</var>, <var data-var='time'>20:32</var> UTC Verifying - The data store has been upgraded. We're now working to bring back all impacted services. Sep <var data-var='date'>13</var>, <var data-var='time'>20:01</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>11</var>, <var data-var='time'>04:00</var> UTC Scheduled - We will be performing a version upgrade on one of our core data stores, commencing Sunday 13 September at 20:00 UTC (Sun 1pm PDT / 4pm EDT / 9pm BST / 10pm CEST, Mon 6am AEST). The aim of this maintenance is to improve system performance, reliability and security. We anticipate the maintenance will take approximately 30–45 minutes. This system backs our API and the majority of our background processing, so there will be disruption across services during the maintenance period. The Vero API will be unavailable while the upgrade is in progress. Requests made during this time will fail with a 5xx error and will not be processed, so API clients should retry any failed requests once maintenance is complete. Background processing, including event and data processing, workflows and email sending, will be paused during the upgrade and will resume and catch up once it is complete. Existing data stored in Vero will not be affected, and messages already queued before the maintenance window will be delivered once maintenance is complete.

System upgrades and maintenance

Aug <var data-var='date'>22</var>, <var data-var='time'>01:00</var> UTC Resolved - Between 01:00 22 August 2026 and 05:00 24 August 2026, customer experienced intermittent access issues when using the MCP server. This was due to a bug in an upstream vendor we use to host our server. Usage should have returned to normal from approximately 05:00 24 August 2026. If you have any remaining access issues, please email us on support@getvero.com.

Intermittent issues with MCP access

Jul <var data-var='date'>20</var>, <var data-var='time'>09:30</var> UTC Resolved - Between 09:30-10:30 UTC 20 July 2026, Vero experienced an availability incident affecting our Tracking API. During the incident some user property and event tracking API requests were not processed successfully. As a result, some data sent to Vero during the incident window may not have been successfully stored and processed. ## Root cause The incident was caused by an infrastructure issue that resulted in an interruption to normal service. Once identified, the issue was remediated and service was restored promptly. Unfortunately, our status page was not updated as it should have been at this time due to a breakdown in the process that updates the status page for this component of our system. ## Follow-up actions We are reviewing the circumstances that led to the interruption, along with our monitoring and operational procedures, to reduce the likelihood of a repeat incident. This includes reviewing our incident response process to ensure status page updates are made consistently during future incidents. We apologise for the disruption this incident caused.

Intermittent issues receiving data via Tracking API

Mar <var data-var='date'> 5</var>, <var data-var='time'>23:15</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'> 5</var>, <var data-var='time'>22:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 4</var>, <var data-var='time'>18:40</var> UTC Scheduled - We will be performing system upgrades on some of our databases, commencing Thursday 5 March at 22:00 UTC (Thu 5pm EST / 2pm PST / 10pm GMT / 11pm CET / Fri 9am AEDT) The aim of this maintenance is to improve system performance and security. There will be some disruptions across services including delays to API and email processing for approximately 30–45 minutes during the maintenance period. There will be no data loss during the downtime and all pending API requests will be processed once maintenance is complete. If you have any questions or concerns, please email us at support@getvero.com.

Nov <var data-var='date'>26</var>, <var data-var='time'>01:07</var> UTC Resolved - We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time. Nov <var data-var='date'>26</var>, <var data-var='time'>00:53</var> UTC Investigating - We're investigating minor delays in message sending and reports that certain elements of the UI (Logs, Profiles) are not loading correctly.

Delays in email sending and certain aspects of UI are not loading

Oct <var data-var='date'>21</var>, <var data-var='time'>00:01</var> UTC Resolved - RESOLVED: Our upstream provider has marked the issue resolved over an hour ago, and we have seen a resumption of normal processing and all services should now be operational. Thank you for your patience. Oct <var data-var='date'>20</var>, <var data-var='time'>22:54</var> UTC Update - We are currently processing all remaining backlogs, and performance should be back to normal for most aspects of Vero. Some workflows and newsletters may still continue to experience delays. Oct <var data-var='date'>20</var>, <var data-var='time'>19:35</var> UTC Monitoring - We are seeing infrastructure come back online and many of our backed up queues are slowly coming down. Workflows are still experiencing significant delays, as are some newsletters. We will continue to monitor the situation and update as conditions improve. Oct <var data-var='date'>20</var>, <var data-var='time'>15:56</var> UTC Investigating - We are seeing multiple delays across the application. This is due to a widespread AWS outage impacting both our services, as well as tools and services we rely on. See https://health.aws.amazon.com/health/status . Segment refreshes, workflow processing and other key Vero components are all impacted. We apologize for any inconvenience and will be continuing to monitor.

Delays and Slow Processing

Aug <var data-var='date'> 5</var>, <var data-var='time'>16:30</var> UTC Resolved - Everything is operating as normal at this time and has been for the last couple of hours. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:43</var> UTC Monitoring - We've made a fix and things are trending back to normal. We're keeping the status as "Degraded performance" for the time being but are monitoring and will mark as resolved as soon as we can. Thanks for your patience. Aug <var data-var='date'> 5</var>, <var data-var='time'>12:34</var> UTC Identified - We are experiencing delays processing API calls and downstream workflows. We know this is frustrating. We have identified the issue and are working to restore processing as soon as possible.

Delays in API and message processing

Jul <var data-var='date'>31</var>, <var data-var='time'>02:43</var> UTC Resolved - Note: we are trying a new format for our post-mortems. *What was the impact* API processing, workflows (including transactional messages and workflows) and newsletters were intermittently offline for a brief period (15:00-15:30) and then delayed for several hours between 15:00 and 23:30 UTC as we caught up processing. *What caused the impact* A datastore used by our queueing system ran out of memory. *Why'd it happen* After QA testing, we deployed a configuration change to our queueing system yesterday to improve the way processing API and workflow jobs are balanced between customers. This change led to unexpected growth in memory in our queueing system, causing it to fail. Whilst we were alerted the memory growth rate was unprecedently large. *What changes have we made* - Investigated the cause of the memory growth and patched it. - Adjusted our alerting on memory growth so we are alerted earlier to give us more time to fix this issue, in the unlikely event it occurs again. *Any other information* This particular part of our infrastructure has been frustratingly brittle over the last year or so, due to inefficient data storage. As a result we elected to migrate to a data store better-suited for these workloads (DynamoDB) at the start of 2025. That work is nearing completion. It will improve queue processing by 10x at least, giving us much-needed headroom. Questions: please email us at support@getvero.com. Jul <var data-var='date'>30</var>, <var data-var='time'>18:25</var> UTC Update - The team is continuing to monitor system stability and performance. Jul <var data-var='date'>30</var>, <var data-var='time'>15:32</var> UTC Monitoring - The team is continuing to monitor system stability and performance. Jul <var data-var='date'>30</var>, <var data-var='time'>14:57</var> UTC Identified - We are currently experiencing delays with our API and message processing systems. Our team has implemented a temporary fix and performance is improving, but you may still encounter slower response times or failed requests to Vero's Track API. Message delivery across all channels—including workflows and newsletters—is currently delayed. We're working to fully resolve these issues and will update you as soon as normal service is restored.

Jul <var data-var='date'>29</var>, <var data-var='time'>07:35</var> UTC Resolved - We are confident this issue has been completely resolved. All emails have been processing as normal since approximately 04:00 UTC 29 July. We are working with our downstream provider to review what has occurred and improve our resiliency in response to this incident. Please email us with any questions at support@getvero.com. Thanks for your patience. Jul <var data-var='date'>29</var>, <var data-var='time'>01:43</var> UTC Monitoring - Our downstream provider has resolved the issue and the system is operating as normal. We are now processing the backlog of delayed messages and will mark this issue as resolved once that is complete. Please email us with any questions via support@getvero.com. Jul <var data-var='date'>28</var>, <var data-var='time'>23:40</var> UTC Identified - At approximately 20:45 UTC, we began noticing errors in our mailer service indicating emails were not going out. Shortly afterwards, we were contacted by our upstream email delivery partner indicating they were experiencing infrastructure issues. This is now impacting **all emails** sent via Vero-managed sending domains and is a major outage. If you send via your own account with an ESP (Sendgrid, Mailjet, etc), you are **not impacted**. SMS and push messages are **not impacted**. We are in communication with our upstream partner, and they are working to restore service. While we do not yet have a definite timeline, we will update as soon we do. We are working to get this back online as quickly as possible. We apologise for the inconvenience. We understand how critical email delivery is to your business.

Vero-managed sending domain outage

May <var data-var='date'>31</var>, <var data-var='time'>00:39</var> UTC Resolved - Newsletter sending has resumed normal operations. However, we will continue to monitor through the weekend. Please reach out to support@getvero.com if you experience additional delays or have any questions. May <var data-var='date'>30</var>, <var data-var='time'>21:21</var> UTC Monitoring - We have identified the root cause of the issue and have applied a fix. We will continue monitoring throughout the day until sending returns to normal operations. May <var data-var='date'>30</var>, <var data-var='time'>20:06</var> UTC Investigating - We are experiencing significant delays with Newsletter sending. The issue began overnight, and we are taking steps to mitigate but service will take some time to return to normal. Once we are positive we have addressed the root cause of the issue, we will provide an update and monitor the issue.

Issue with Newsletter sending

May <var data-var='date'>29</var>, <var data-var='time'>19:00</var> UTC Resolved - All stats should now be caught up. We have monitored overnight and observed no additional issues. May <var data-var='date'>28</var>, <var data-var='time'>22:29</var> UTC Monitoring - This issue has been identified and patched. We are currently monitoring to ensure the issue has been fully addressed. In the meanwhile, delivery stats are being backfilled but will take some hours before they are fully accurate. May <var data-var='date'>28</var>, <var data-var='time'>09:40</var> UTC Identified - We are receiving multiple reports that the "Delivery" metric in the Vero UI and integrations via webhooks are currently under-reporting. We have identified the cause of this issue. At this time it appears it relates to reporting only: messages are still being successfully delivered. We will provide an update as soon as we have deployed a fix and are monitoring the solution. Please email support@getvero.com with any questions.

Delivery metrics under-reporting

Apr <var data-var='date'> 2</var>, <var data-var='time'>21:39</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>19</var>, <var data-var='time'>14:50</var> UTC Monitoring - We have identified an issue introduced during a recent upgrade that affected data processing for newsletters sent through Vero 2.0. On 16 March 06:26 UTC we made a change to increase the send rate of newsletters sent through Vero 2.0. Due to an issue in this deploy, some email profiles have since been incorrectly identified, leading to: 1. Missing report data for some campaigns. 2. Emails sent to previously-unsubscribed users. We’ve deployed a fix and are currently back-filling the data. From this time, unsubscribed users *are* being correctly respected. Additionally, we’re working to recover the missing reporting stats and correct any previously-impacted profiles. This process is ongoing, with full restoration expected within the next 24 hours. We’ll provide further updates as the process progresses. We understand the impact of this bug and apologise for the inconvenience caused. Please email via support@getvero.com with any questions.

Issues with Vero 2.0 Newsletter Reports and Data Availability

Aug <var data-var='date'> 6</var>, <var data-var='time'>10:26</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'> 6</var>, <var data-var='time'>09:38</var> UTC Investigating - We are currently investigating an issue in which the main Customers page is not displaying all customer data.

Vero Customers Page Inaccessible

Jul <var data-var='date'>29</var>, <var data-var='time'>21:02</var> UTC Resolved - The root cause of the issue has been identified, and an appropriate configuration change has been made. Service appears to be restored, and we are marking this issue as resolved. We will continue to monitor but do not anticipate additional issues. Please reach out to support@getvero.com with any questions or concerns. Jul <var data-var='date'>29</var>, <var data-var='time'>19:14</var> UTC Investigating - We are currently experiencing an API outage. Our platform team is investigating but has yet to identify a root cause.

API Outage

Jul <var data-var='date'>11</var>, <var data-var='time'>23:33</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>11</var>, <var data-var='time'>01:23</var> UTC Update - We have now processed 98% of the backlog and are working through the final 2%. We will leave this issue as "Monitoring" until we've fully cleared the backlog. Jul <var data-var='date'>10</var>, <var data-var='time'>22:14</var> UTC Monitoring - We have been monitoring the situation since identifying and addressing the issue earlier today. We are still working through the backlog of webhooks and will continue to monitor until we are back in real time. Jul <var data-var='date'>10</var>, <var data-var='time'>12:24</var> UTC Identified - We have identified the cause of the issue. Jul <var data-var='date'>10</var>, <var data-var='time'>07:51</var> UTC Investigating - We are currently investigating this issue.

Delays in webhook processing

Jul <var data-var='date'>10</var>, <var data-var='time'>07:30</var> UTC Resolved - The incident related to delays in webhook processing has resulted in delays to campaign reporting in Vero’s UI. No data has been lost and all reports will be backfilled.

Delays in Campaign Reporting

Jun <var data-var='date'>20</var>, <var data-var='time'>13:05</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>20</var>, <var data-var='time'>11:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>20</var>, <var data-var='time'>09:49</var> UTC Update - We are still investigating. We apologise for the delay. We will provide further updates as soon as we can. Jun <var data-var='date'>20</var>, <var data-var='time'>09:08</var> UTC Investigating - We're investigating reports of delays processing API events and triggering automated campaigns.

Delays in automated email processing

Jun <var data-var='date'>19</var>, <var data-var='time'>06:56</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>19</var>, <var data-var='time'>06:28</var> UTC Investigating - We are currently investigating this issue.

Vero UI inaccessible

Jun <var data-var='date'>11</var>, <var data-var='time'>01:41</var> UTC Resolved - We've now resolved this issue. We will reach out to the affected customers to discuss any follow-up questions. If you have any questions, please email us at support@getvero.com. Jun <var data-var='date'>10</var>, <var data-var='time'>22:30</var> UTC Identified - One of our email delivery processing clusters is experiencing delays, affecting a portion of our customers. This is impacting automated (transactional, behavioural, workflow) campaigns, resulting in significant delays. We have found the root cause and are working on a fix now.

Delays in automated campaigns

May <var data-var='date'> 2</var>, <var data-var='time'>11:00</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 2</var>, <var data-var='time'>09:10</var> UTC Monitoring - We are currently monitoring delays in newsletter sending.

Delays in newsletter sending

Apr <var data-var='date'> 1</var>, <var data-var='time'>11:30</var> UTC Resolved - At 11:17 UTC (1 April), our team was alerted to delays in automated campaign processing. At this time we marked behavioural, transactional and workflow processing as degraded. This affected all customers. By 11:54 UTC, our team had isolated the root cause: delayed filter evaluations on one of our data sources. At 12:30 UTC, processing performance had returned to normal but there was a large backlog of automated campaign jobs to work through. We continued to monitor as the backlog reduced and began work on a fix to the root cause. At 18:49 UTC, we noticed a spike in processing again. This was quickly resolved (as of 19:30). We continued to monitor the backlog. As of 21:30 UTC, the backlog has cleared and workflow processing is 100% realtime for all but handful of customers (with larger backlogs). These remaining backlogs should be fully cleared by 00:00 UTC. At 21:56 we deployed a patch for the root cause. We believe we have fixed the underlying cause and this will not occur again. We will monitor extra closely over the coming 48 hours to ensure this is the case. If you have any questions, please email support@getvero.com. Thank you. We also want to note that this incident was unrelated to the database upgrades/maintenance conducted over the weekend. These changes have gone smoothly. -- Processing has returned to normal and we can report the following metrics for the key time windows. These are the P50 to P90 reports for workflow node processing. This represents how long it takes to process a node vs. when the node was queued for evaluation. We expect a p90 of 5 minutes across all nodes. Note that this include **all node types** across all workflow types (transactional, non-transactional, etc.). For example, A node with 50 conditions looking back across a large date range will take longer to evaluate than a simple email node. 10:00 - 21:30 UTC 1 April (catching up on backlog) • p50 = 1 hour • p75 = 2.45 hours • p90 = 4.6 hours 21:30 - 00:00 UTC 1 April (tail of backlog, with majority of customers in realtime) • p50 = 48 minutes • p75 = 1.8 hours • p90 = 3.1 hours 00:00 - 01:00 UTC 2 April (backlog fully processed and processing in realtime) • p50 = 31 seconds • p75 = 3 minutes • p90 = 5.4 minutes

Delays in automated campaign processing

Apr <var data-var='date'> 1</var>, <var data-var='time'>01:12</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'> 1</var>, <var data-var='time'>00:55</var> UTC Update - We are continuing to verify the maintenance items. Apr <var data-var='date'> 1</var>, <var data-var='time'>00:41</var> UTC Verifying - Verification is currently underway for the maintenance items. Apr <var data-var='date'> 1</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>28</var>, <var data-var='time'>23:36</var> UTC Scheduled - We will be performing system upgrades on some of our databases, commencing Monday 1 April at 00:00 UTC (Sun 5pm PDT / 8pm EDT, Mon 1am BST / 2am CEST / 11am AEDT) The aim of this maintenance is to improve system performance and security. There will be some disruptions across services including delays to API and email processing for approximately 30-45 minutes during the maintenance period. There will be no data loss during the downtime and all pending API requests will be processed once maintenance is complete. If you have any questions or concerns, please email us at support@getvero.com.

Oct <var data-var='date'>28</var>, <var data-var='time'>00:19</var> UTC Resolved - We believe we have addressed the underlying configuration issues when led to last week's major service degradation. Over the past few months we've been working on some important optimizations and security patches to several of our key data stores and infrastructure. These changes were meant to be rolling changes with no production impact and many of the changes have been. Unfortunately, some of the changes we made led to unanticipated issues, causing degraded performance across the majority of Vero's services. One of the database shards on which we store and read user properties has been falling out of sync with the primary data store. Unfortunately, the services that rely on this particular data source include those that personalize email content and evaluate automated campaigns and workflows. These services will wait for eventual consistency but have a low tolerance for delays in order to deliver the speed our customers expect. This has caused periodic, significant delays. We've been able to uncover the source of these issues and have made configuration changes that have resolved the synchronization lag. We are monitoring to ensure there are no further issues. Separately, we recently made some important optimizations to our event storage to improve performance. Despite significant planning, these changes led to unexpected degredation in some of the queries related to automated email delays. Our platform team has been hard at work optimizing these queries and we've seen major improvements. Processing is back to BAU at this time. We are monitoring and are continuing to make further optimizations until we've seen the net performance improvements we're targeting. It has taken us longer than we would like to roll forward and adjust the configuration to return performance to the needed levels. We have been monitoring and have seen all services operating as expected. We will continue monitoring until we are certain we have restored the systems to their full capacity. Oct <var data-var='date'>24</var>, <var data-var='time'>00:58</var> UTC Update - We are continuing to monitor the situation and make adjustments to improve performance. We will share a post mortem when we are satisfied that the situation is resolved Oct <var data-var='date'>20</var>, <var data-var='time'>21:24</var> UTC Monitoring - We apologize for the service degradation experienced intermittently throughout this last week. These have been caused by some large, necessary infrastructure improvements we are making to our system. The primary changes have now been made and we expect to see improvements to any remaining performance issues over the next several hours. We will continue to monitor the situation over the weekend, and provide a more detailed post-mortem afterwards. Thanks for your patience. If you have any questions, please emails us via support@getvero.com.

Is Vero down?

Vero status is UP

Lastest published events

Database upgrades and maintenance

Database upgrades and maintenance

System upgrades and maintenance

Vero Services, Components and Regions

Recent Vero events

Database upgrades and maintenance

Database upgrades and maintenance

System upgrades and maintenance

Intermittent issues with MCP access

Intermittent issues receiving data via Tracking API

Database upgrades and maintenance