All Systems Operational

Uptime over the past 90 days. View historical uptime.
Vero 1.0: Ingestion API Operational
90 days ago
100.0 % uptime
Today
Vero 1.0: UI Operational
General UI access and speed Operational
Logs page activity Operational
CSV Imports and Exports Operational
Vero 1.0: Segment calculation Operational
90 days ago
100.0 % uptime
Today
Vero 1.0: Newsletter processing Operational
90 days ago
99.81 % uptime
Today
Vero 1.0: Automated email processing Operational
90 days ago
100.0 % uptime
Today
Transactional emails Operational
90 days ago
100.0 % uptime
Today
Workflows Operational
90 days ago
100.0 % uptime
Today
Behavioral emails Operational
90 days ago
100.0 % uptime
Today
Vero 1.0: Reports data availability Operational
Reports data availability (Vero default and Mailgun integrations) Operational
Reports data availability (Sendgrid and other non-Mailgun integrations) Operational
Vero 2.0: UI Operational
90 days ago
100.0 % uptime
Today
Vero 2.0: Imports Operational
90 days ago
99.68 % uptime
Today
Vero 2.0: Newsletter processing Operational
90 days ago
99.81 % uptime
Today
Vero 2.0: Reports data availability Operational
90 days ago
100.0 % uptime
Today
Outgoing webhooks Operational
90 days ago
100.0 % uptime
Today
Open and Click Tracking Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jul 24, 2026

No incidents reported today.

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

No incidents reported.

Jul 20, 2026
Intermittent issues receiving data via Tracking API
Resolved - 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.
Jul 20, 09:30 UTC
Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

No incidents reported.

Jul 15, 2026

No incidents reported.

Jul 14, 2026

No incidents reported.

Jul 13, 2026

No incidents reported.

Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage