Live / PAY. / Incident
PAY.: Mobile connectivity issues affecting some payment terminals
PAY. · pay.nlResolved2026-10-23 08:55 UTC
Public — what happened
Summary
PAY. said some of its payment terminals had trouble connecting through their SIM cards, a problem it traced to its mobile connectivity provider. The incident was reopened on 22 October at 14:33 UTC after an earlier recovery proved incomplete, and PAY. suggested using Wi-Fi, a mobile hotspot, or Pay.POS on a smartphone in the meantime. PAY. said the provider narrowed the problem to part of its core network and later found unusually slow responses in a key component. At 07:13 UTC on 23 October PAY. said service came back after the provider returned to its previous system, and it marked the incident resolved at 08:55 after a monitoring period, advising anyone still disconnected to restart their terminal.
Affected
Instore Payments
Timeline
- Started — 2026-10-22 14:33 UTC
- Investigating — 2026-10-22 14:33 UTC
- Identified — 2026-10-22 15:37 UTC (4 updates)
- Monitoring — 2026-10-23 07:13 UTC
- Resolved — 2026-10-23 08:55 UTC · 18h 22m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach PAY. against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for PAY.: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the PAY. report →
More from PAY.
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.