Vero Status Page

Jul 20, 2026 · resolved Jul 20

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.

Nov 26, 2025 · resolved Nov 26

We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time.

Oct 20, 2025 · resolved Oct 21

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.

Aug 5, 2025 · resolved Aug 5

Everything is operating as normal at this time and has been for the last couple of hours.

Jul 30, 2025 · resolved Jul 31

Note: we are trying a new format for our post-mortems. *What was the impact* API processing, workflows (including transactional messages and workflows) and newsletters were intermittently offline for a brief period (15:00-15:30) and then delayed for several hours between 15:00 and 23:30 UTC as we caught up processing. *What caused the impact* A datastore used by our queueing system ran out of memory. *Why'd it happen* After QA testing, we deployed a configuration change to our queueing system yesterday to improve the way processing API and workflow jobs are balanced between customers. This change led to unexpected growth in memory in our queueing system, causing it to fail. Whilst we were alerted the memory growth rate was unprecedently large. *What changes have we made* - Investigated the cause of the memory growth and patched it. - Adjusted our alerting on memory growth so we are alerted earlier to give us more time to fix this issue, in the unlikely event it occurs again. *Any other information* This particular part of our infrastructure has been frustratingly brittle over the last year or so, due to inefficient data storage. As a result we elected to migrate to a data store better-suited for these workloads (DynamoDB) at the start of 2025. That work is nearing completion. It will improve queue processing by 10x at least, giving us much-needed headroom. Questions: please email us at support@getvero.com.

Is Vero down right now?

Yes — Vero is reporting a minor incident as of Aug 19, 10:43 PM UTC.

What is Vero's current status?

Vero: Partially Degraded Service. Alert24 checks Vero's status page continuously and can notify you the moment it changes.

How do I get alerted when Vero goes down?

Alert24 monitors Vero and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.