Live / Paysafe / Incident
Paysafe: Service Disruption - PagoEfectivo
Paysafe · paysafe.comMinor incidentResolved2026-11-01 22:47 UTC
Public — what happened
Summary
Paysafe reported a minor service disruption affecting PagoEfectivo, which it began investigating at 16:25 UTC on 2026-11-01. By 17:52 UTC it said a solution was in place and it was watching activity on the affected services. Later, at 20:32 UTC, it said it had found a further improvement and was applying a fix, and at 21:08 UTC it said the fix was deployed and the issue was no longer seen. The incident was marked resolved at 22:47, and Paysafe did not state a cause in its updates.
Affected
Merchant Notification (PagoEfectivo)
Timeline
- Started — 2026-11-01 16:25 UTC
- Investigating — 2026-11-01 16:25 UTC
- Monitoring — 2026-11-01 17:52 UTC (4 updates)
- Resolved — 2026-11-01 22:47 UTC · 6h 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 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.