Live / Paysafe / Incident
Paysafe: Service Disruption - White Labels (Client Websites)
Paysafe · paysafe.comMajor incidentResolved2026-10-26 08:04 UTC
Public — what happened
Summary
Paysafe reported a major service disruption affecting white label services, which it described as client websites. The company said it began investigating at 05:53 UTC on 2026-10-26, and by 07:11 UTC it said it had found the root cause and was working on a fix. At 07:51 UTC Paysafe said a solution was in place and it was monitoring the affected services, and the incident was marked resolved at 08:04 UTC. The company did not say how many customers were affected or describe the cause in detail.
Affected
Income Access - White Labels (Client Websites)
Timeline
- Started — 2026-10-26 05:53 UTC
- Investigating — 2026-10-26 05:53 UTC
- Identified — 2026-10-26 07:11 UTC
- Monitoring — 2026-10-26 07:51 UTC
- Resolved — 2026-10-26 08:04 UTC · 2h 11m 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 Paysafe 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 Paysafe: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Paysafe report →
More from Paysafe
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.