Vero had 9 outages in the last 2 years totaling 400h 50m of downtime — averaging 0.4 incidents per month.
There were 9 Vero outages since March 19, 2025 totaling 400h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 [email protected].
We're investigating minor delays in message sending and reports that certain elements of the UI (Logs, Profiles) are not loading correctly.
We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time.
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.
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.
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.
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.
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.
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.
Everything is operating as normal at this time and has been for the last couple of hours.
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.
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].
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.
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.
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.
All stats should now be caught up. We have monitored overnight and observed no additional issues.
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.
This incident has been resolved.