Histórico de interrupções do Vero

1. 24 Eost 2026 da 08:12 UTCresolved

   Entre 01:00 22 de agosto de 2026 e 05:00 24 de agosto de 2026, o cliente teve problemas de acesso intermitentes ao usar o servidor MCP. Isso foi devido a um bug em um fornecedor upstream que usamos para hospedar nosso servidor. O uso deve ter voltado ao normal a partir de aproximadamente 05:00 24 agosto 2026. Se tiver quaisquer problemas de acesso restantes, envie-nos um e-mail para [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 08:18 UTCresolved

   Entre 09:30-10:30 UTC 20 de julho de 2026, a Vero teve um incidente de disponibilidade afetando nossa API de rastreamento. Durante o incidente algumas propriedades do usuário e pedidos de API de rastreamento de eventos não foram processados com sucesso. Como resultado, alguns dados enviados para Vero durante a janela incidente podem não ter sido armazenados e processados com sucesso. # # Causa raiz O incidente foi causado por uma questão de infraestrutura que resultou em uma interrupção do serviço normal. Uma vez identificada, a questão foi remediada e o serviço foi restaurado prontamente. Infelizmente, nossa página de status não foi atualizada como deveria ter sido neste momento devido a uma falha no processo que atualiza a página de status para este componente do nosso sistema. # # Acções de acompanhamento Estamos a rever as circunstâncias que levaram à interrupção, juntamente com o nosso acompanhamento e procedimentos operacionais, para reduzir a probabilidade de um incidente repetido. Isso inclui revisar nosso processo de resposta a incidentes para garantir que as atualizações da página de status sejam feitas de forma consistente durante futuros incidentes. Pedimos desculpa pela perturbação que este incidente causou.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Du 2025 da 00:53 UTCinvestigating

   We're investigating minor delays in message sending and reports that certain elements of the UI (Logs, Profiles) are not loading correctly.

2. 26 Du 2025 da 01:07 UTCresolved

   We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time.

1. 20 Here 2025 da 15:56 UTCinvestigating

   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.

2. 20 Here 2025 da 19:35 UTCmonitoring

   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.

3. 20 Here 2025 da 22:54 UTCmonitoring

   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.

4. 21 Here 2025 da 00:01 UTCresolved

   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.

1. 5 Eost 2025 da 12:34 UTCidentified

   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.

2. 5 Eost 2025 da 13:43 UTCmonitoring

   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.

3. 5 Eost 2025 da 23:05 UTCresolved

   Everything is operating as normal at this time and has been for the last couple of hours.

1. 30 Gouere 2025 da 14:57 UTCidentified

   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.

2. 30 Gouere 2025 da 18:25 UTCmonitoring

   The team is continuing to monitor system stability and performance.

3. 31 Gouere 2025 da 02:43 UTCresolved

   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 [email protected].

1. 28 Gouere 2025 da 23:40 UTCidentified

   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.

2. 29 Gouere 2025 da 01:43 UTCmonitoring

   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 [email protected].

3. 29 Gouere 2025 da 07:35 UTCresolved

   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 [email protected]. Thanks for your patience.

1. 30 Mae 2025 da 20:06 UTCinvestigating

   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.

2. 30 Mae 2025 da 21:21 UTCmonitoring

   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.

3. 31 Mae 2025 da 00:39 UTCresolved

   Newsletter sending has resumed normal operations. However, we will continue to monitor through the weekend. Please reach out to [email protected] if you experience additional delays or have any questions.

4. 2 Mezheven 2025 da 05:58 UTCpostmortem

   On Friday, May 30, customers experienced significant delays in the delivery of one-to-many newsletter campaigns. We know how critical timely delivery is and are providing a post mortem. **What happened** Between 0700 30 May - 0130 31 May UTC, scheduled newsletter campaigns were delayed due to a combination of factors: 1. **Downstream service disruption**. A configuration issue at one of our external partners impacted message throughput. 2. **Authentication issues.** A component of our infrastructure experienced a disruption related to service authentication with another internal service, which contributed to the backlog. These issues together resulted in prolonged delivery times for a subset of campaign traffic. **Resolution** We worked with our external partner to address the configuration issue and restored full functionality to the affected internal service. Message queues were cleared and delivery returned to normal by 0130 31 May. **Preventative and detective measures** To improve reliability and reduce risk going forward, we are: * Enhancing proactive monitoring and alerting for system-level authentication and connectivity health. * with our third-party partner to strengthen deployment safeguards. -- We’re committed to ensuring the dependability of your campaigns. While this incident was complex and multi-faceted, we take full responsibility and apologise for the inconvenience. Thank you for your trust and patience. Please email us at [[email protected]](mailto:[email protected]) if you have any questions.

1. 28 Mae 2025 da 09:40 UTCidentified

   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 [email protected] with any questions.

2. 28 Mae 2025 da 22:29 UTCmonitoring

   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.

3. 29 Mae 2025 da 19:00 UTCresolved

   All stats should now be caught up. We have monitored overnight and observed no additional issues.

1. 19 Meurzh 2025 da 14:50 UTCmonitoring

   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 [email protected] with any questions.

2. 2 Ebrel 2025 da 21:39 UTCresolved

   This incident has been resolved.

1. 6 Eost 2024 da 09:38 UTCinvestigating

   We are currently investigating an issue in which the main Customers page is not displaying all customer data.

2. 6 Eost 2024 da 10:26 UTCresolved

   This incident has been resolved.

1. 29 Gouere 2024 da 19:14 UTCinvestigating

   We are currently experiencing an API outage. Our platform team is investigating but has yet to identify a root cause.

2. 29 Gouere 2024 da 21:02 UTCresolved

   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 [email protected] with any questions or concerns.

1. 10 Gouere 2024 da 07:51 UTCinvestigating

   We are currently investigating this issue.

2. 10 Gouere 2024 da 12:24 UTCidentified

   We have identified the cause of the issue.

3. 10 Gouere 2024 da 22:14 UTCmonitoring

   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.

4. 11 Gouere 2024 da 01:23 UTCmonitoring

   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.

5. 11 Gouere 2024 da 23:33 UTCresolved

   This incident has been resolved.

1. 11 Gouere 2024 da 07:34 UTCresolved

   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.

1. 20 Mezheven 2024 da 09:08 UTCinvestigating

   We're investigating reports of delays processing API events and triggering automated campaigns.

2. 20 Mezheven 2024 da 09:49 UTCinvestigating

   We are still investigating. We apologise for the delay. We will provide further updates as soon as we can.

3. 20 Mezheven 2024 da 11:43 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 20 Mezheven 2024 da 13:05 UTCresolved

   This incident has been resolved.

1. 19 Mezheven 2024 da 06:28 UTCinvestigating

   We are currently investigating this issue.

2. 19 Mezheven 2024 da 06:56 UTCresolved

   This incident has been resolved.

1. 10 Mezheven 2024 da 23:30 UTCidentified

   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.

2. 11 Mezheven 2024 da 01:41 UTCresolved

   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 [email protected].

1. 2 Mae 2024 da 09:10 UTCmonitoring

   We are currently monitoring delays in newsletter sending.

2. 2 Mae 2024 da 11:20 UTCresolved

   This incident has been resolved.

1. 2 Ebrel 2024 da 00:21 UTCresolved

   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 [email protected]. 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

1. 20 Here 2023 da 21:24 UTCmonitoring

   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 [email protected].

2. 24 Here 2023 da 00:58 UTCmonitoring

   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

3. 28 Here 2023 da 00:19 UTCresolved

   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.