Live / Zoop / Incident
Zoop: Instabilidade identificada em CNP e Tokenização
Zoop · zoop.com.brMajor incidentResolved2026-08-31 16:09 UTC
Public — what happened
Summary
Zoop reported a major incident involving instability in its card-not-present (CNP) payments and tokenization services, beginning on 2026-08-31 at 15:18 UTC. The company said it had found where the problem originated but did not describe the cause, and that several teams were working together on a fix while closely watching the systems. Zoop's status was still listed as identified, though the incident record shows a resolution time of 17:00 the same day.
Timeline
- Started — 2026-08-31 15:18 UTC
- Resolved — 2026-08-31 17:00 UTC · 1h 42m 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 Zoop 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 Zoop: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zoop report →
More from Zoop
Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.