Vero logo

Is Vero Down?

CommunicationLive status, outages, and incident history

No. Vero is up right now.

Every monitored Vero system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Vero breaks

Vero is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Vero status page
How we know: the official Vero status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Vero Component Status

The main Vero systems on this page. All 19 are operational right now.

19operational
Campaigns API
Operational
MCP Server
Operational
Open and Click Tracking
Operational

16 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Outgoing webhooks, Vero 1.0: Automated email processing » Behavioral emails, Vero 1.0: Automated email processing » Transactional emails, Vero 1.0: Automated email processing » Workflows, Vero 1.0: Ingestion API, Vero 1.0: Newsletter processing, Vero 1.0: Reports data availability » Reports data availability, Vero 1.0: Segment calculation, Vero 1.0: UI » CSV Imports and Exports, Vero 1.0: UI » General UI access and speed, Vero 1.0: UI » Logs page activity, Vero 2.0: Imports, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Vero Outages & Incidents

Incident history from the official Vero status page, including resolution updates.

Database upgrades and maintenanceScheduled for Sep 27, 2026 · 2h 0mScheduled

We will be performing a version upgrade on one of our core data stores, commencing Sunday 27 September at 20:00 UTC (Sun 1pm PDT / 4pm EDT / 9pm BST / 10pm CEST, Mon 28 September 6am AEST). The aim of this maintenance is to improve system performance, reliability and security. We expect the maintenance to be completed within one hour, but depending on how long the data migration takes, it could take up to two hours. This system is used for message delivery, so email, push and SMS sending, as well as webhooks, will be paused during the maintenance period. Once the upgrade is complete, delivery will resume and catch up. All other services, including the Vero API, event and data processing will continue to operate as normal. Existing data stored in Vero will not be affected. Messages queued before or during the maintenance window will not be lost and will be delivered once maintenance is complete.

System upgrades and maintenanceScheduled for Sep 13, 2026 · 45 minScheduled

All maintenance tasks have been completed. Our API and background processing infrastructure is functioning normally. There is still a small backlog of tasks from the maintenance period which should processed within the next 30 minutes. --- [2026-09-13T20:48:36.792Z] (verifying) Our API is now accepting requests successfully. We're still working to bring back our background processing infrastructure, so there will be a delay in processing the API data (profile updates, event tracking, etc) as well as message delivery. --- [2026-09-13T20:32:28.259Z] (verifying) The data store has been upgraded. We're now working to bring back all impacted services. --- [2026-09-13T20:01:58.221Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-13T19:00:07.467Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-11T04:00:29.803Z] (scheduled) We will be performing a version upgrade on one of our core data stores, commencing Sunday 13 September at 20:00 UTC (Sun 1pm PDT / 4pm EDT / 9pm BST / 10pm CEST, Mon 6am AEST). The aim of this maintenance is to improve system performance, reliability and security. We anticipate the maintenance will take approximately 30–45 minutes. This system backs our API and the majority of our background processing, so there will be disruption across services during the maintenance period. The Vero API will be unavailable while the upgrade is in progress. Requests made during this time will fail with a 5xx error and will not be processed, so API clients should retry any failed requests once maintenance is complete. Background processing, including event and data processing, workflows and email sending, will be paused during the upgrade and will resume and catch up once it is complete. Existing data stored in Vero will not be affected, and messages already queued before the maintenance window will be delivered once maintenance is complete.

Intermittent issues with MCP accessResolved Aug 24, 2026 · -3312 minResolved

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 support@getvero.com.

Vero Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Vero incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 12 days with incidentsSep 25

Live Vero Outage Reports

Problems reported by engineers using Vero. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Vero problems reported yet.

Something wrong with Vero on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Vero

Vero publishes a public status page at status.getvero.com covering 20 components, including Vero 1.0: Ingestion API, General UI access and speed and Transactional emails. PulsAPI tracks Vero outages, degraded performance and incident history in real time, alongside the rest of your communications stack.

Over the past 30 days, PulsAPI has measured Vero uptime at 100.00%. Response times, incident history, and SLA tracking for Vero are available on the PulsAPI dashboard.

Vero Status FAQ

Is Vero down right now?

The verdict at the top of this page comes from the latest poll of the official Vero status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Vero is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Vero recovers.

How do I check Vero uptime history?

PulsAPI tracks Vero uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Vero changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Vero outages?

PulsAPI reads the official Vero status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Vero components?

Yes. PulsAPI monitors 19 individual Vero components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Vero goes down?

Yes. Create a free account and subscribe to Vero: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Vero to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Vero problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Vero?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Vero plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Vero with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services