Vero Outage History

Vero is up right now

Vero had 6 outages in the last 2 years totaling 58h 2m of downtime — averaging 0.2 incidents per month.

There were 6 Vero outages since May 28, 2025 totaling 58h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.getvero.com

Minor November 26, 2025

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

Detected by Pingoru
Nov 26, 2025, 12:53 AM UTC
Resolved
Nov 26, 2025, 01:07 AM UTC
Duration
13m
Affected: Transactional emailsLogs page activityVero 1.0: Newsletter processingWorkflowsBehavioral emailsVero 2.0: UIVero 2.0: Newsletter processingOutgoing webhooks
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major October 20, 2025

Delays and Slow Processing

Detected by Pingoru
Oct 20, 2025, 03:56 PM UTC
Resolved
Oct 21, 2025, 12:01 AM UTC
Duration
8h 5m
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
  1. 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.

  2. 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.

  3. 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.

  4. 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.

Read the full incident report →

Minor August 5, 2025

Delays in API and message processing

Detected by Pingoru
Aug 05, 2025, 12:34 PM UTC
Resolved
Aug 05, 2025, 04:30 PM UTC
Duration
3h 56m
Affected: Vero 1.0: Ingestion APITransactional emailsLogs page activityWorkflowsBehavioral emails
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Critical July 28, 2025

Vero-managed sending domain outage

Detected by Pingoru
Jul 28, 2025, 11:40 PM UTC
Resolved
Jul 29, 2025, 07:35 AM UTC
Duration
7h 54m
Affected: Transactional emailsVero 1.0: Newsletter processingWorkflowsBehavioral emailsVero 2.0: Newsletter processing
Timeline · 3 updates
  1. 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.

  2. 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].

  3. 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.

Read the full incident report →

Minor May 28, 2025

Delivery metrics under-reporting

Detected by Pingoru
May 28, 2025, 09:40 AM UTC
Resolved
May 29, 2025, 07:00 PM UTC
Duration
1d 9h
Affected: Reports data availability (Vero default and Mailgun integrations)Vero 2.0: Reports data availability
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved May 29, 2025, 07:00 PM UTC

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

Read the full incident report →