Live / Nayax / Incident
Nayax: Identified - partner - network
Nayax · nayax.comResolved2026-10-22 19:28 UTC
Public — what happened
Summary
Nayax reported a problem that began at 18:37 UTC on 2026-10-22, which it said came from a network issue at one of its partners. The company said the partner was working to fix the underlying problem while Nayax monitored the situation and worked to restore steady support across its own network. The incident is marked resolved as of 19:28 UTC the same day, and Nayax did not say which customers were affected.
Affected
CORE, SQS (Transaction Reports), Telemetry, Monyx, MoMa, MQTT
Timeline
- Started — 2026-10-22 18:37 UTC
- Identified — 2026-10-22 18:37 UTC
- Resolved — 2026-10-22 19:28 UTC · 51 min 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 Nayax 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 Nayax: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Nayax report →
More from Nayax
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.