Previous incidents

API response times and error rates have been back to normal since 13:50 UTC. Delayed webhook deliveries are being processed. This incident is resolved.

Our authentication provider has deployed a fix, and we are seeing login sessions being created normally again. Dashboard access has recovered, and we are marking this incident as resolved.

We will continue to monitor the service for any further issues.

The incident has been resolved and all services are operating normally.

As part of the recovery process, a database restart was performed. During this step, some clients may have experienced a brief interruption in service. The platform has since recovered and is operating normally.

Our team will continue to review the incident and will publish a detailed post-incident summary, including the root cause and any follow-up actions, once the investigation is complete.

The issue affecting JPY currency rates has been resolved. Web checkout and CMS functionality for JPY transactions are now operating normally.

We have verified that services are functioning as expected and will continue to monitor the system to ensure ongoing stability.

We apologize for any inconvenience this may have caused and appreciate your patience.

What happened

On 30 June 2026, between 5:26 PM and 5:34 PM UTC, the platform experienced
elevated latency and a number of failed requests over an approximately
eight-minute window. The issue began during planned database maintenance and
was fully resolved by 5:34 PM UTC. No customer data was lost or corrupted.

What caused it

The incident was triggered by planned maintenance on our primary database,
which briefly required locking parts of the database. At the same time, a
high-frequency...

Between June 19 and June 21, Ventrata experienced four brief periods of service disruption due to automated restarts on our primary database instance. Adjusted to UTC, the specific downtime windows occurred on June 19 from 14:00 to 14:10 UTC and 19:23 to 19:27 UTC, June 20 from 11:21 to 11:23 UTC, and June 21 from 17:51 to 17:57 UTC. All systems automatically recovered within minutes of each incident. The underlying database migration has since been successfully completed, and permanent archi...

Service appears to be returning to normal. We are continuing to monitor the situation closely and will provide further updates.

Transactional email delivery is showing signs of recovery after the earlier degraded performance from our email provider. The provider has marked the incident as resolved, and we are seeing the backlog of queued messages continue to decrease.

Some emails may still be delayed while the remaining backlog is processed. We will continue to monitor delivery performance and provide further updates if needed.