Paydock Outage History

This incident has been resolved. An unusually high volume of traffic affected our payment processing systems, causing delays and failed payments for some customers. We've put additional protections in place, and payment processing has been operating normally since. We'll continue to monitor closely. We apologise for the disruption, and thank you for your patience.

Following the earlier incident, Paydock experienced a second period of degraded performance beginning 04:49 UTC (14:49 AEST). The affected window — during which several internal services in the payment path were unavailable — was 05:29–05:49 UTC (15:29–15:49 AEST). Performance stabilised shortly after, and full recovery was confirmed by 07:05 UTC (17:05 AEST).

All services have been restored to full functionality. Please reach out to [email protected] if you are still experiencing any issues.

Issues with Payment throughput were resolved at 3:23pm AEDT

This incident has been resolved.

Gpayments have advised that the issue has been resolved, no errors have been observed since 6:50pm AEST.

Temporary unavailability and degraded performance of POST//v1/charges/wallet and POST//v1/charges endpoints due to a configuration change to reinforce the Platform's security. Customers of the unaffected instances were still able to complete their transactions. The incident itself started at 16:38 PM UTC and finished at 17:47 PM UTC.

On the 22/01/2025 Between 09:45 PM and 10:17PM AEDT We experienced a major outage affecting 50% of our instances, meaning that 50% of the instances continued to function correctly. However, the misconfiguration had a direct impact on customers attempting to make card and wallet payments. Customers on the affected instances were unable to complete transactions, which caused a significant disruption. That said, customers on unaffected instances were still able to transact normally, ensuring some continuity of service.

The Incident has been resolved.