Incidents reported on status page for Paygle Pty Ltd https://status.paygle.com/ https://d1lppblt9t2x15.cloudfront.net/logos/583c00c72119fc01bb9f1e56cac56829.png https://status.paygle.com/ en https://status.paygle.com/ Mon, 16 Mar 2026 00:38:35 +0000 https://status.paygle.com/#f5133c997b0c0d08e8c13c0d1e6b1761b669ac4cd693b13428f7f03fa1638779 Paygle API recovered https://status.paygle.com/ Mon, 16 Mar 2026 00:27:57 +0000 https://status.paygle.com/#f5133c997b0c0d08e8c13c0d1e6b1761b669ac4cd693b13428f7f03fa1638779 Paygle API went down https://status.paygle.com/ Fri, 13 Mar 2026 02:41:32 +0000 https://status.paygle.com/#179ce215347ebac660efd108492afdb0bacd70e7bd5e9fc6ad1f0e07d2c8ecaa Paygle API recovered https://status.paygle.com/ Fri, 13 Mar 2026 02:36:27 +0000 https://status.paygle.com/#179ce215347ebac660efd108492afdb0bacd70e7bd5e9fc6ad1f0e07d2c8ecaa Paygle API went down https://status.paygle.com/ Tue, 10 Mar 2026 00:47:30 +0000 https://status.paygle.com/#cc857a2347e6c37b84f654ba54b4b59e759f1e087fe59551d785483c290a0261 Paygle API recovered https://status.paygle.com/ Tue, 10 Mar 2026 00:37:06 +0000 https://status.paygle.com/#cc857a2347e6c37b84f654ba54b4b59e759f1e087fe59551d785483c290a0261 Paygle API went down https://status.paygle.com/ Mon, 09 Mar 2026 00:44:42 +0000 https://status.paygle.com/#0f770db871d936964af12228eee3efb52601587d60a5f92e4624ec66845b4fed Paygle API recovered https://status.paygle.com/ Mon, 09 Mar 2026 00:37:06 +0000 https://status.paygle.com/#0f770db871d936964af12228eee3efb52601587d60a5f92e4624ec66845b4fed Paygle API went down https://status.paygle.com/ Sat, 07 Mar 2026 03:29:34 +0000 https://status.paygle.com/#b57c3863b73ac0fe42cbbf2d5f9d25d67d3d5ce3bd166718e3ddd4aa1ee40fe9 Paygle API recovered https://status.paygle.com/ Sat, 07 Mar 2026 03:22:02 +0000 https://status.paygle.com/#b57c3863b73ac0fe42cbbf2d5f9d25d67d3d5ce3bd166718e3ddd4aa1ee40fe9 Paygle API went down https://status.paygle.com/incident/373989 Fri, 24 May 2024 04:00:00 -0000 https://status.paygle.com/incident/373989#d43e516838ec39d7d8932bd046050dba60c176ca6fc5cd82ccebbb659ce4c2f0 Due to an unscheduled server reboot, the status check endpoint temporarily (for around 8 minutes) experience longer than normal response times. Note that API requests were not impacted at this time, as the backend would have automatically moved load to the corresponding geo-redundant server