Vero Outage History
Vero degraded View live status →Pingoru has recorded 55 incidents for Vero: 3 in the last 12 months and 1 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 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 517 (0%) |
Incidents, newest first
Notice August 22, 2026 Intermittent issues with MCP access –
Started Aug 22, 2026, 01:00 AM UTC· resolved Aug 22, 2026, 01:00 AM UTC
- resolved Aug 24, 2026, 08:12 AM UTC
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].
Notice July 20, 2026 Intermittent issues receiving data via Tracking API 1h
Started Jul 20, 2026, 09:30 AM UTC· resolved Jul 20, 2026, 10:30 AM UTC
- resolved Jul 21, 2026, 08:18 AM UTC
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.
Minor November 26, 2025 Delays in email sending and certain aspects of UI are not loading 13m Transactional emails, Logs page activity, Vero 1.0: Newsletter processing, Workflows and 4 more
Started Nov 26, 2025, 12:53 AM UTC· resolved Nov 26, 2025, 01:07 AM UTC
- 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.
Major October 20, 2025 Delays and Slow Processing 8h 5m Vero 1.0: Ingestion API, Transactional emails, Vero 1.0: Segment calculation, Vero 1.0: Newsletter processing and 5 more
Started Oct 20, 2025, 03:56 PM UTC· resolved Oct 21, 2025, 12:01 AM UTC
- 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.
Minor August 5, 2025 Delays in API and message processing 3h 56m Vero 1.0: Ingestion API, Transactional emails, Logs page activity, Workflows and 1 more
Started Aug 05, 2025, 12:34 PM UTC· resolved Aug 05, 2025, 04:30 PM UTC
- 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.
Critical July 28, 2025 Vero-managed sending domain outage 7h 54m Transactional emails, Vero 1.0: Newsletter processing, Workflows, Behavioral emails and 1 more
Started Jul 28, 2025, 11:40 PM UTC· resolved Jul 29, 2025, 07:35 AM UTC
- 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.
Major May 30, 2025 Issue with Newsletter sending 4h 32m Vero 1.0: Newsletter processing, Vero 2.0: Imports, Vero 2.0: Newsletter processing
Started May 30, 2025, 08:06 PM UTC· resolved May 31, 2025, 12:39 AM UTC
- investigating May 30, 2025, 08:06 PM UTC
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.
- monitoring May 30, 2025, 09:21 PM UTC
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.
- resolved May 31, 2025, 12:39 AM UTC
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.
- postmortem Jun 02, 2025, 05:58 AM UTC
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.
Minor May 28, 2025 Delivery metrics under-reporting 1d 9h Reports data availability (Vero default and Mailgun integrations), Vero 2.0: Reports data availability
Started May 28, 2025, 09:40 AM UTC· resolved May 29, 2025, 07:00 PM UTC
- 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.
Minor March 19, 2025 Issues with Vero 2.0 Newsletter Reports and Data Availability 14d 6h Vero 2.0: Reports data availability
Started Mar 19, 2025, 02:50 PM UTC· resolved Apr 02, 2025, 09:39 PM UTC
- 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.