All Systems Operational
API ? Operational
Email Processing Operational
Transactional emails Operational
Behavioral emails Operational
Newsletter emails Operational
Web Interface Operational
Email reports and statistics ? Operational
Activity logs ? Operational
Backend Processing Operational
Imports and Exports ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
API Response Times
Fetching
Past Incidents
Jan 17, 2017

No incidents reported today.

Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017
Between 1am UTC and 3am UTC on 11 January, we experienced a small scale outage at Vero.

Thanks to our automated systems, our Operations team identified the issue immediately and promptly began work on a resolution.

In the last month we have added new caching stores to support our continued growth. This outage was a result of one of the critical servers in this cluster becoming unavailable. In the event of such an outage, the server should automatically fail over to a secondary instance. Our investigation has shown that this did not occur and we are currently working with our upstream provider to determine why.

There was no data loss during this time, as this was only part of our caching layer.

We can confirm that during this time only a subset of API and email processing saw delays. Once back online, it took around 30 minutes for us to process the subset of delays remaining.

We will continue to monitor this closely for the next 24 hours.

If you have any questions, please send us an email via support@getvero.com. Have a great day wherever you are 🌏!

The Vero Infrastructure Team
Jan 12, 15:12 AEDT
Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017

No incidents reported.

Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.

Jan 6, 2017

No incidents reported.

Jan 5, 2017

No incidents reported.

Jan 4, 2017

No incidents reported.

Jan 3, 2017

No incidents reported.