Vero Outage History
Vero is up right nowVero had 10 outages in the last 2 years totaling 403h 27m of downtime — averaging 0.4 incidents per month.
There were 10 Vero outages since July 29, 2024 totaling 403h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.
Delays in email sending and certain aspects of UI are not loading
Affected: Transactional emailsLogs page activityVero 1.0: Newsletter processingWorkflowsBehavioral emailsVero 2.0: UIVero 2.0: Newsletter processingOutgoing webhooks
Timeline · 2 updates
- investigating Nov 26, 2025, 12:53 AM UTC
We're investigating minor delays in message sending and reports that certain elements of the UI (Logs, Profiles) are not loading correctly.
- resolved Nov 26, 2025, 01:07 AM UTC
We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time.
Delays and Slow Processing
Affected: Vero 1.0: Ingestion APITransactional emailsVero 1.0: Segment calculationVero 1.0: Newsletter processingWorkflowsBehavioral emailsVero 2.0: ImportsVero 2.0: Newsletter processingVero 2.0: Reports data availability
Timeline · 4 updates
- investigating Oct 20, 2025, 03:56 PM UTC
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.
- monitoring Oct 20, 2025, 07:35 PM UTC
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.
- monitoring Oct 20, 2025, 10:54 PM UTC
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 Oct 21, 2025, 12:01 AM UTC
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.
Delays in API and message processing
Affected: Vero 1.0: Ingestion APITransactional emailsLogs page activityWorkflowsBehavioral emails
Timeline · 3 updates
- identified Aug 05, 2025, 12:34 PM UTC
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.
- monitoring Aug 05, 2025, 01:43 PM UTC
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.
- resolved Aug 05, 2025, 11:05 PM UTC
Everything is operating as normal at this time and has been for the last couple of hours.
Vero-managed sending domain outage
Affected: Transactional emailsVero 1.0: Newsletter processingWorkflowsBehavioral emailsVero 2.0: Newsletter processing
Timeline · 3 updates
- identified Jul 28, 2025, 11:40 PM UTC
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.
- monitoring Jul 29, 2025, 01:43 AM UTC
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].
- resolved Jul 29, 2025, 07:35 AM UTC
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.
Issue with Newsletter sending
Affected: Vero 1.0: Newsletter processingVero 2.0: ImportsVero 2.0: Newsletter processing
Timeline · 4 updates
Delivery metrics under-reporting
Affected: Reports data availability (Vero default and Mailgun integrations)Vero 2.0: Reports data availability
Timeline · 3 updates
- identified May 28, 2025, 09:40 AM UTC
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.
- monitoring May 28, 2025, 10:29 PM UTC
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.
- resolved May 29, 2025, 07:00 PM UTC
All stats should now be caught up. We have monitored overnight and observed no additional issues.
Issues with Vero 2.0 Newsletter Reports and Data Availability
Affected: Vero 2.0: Reports data availability
Timeline · 2 updates
- monitoring Mar 19, 2025, 02:50 PM UTC
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.
- resolved Apr 02, 2025, 09:39 PM UTC
This incident has been resolved.
Vero Customers Page Inaccessible
Timeline · 2 updates
- investigating Aug 06, 2024, 09:38 AM UTC
We are currently investigating an issue in which the main Customers page is not displaying all customer data.
- resolved Aug 06, 2024, 10:26 AM UTC
This incident has been resolved.
API Outage
Affected: Vero 1.0: Ingestion APIReports data availability (Vero default and Mailgun integrations)Logs page activityReports data availability (Sendgrid and other non-Mailgun integrations)Vero 2.0: Reports data availability
Timeline · 2 updates
- investigating Jul 29, 2024, 07:14 PM UTC
We are currently experiencing an API outage. Our platform team is investigating but has yet to identify a root cause.
- resolved Jul 29, 2024, 09:02 PM UTC
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.