Live / Tazapay / Incident
Tazapay: [Auto] Degraded performance: GBP
Tazapay · tazapay.comMinor incidentResolved2026-10-26 02:32 UTC
Public — what happened
Summary
Tazapay reported a minor issue affecting its GBP service, which it labeled degraded performance, starting at 02:31 UTC on 2026-10-25. The company said the problem was a service degradation at the provider or partner level and that it was working with that provider toward a fix. Tazapay marked the incident resolved at 02:32 UTC on 2026-10-26, and it did not describe who was affected beyond the GBP service.
Affected
GBP
Timeline
- Started — 2026-10-25 02:31 UTC
- Investigating — 2026-10-25 02:31 UTC
- Resolved — 2026-10-26 02:32 UTC · 24h 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 Tazapay 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 Tazapay: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Tazapay report →
More from Tazapay
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.