TRM Labs Outage History

We’re investigating an issue affecting Graph Visualizer. Some customers may be unable to save graphs, may see graph nodes become unclickable during auto-save, or may find that saved graphs reopen blank or without a draft name. Our engineering team is actively investigating. We will provide another update within approximately 30 minutes, or sooner if we identify a mitigation or resolution. We’re sorry for the disruption and recommend avoiding edits to affected graphs until we provide further guidance.

Updated the components affected.

We're experiencing an elevated level of API errors and are currently looking into the issue.

We’re investigating an issue preventing some users from switching between customer environments. Other functionality may be available, but switching environments is currently affected. As a workaround in the meantime, users can log out and and log back into the environment they wish to switch to.

A cross-service error-rate spike affected Transaction Monitoring, Graph Visualizer, and Wallet Screening for approximately 15 mins between 22:23–22:38 UTC (6:23–6:38pm EDT). The spike has subsided and the current error rate is now low. The team is investigating the root cause.

We are investigating ongoing degraded performance affecting Graph Visualizer. Some customers may experience elevated error rates and requests taking longer than usual. We will provide another update as more information becomes available.

We confirmed this degradation was caused by AlloyDB realtime replication lag, which led to realtime query timeouts and elevated 5xx responses on GV fast path endpoints. We're investigating remediation steps.

We are investigating an issue causing Graph Visualizer to load very slowly or freeze when customers add or manipulate graphs.

We're experiencing an elevated level of API errors and are currently looking into the issue.

We are continuing to investigate this issue.

We’re investigating slow responses and elevated errors affecting the transactions feature and API endpoint. Requests involving multiple transactions may take up to 30 seconds to complete or may fail with a timeout, which can cause plotting and transaction-query features in GV to load slowly or fail.

Investigating: degraded Graph Visualizer transaction queries We’re continuing to investigate slow responses and intermittent timeouts affecting transaction-based plots in Graph Visualizer. Requests involving multiple transactions may take up to 30 seconds to complete or may fail, causing some plots to load slowly or not render. Our engineering team has identified and is applying a fix. We’re aiming to restore normal performance within approximately one hour. We’ll provide another update when the fix is deployed and verified.

We are investigating reports of elevated errors and latency affecting wallet screening requests. Our engineering team is reviewing the available data to determine the scope and cause of the issue. We will provide another update by 6:00pm PDT on 20 August 2026, or sooner if more information becomes available.

TM2 transfers are currently experiencing degraded performance and customers might experience timeouts. The team is investigating

We are investigating delays affecting retry screening for Transaction Monitoring (TM2) transfers on the Injective chain.

Some of the TRM systems are experiencing issues resulting in users not being able to access our services. We are investigating the issues.

We are currently investigating a performance degradation affecting the GV Fast Path service. Users may experience slower response times and increased latency. Our engineering team is actively working to identify and resolve the root cause.

We are experiencing some data freshness issues. All services remain available. The team has identified the issue and is investigating.

We are investigating an error rate on specific API route for Forensics

We are investigating reports of 502 Bad Gateway errors.

We are continuing to investigate the issue.

We're noticing roughly 1% of initial screenings are degraded. We're investigating the issue.

Currently investigating

Note: API services are healthy. Only webhook services are affected.

NOTE: The API itself continues to be healthy. This is only affecting webhook services.