TRM Labs logo and current status indicator

TRM Labs Incident History

Operational

trmlabs.com 2 components

checked Sep 7, 2026 6:15 AM UTC · TRM Labs's official status page

TRM Labs is up and running.

TRM Labs is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.

Be the first to know

Statusfield watches TRM Labs alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

TRM Labs incident history

13 reports published by TRM Labs in the last 30 days

When TRM Labs breaks, it is typically resolved in 2h 5m — median across 11 resolved incidents over 90 days.

September 4, 2026

Users unable to switch environments

Last update
  1. resolvedSep 4 · 04:03 UTC

    Issue is fixed

Reported by TRM Labs on their status page.

Wallet Screening API - degraded performance detected

Last update
  1. resolvedSep 4 · 02:59 UTC

    We've identified the root cause and have implemented a fix.

Reported by TRM Labs on their status page.

September 1, 2026

Wallet Screening API - degraded performance detected

Last update
  1. resolvedSep 1 · 23:05 UTC

    Between 4:19:54pm and 4:38:58pm EDT on 1 September 2026, some US Wallet Screening requests failed or experienced degraded performance, including address screening and related risk and attribution lookups. Impact in the EU was negligible. The issue has been resolved. Service recovered at approximately 4:39pm EDT, and subsequent monitoring confirmed normal traffic and error rates. A mitigation has been deployed and tested to reduce the risk of recurrence. We apologize for the disruption.

Reported by TRM Labs on their status page.

August 28, 2026

Brief spike in error rates across Graph Visualizer, Wallet Screening and Transaction Monitoring.

Last update
  1. resolvedAug 28 · 01:56 UTC

    We identified an infrastructure node upgrade that rotated database proxy pods during the incident window. The pods did not drain connections cleanly, concentrating reconnects on replacement pods and causing database query read timeouts. A fix is being actively pushed. Customer impact remains resolved.

Reported by TRM Labs on their status page.

August 27, 2026

Resolved: intermittent TRM login issues

Last update
  1. resolvedAug 27 · 11:45 UTC

    The provider restored service, and TRM login access has been restored and validated

Reported by TRM Labs on their status page.

August 26, 2026

Graph Visualizer degraded performance

Last update
  1. resolvedAug 26 · 06:30 UTC

    All systems continue to look healthy. Resolving the incident.

Reported by TRM Labs on their status page.

August 24, 2026

Graph Visualizer service degraded

Last update
  1. resolvedAug 24 · 23:32 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.

August 22, 2026

Elevated API Errors

Last update
  1. resolvedAug 22 · 11:31 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.

August 21, 2026

Degraded Transaction Query Performance

Last update
  1. resolvedAug 21 · 18:33 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.

Brief interruption due to backend database outage

Last update
  1. resolvedAug 21 · 05:30 UTC

    At approximately 10:35 PM PT, TRM experienced a brief service interruption due to the underlying cloud provider's maintenance affecting some Insights endpoints. The disruption lasted approximately ten minutes, after which systems recovered and service resumed normal operation.

Reported by TRM Labs on their status page.

Wallet Screening performance

Last update
  1. resolvedAug 21 · 06:21 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.

August 14, 2026

TM2 degradation

Last update
  1. resolvedAug 14 · 18:50 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.

August 11, 2026

Delayed retry screening for Injective Chain transaction monitoring

Last update
  1. resolvedAug 11 · 15:09 UTC

    This incident has been resolved.

Reported by TRM Labs on their status page.