Live  /  Payplug  /  Incident

Payplug: Incident externe / External incident / Incidente esterno

Payplug · payplug.comMinor incidentResolved2026-10-13 07:10 UTC
Public — what happened

Summary

Payplug said that on 2026-10-12 at 14:56 UTC, payments made through Oney on its platform were failing with a 5001 error code, and that the problem appeared to originate outside its own systems. By 15:05 UTC the company reported that the underlying cause had been found and that an outside provider was working on a fix. Payplug said the provider rolled out the fix at 16:49 UTC, after which it kept watching the service, and the incident was marked resolved on 2026-10-13 at 07:10.

Affected

Moyens de paiements alternatifs

As listed on Payplug’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Payplug against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Payplug: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Payplug report →

More from Payplug

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Payplug status & history page.

Related: Payplug status & history. SquidGrid is not affiliated with Payplug.