Vero experienced a major incident on October 20, 2025 affecting Vero 1.0: Ingestion API and Transactional emails and 1 more component, lasting 8h 5m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.