Home
/
Status
/
Service
Multi-channel customer engagement platform for personalized messaging and A/B testing.
Source
auto
Category
Communication
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 9m ago
20
Components
0
Active incidents
0
Maintenance
66.67%
90d uptime
Delays in email sending and certain aspects of UI are not loading
Nov 26, 12:53 AM
Normalized official status-page data for incidents, maintenance, components, and history.
66.67%
Known uptime
3 known history days
20
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
27
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Vero 2.0: Imports
Operational
Behavioral emails
Operational
CSV Imports and Exports
Operational
General UI access and speed
Operational
Logs page activity
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
2
operational days
0
degraded days
1
outage days
0
maintenance days
87
unknown days
Latest outages and degradations detected from the official status page.
We have confirmed the source of the issue and deployed a fix. This issue is now fully resolved and all message are real time.
RESOLVED: Our upstream provider has marked the issue resolved over an hour ago, and we have seen a resumption of normal processing and all services should now be operational. Thank you for your patience.
Everything is operating as normal at this time and has been for the last couple of hours.
Note: we are trying a new format for our post-mortems. *What was the impact* API processing, workflows (including transactional messages and workflows) and newsletters were intermittently offline for a brief period (15:00-15:30) and then delayed for several hours between 15:00 and 23:30 UTC as we caught up processing. *What caused the impact* A datastore used by our queueing system ran out of memory. *Why'd it happen* After QA testing, we deployed a configuration change to our queueing system yesterday to improve the way processing API and workflow jobs are balanced between customers. This change led to unexpected growth in memory in our queueing system, causing it to fail. Whilst we were alerted the memory growth rate was unprecedently large. *What changes have we made* - Investigated the cause of the memory growth and patched it. - Adjusted our alerting on memory growth so we are alerted earlier to give us more time to fix this issue, in the unlikely event it occurs again. *Any other information* This particular part of our infrastructure has been frustratingly brittle over the last year or so, due to inefficient data storage. As a result we elected to migrate to a data store better-suited for these workloads (DynamoDB) at the start of 2025. That work is nearing completion. It will improve queue processing by 10x at least, giving us much-needed headroom. Questions: please email us at support@getvero.com.
We are confident this issue has been completely resolved. All emails have been processing as normal since approximately 04:00 UTC 29 July. We are working with our downstream provider to review what has occurred and improve our resiliency in response to this incident. Please email us with any questions at support@getvero.com. Thanks for your patience.
On Friday, May 30, customers experienced significant delays in the delivery of one-to-many newsletter campaigns. We know how critical timely delivery is and are providing a post mortem. **What happened** Between 0700 30 May - 0130 31 May UTC, scheduled newsletter campaigns were delayed due to a combination of factors: 1. **Downstream service disruption**. A configuration issue at one of our external partners impacted message throughput. 2. **Authentication issues.** A component of our infrastructure experienced a disruption related to service authentication with another internal service, which contributed to the backlog. These issues together resulted in prolonged delivery times for a subset of campaign traffic. **Resolution** We worked with our external partner to address the configuration issue and restored full functionality to the affected internal service. Message queues were cleared and delivery returned to normal by 0130 31 May. **Preventative and detective measures** To improve reliability and reduce risk going forward, we are: * Enhancing proactive monitoring and alerting for system-level authentication and connectivity health. * with our third-party partner to strengthen deployment safeguards. -- We’re committed to ensuring the dependability of your campaigns. While this incident was complex and multi-faceted, we take full responsibility and apologise for the inconvenience. Thank you for your trust and patience. Please email us at [support@getvero.com](mailto:support@getvero.com) if you have any questions.
All stats should now be caught up. We have monitored overnight and observed no additional issues.
This incident has been resolved.
This incident has been resolved.
The root cause of the issue has been identified, and an appropriate configuration change has been made. Service appears to be restored, and we are marking this issue as resolved. We will continue to monitor but do not anticipate additional issues. Please reach out to support@getvero.com with any questions or concerns.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed successfully. All Vero Connect users will need to login once again. If you have an existing session with Vero Connect, please refresh your browser window to be redirected to the login page. Thank you, and Happy Holidays from the team at Vero!
The scheduled maintenance has been completed.
Due to circumstances beyond our control we were unable to proceed with our scheduled maintenance as intended. We intend to reschedule the planned maintenance program to the next available opportunity and will advise when we have more details. Thank you and hope you enjoy the rest of the weekend!
This scheduled maintenance incident is now complete and confirming that all services are processing again in real-time. Although the maintenance operations were completed some time ago we subsequently experienced a performance degradation which intermittently affected our processing and caused delays to email campaigns including transactional, behavioural and workflow emails - however we were able to take immediate steps to mitigate the issue and have since been able to fully resolve it. If you have any questions please email us at support@getvero.com - thanks again and have a great weekend!
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Vero status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.getvero.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 20 of 20 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Vero 1.0: UI Web UI feature availability and access to Vero Workflows. | Operational | Group | Not recorded |
Vero 1.0: Automated email processing Records whether Workflows and (legacy) Transactional and Behavioral campaigns are sending in the Vero Workflows product without issue and sending at anticipated speeds. | Operational | Group | Not recorded |
Vero 1.0: Reports data availability Records whether Delivered, Opened and Clicked statistics for email reports on the Campaigns index and Reports pages of the Vero Workflows product are being updated without delay. | Operational | Group | Not recorded |
General UI access and speed Records whether the web UI is generally available and loading at typical speeds. | Operational | Component | Not recorded |
Reports data availability (Vero default and Mailgun integrations) Records whether Delivered, Opened and Clicked statistics for email reports on the Campaigns index and Reports pages are being updated without delay. | Operational | Component | Not recorded |
Vero 1.0: Ingestion API API used to send data to Vero Workflows via https://api.getvero.com | Operational | Component | Not recorded |
Logs page activity Records whether the Logs page is being updated in realtime. | Operational | Component | Not recorded |
Reports data availability (Sendgrid and other non-Mailgun integrations) Records whether Delivered, Opened and Clicked statistics for email reports on the Campaigns index and Reports pages are being updated without delay. | Operational | Component | Not recorded |
Transactional emails | Operational | Component | Not recorded |
CSV Imports and Exports Records whether there are delays for CSV imports or CSV exports initiated via the Vero UI. | Operational | Component | Not recorded |
Vero 1.0: Segment calculation Records whether Segments are calculating in the Vero Workflows product at typical speeds. | Operational | Component | Not recorded |
Vero 1.0: Newsletter processing Records whether Newsletter campaigns are sending in Vero Workflows without issue and without delay. | Operational | Component | Not recorded |
Workflows | Operational | Component | Not recorded |
Behavioral emails | Operational | Component | Not recorded |
Vero 2.0: UI Web UI feature availability and access to Vero Newsletters. | Operational | Component | Not recorded |
Vero 2.0: Imports Records whether campaigns in Vero Connect are importing data. | Operational | Component | 6/19/2026 |
Vero 2.0: Newsletter processing Records whether Newsletter campaigns are sending in Vero Newsletters without issue and without delay. | Operational | Component | Not recorded |
Vero 2.0: Reports data availability Records whether Delivered, Opened and Clicked statistics for email reports on the Campaigns index and Reports pages of the Vero 2.0 product are being updated without delay. | Operational | Component | Not recorded |
Outgoing webhooks Webhooks emitted from Vero for sent, delivered, opened, clicked and other events. Covers both products. | Operational | Component | Not recorded |
Open and Click Tracking Service which re-writes links, handles incoming links, and tracks opens and clicks for Vero managed sending. | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Vero is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
