TRM Labs experienced a major incident on May 27, 2026 affecting US - API - Wallet Screening and US - API - Transaction Monitoring and 1 more component, lasting 4h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 27, 2026, 07:21 AM UTC
We an investigating an issue with an upstream infrastructure provider, and working on failover options.
- investigating May 27, 2026, 07:23 AM UTC
We are continuing to investigate this issue.
- investigating May 27, 2026, 07:56 AM UTC
We are continuing to investigate network connectivity issues between our web tier and confluent cloud. We have identified a potential cause, and currently working on failover
- investigating May 27, 2026, 08:00 AM UTC
We are continuing to look into the issue and pursuing a few mitigation options.
- identified May 27, 2026, 08:26 AM UTC
We have validated the root cause (web tier egress IPs were auto-blocklisted for malicious activity), and we are continuing to failover to AWS unblock new requests.
- identified May 27, 2026, 08:27 AM UTC
We are continuing to work on a fix for this issue.
- identified May 27, 2026, 08:45 AM UTC
We failed over TM2, and all new requests should proceed as normal. We are actively working on requeueing pending requests posted during the outage.
- identified May 27, 2026, 09:40 AM UTC
We are working on requeuing any outstanding transfers submitted during the incident
- monitoring May 27, 2026, 10:19 AM UTC
We have worked with our infrastructure provider to fix connectivity issues, and all systems are recovering. We are working on re-processing in-flight TM2 requests during the outage.
- monitoring May 27, 2026, 11:21 AM UTC
We are continuing to work through the backlog of re-processing the in-flight TM2 requests.
- resolved May 27, 2026, 12:00 PM UTC
The entire backlog has been re-processed. Systems are back in a healthy state.