Live / Tango Card / Incident
Tango Card: Order History Delayed
Tango Card · tangocard.comMinor incidentResolved2026-11-04 23:04 UTC
Public — what happened
Summary
Tango Card said that starting at 22:07 UTC on 2026-11-04, order history shown in its Tango Portal was running about 2 to 3 hours behind, and that lookups of orders through its RaaS service might also be late. The company said it had already fixed the underlying problem and was working through the backlog of delayed records. It also said orders were still being fulfilled normally and recipients were not affected. Tango Card marked the incident resolved at 23:04 UTC the same day.
Affected
RaaS API v2 - Production, Tango Portal
Timeline
- Started — 2026-11-04 22:07 UTC
- Identified — 2026-11-04 22:07 UTC
- Resolved — 2026-11-04 23:04 UTC · 57 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 Tango Card 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 Tango Card: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Tango Card report →
More from Tango Card
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.