Is Vero down?

Last checked 2m ago
Current status
Vero is up

No incidents right now.

Official status page: http://status.getvero.com · Polled every 5 minutes · 19 components tracked

Vero is operational right now. Last checked 2m ago; the most recent incident resolved 2d ago.

Real-time Vero status, recent outages, and incident history — pulled directly from Vero's official status page at http://status.getvero.com every 5 minutes. Pingoru tracks 19 Vero services and has captured 3 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Vero reports a new incident — free for 5 monitors, no credit card.

Users who monitor Vero also follow these Email services: SendGrid Calendly SparkPost Exclaimer Mailjet Front sendwithus Proton Mail Virtru mailprotector View all 6,000+ providers
Vero uptime 100.00% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Aug 24, 2026, 08:12 AM UTC · Resolved Aug 22, 2026, 01:00 AM UTC
    Timeline · 1 update
    • resolved · Aug 24, 2026, 08:12 AM UTC

      Between 01:00 22 August 2026 and 05:00 24 August 2026, customer experienced intermittent access issues when using the MCP server. This was due to a bug in an upstream vendor we use to host our server. Usage should have returned to normal from approximately 05:00 24 August 2026. If you have any remaining access issues, please email us on [email protected].

    Latest: Between 01:00 22 August 2026 and 05:00 24 August 2026, customer experienced intermittent access issues when using the MCP server. This was due to a bug in an upstream vendor we use…

  2. Resolved
    Started Jul 21, 2026, 08:18 AM UTC · Resolved Jul 20, 2026, 09:30 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 w…

Outage history

Past 90 days · 2 incidents View full outage history →