Vero incident

Intermittent issues receiving data via Tracking API

Resolved after 1 hour, on July 20, 2026.

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.

Started
Jul 20, 2026, 09:30 AM UTC
Resolved
Jul 20, 2026, 10:30 AM UTC
Duration
1h
Detected by Pingoru
Jul 20, 2026, 09:30 AM UTC

Update timeline

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

Your product runs on more than Vero

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →