pingoru pingoru VoPay had 6 outages in the last 2 years totaling 14h 17m of downtime, averaging 0.2 incidents per month.
There were 6 VoPay outages since April 7, 2025 totaling 14h 17m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We're currently experiencing fund settlement delays due to temporary connectivity issues with our banking partner. Our team is actively working to resolve this as quickly as possible
This incident has been resolved.
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.
VoPay services experienced intermittent connectivity issues and full service disruption due to a widespread global network outage affecting Cloudflare, one of our key cloud infrastructure providers. The outage impacted inbound access to our APIs and portals, resulting in elevated error rates, service timeouts, and inaccessible interfaces during the affected periods. All VoPay systems remained operational internally; however, requests entering through Cloudflare’s edge network were unable to reach our infrastructure reliably. Service was fully restored once Cloudflare remediated the underlying issue.
We are currently observing disruptions affecting Interac E-transfers. These appear to be related to an ongoing issue with a third-party service provider integral to our Interac E-transfer operations. Users may experience delays in sending/receiving Interac E-transfers. Our APIs remain operational. We are closely monitoring the situation and are in contact with our partner to understand their resolution timeline.
This incident has been resolved. There may still some delays while the backlog of transactions are processed.
Between 7PM EST and 8PM EST, we observed disruptions affecting EFT processing. These were determined to be related to an issue with a third-party service provider integral to our EFT operations. Our internal systems remained operational during this period. We monitored the situation and confirmed that services were restored at approximately 8PM EST. EFT processing is now functioning normally. We apologize for any inconvenience this may have caused.
Beginning at approximately 2:18am, some clients may have experienced intermittent API errors or timeouts. The issue was traced to connectivity disruptions affecting certain Amazon RDS instances, and has since been resolved.