VoPay incident

API Performance Issues

Resolved on February 3, 2026.

resolved Feb 04, 2026, 11:06 PM UTC

Between 7:58 AM and 8:16 AM PT on February 3, the platform experienced degraded performance and a brief period of API instability. This was caused by a database migration that resulted in unexpected resource locking, leading to client timeouts. Our engineering team identified the lock and took immediate action to clear it, restoring full service by 8:16 AM PT. We have since verified that all systems are processing normally. We are reviewing our deployment and testing protocols to ensure better visibility into these types of database locks in the future.

Started
Feb 03, 2026, 04:00 PM UTC
Resolved
Feb 03, 2026, 04:00 PM UTC
Duration
–
Detected by Pingoru
Feb 03, 2026, 04:00 PM UTC

Update timeline

  1. resolved Feb 04, 2026, 11:06 PM UTC

    Between 7:58 AM and 8:16 AM PT on February 3, the platform experienced degraded performance and a brief period of API instability. This was caused by a database migration that resulted in unexpected resource locking, leading to client timeouts. Our engineering team identified the lock and took immediate action to clear it, restoring full service by 8:16 AM PT. We have since verified that all systems are processing normally. We are reviewing our deployment and testing protocols to ensure better visibility into these types of database locks in the future.

Your product runs on more than VoPay

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →