Vero Outage History
7 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Vero Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 4, 2026 | Database upgrades and maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 27, 2026 | Database upgrades and maintenanceWe've postponed today's scheduled maintenance. No action is needed on your end, and we'll announce the new maintenance window later this week. | 2h 0m | Scheduled |
| Sep 13, 2026 | System upgrades and maintenanceAll 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… | 45 min | Scheduled |
| Aug 24, 2026 | Intermittent issues with MCP accessBetween 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… | -3312 min | Resolved |
| Jul 21, 2026 | Intermittent issues receiving data via Tracking APIBetween 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… | -1368 min | Resolved |
| Mar 5, 2026 | Database upgrades and maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 26, 2025 | Delays in email sending and certain aspects of UI are not loadingWe have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time. | 13 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Vero incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Vero Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Vero acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Vero outage in this window ran 2h, against a mean recovery of 1h 12m. If you depend on Vero in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.