Live / TRM Labs / Incident
TRM Labs: Delayed Initial Transaction Screenings
TRM Labs · trmlabs.comCritical outageResolved2026-10-21 16:58 UTC
Public — what happened
Summary
TRM Labs said that starting at 6:03 PM EDT on October 20, 2026, initial transaction screenings in Transaction Monitoring 2.0 in its EU region stayed in a processing state and did not finish. The company reported at 07:15 UTC on October 21 that it had found the cause and was restarting the affected services so that queued transfers could be handled. By 07:21 UTC it said recovery was confirmed and it was monitoring, and the incident was marked resolved at 16:58 UTC.
Affected
EU - API - Transaction Monitoring
Timeline
- Started — 2026-10-21 07:13 UTC
- Identified — 2026-10-21 07:13 UTC (3 updates)
- Monitoring — 2026-10-21 07:21 UTC
- Resolved — 2026-10-21 16:58 UTC · 9h 45m 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 TRM Labs 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 TRM Labs: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the TRM Labs report →
More from TRM Labs
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.