Degraded performance of Block Explorer
Timeline · 1 update
- resolved Feb 21, 2026, 08:47 PM UTC
Certain large entities on Block Explorer were not loading all cards. This was intermittent and the service is now working as expected.
TRM Labs had 53 outages in the last 2 years totaling 187h 41m of downtime — averaging 2.2 incidents per month.
There were 53 TRM Labs outages since October 22, 2025 totaling 187h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Certain large entities on Block Explorer were not loading all cards. This was intermittent and the service is now working as expected.
High error rates on WS APIs. The issue has been identified, the errors are not happening at the moment and we are continuing to monitor.
We have deployed a temporary fix and error rates have stabilized. We expect to roll out a permanent resolution within the next 24–48 hours.
Fixes have landed. All systems back to normal.
Issues with plotting/loading Graph Visualizer
The issue has been identified and we are working on a fix.
A fix has been rolled out and Graph Visualizer is restored. We will continue to monitor.
The issue has been resolved with all functionality restored.
Seeing intermittent high error rates on WS APIs. Investigating the issue.
We have identified the issue. We are looking in to resolving it. Currently, there are no net new errors on the APIs.
The issue has been fixed and we see no errors on the APIs. We will continue to monitor and provide the next update around Friday 02/06 12 PM EST.
The issue has been resolved.
We are seeing slowness and some occasional errors in EU Forensics. We are currently investigating.
We have identified the issue and working on a fix.
All errors on Forensics in EU have been resolved. We are looking in to any slowness concerns.
Risk indicator issues are resolved as well and we see improved performance. Will continue to monitor.
The issue is resolved.
Our monitoring systems have detected degraded performance on the Wallet Screening endpoint. TRM engineering teams are investigating and will provide regular updates.
This incident has been resolved.
The incident has been resolved.
This incident has been resolved.
We are experiencing reduced performance of our APIs
The issue has been resolved with no reported customer impact.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of transactions suck in processing in our Transaction Monitoring platform.
We have confirmed an issue which has delayed processing of Transaction Monitoring transactions. This has resulted in transactions being stuck in "PROCESSING" on the platform. We are actively root causing.
We have identified and mitigated the issue. We are monitoring to confirm resolution.
All stale transactions are processed and issued are resolved.
We are monitoring elevated error rates
We are continuing to monitoring elevated error rates
We have identified the issue, and rolled back the bad release
Error rates are back to normal, and we are monitoring the situation
Error rates and API throughput have recovered
We are currently investigating this issue.
We are still investigating this issue.
We are still investigating this issue.
We've released a fix for the issue and are monitoring the situation.
Performance and error rates are back to baseline.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of TM API errors and are currently investigating into the issue.
A small subset of transactions related to a dusting attack are experiencing elevated error rates. We are coordinating directly with impacted customers.
A small subset of transactions related to a dusting attack are experiencing elevated error rates. We have identified the issue and are in the process of applying a fix. We are coordinating directly with impacted customers.
A small subset of transactions related to a dusting attack experienced elevated error rates. A fix has been applied, and we are monitoring to ensure stability. We are coordinating directly with impacted customers.
A small subset of transactions related to a dusting attack experienced elevated error rates. The issue has been resolved, and systems are operating normally.
We're experiencing an elevated level of TM API errors and are currently investigating into the issue.
We have identified the issue causing elevated error rates. The impact is limited to a small number of TM API calls with large payload sizes. Our team is actively working on mitigation and will provide updates as progress is made.
A fix has been implemented to mitigate the elevated error rates affecting a small subset of TM API calls with large payloads. The team is actively monitoring to ensure continued stability.
This incident has been resolved.
Customers experienced a Service Degradation affecting Forensics for approximately 35 min. During this time, some requests may have been slower than expected or intermittently unavailable. Other TRM APIs, including WS and TM, were not impacted.
We are actively investigating a performance degradation affecting some Forensics components.
We have identified the underlying issue affecting some Forensics components and applied mitigations. We are seeing recovery and key performance metrics are moving back toward normal levels.
We have identified the underlying issue affecting some Forensics components and applied mitigations. The system has recovered, and we are monitoring closely to ensure performance remains stable.
The issue impacting performance of Forensics components has been resolved.
We are investigating reports of ongoing Cloudflare issues disrupting access to our systems.
We have confirmed reports of a brief Cloudflare outage. They had an incident they reported on and closed that impacted our APIs. https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q This issue has been resolved and we are observing no ongoing evidence of issues. We are continuing to monitor this to ensure no impacts.
Cloudflare has confirmed that the incident has been fully resolved. Our services have remained stable since their remediation, and we are no longer observing any related errors or impact. This issue is now considered resolved. We will continue routine monitoring to ensure continued system performance.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating the issue with BTC transfers table.
We have identified the missing subset of transfers from the 15th for BTC. We are currently working on a fix.
A fix has been implemented, the missing transfers can be viewed on Forensics now. We are doing further validations.
The incident has been resolved.
An outage with our upstream authentication provider (Auth0) may cause some people to not be able to login to TRM. We are working closely with our provider to restore services. https://status.auth0.com/incidents/hykzwhgmgn8z
We monitoring recovery, and new user sessions should now be available. We are continuing to monitor for an ongoing error rates for user login. Core transactions APIs remain un-affected. Incident is ongoing for upstream provider
We are continuing to see recovery. Upstream provider has also updated their status to monitoring.
Upstream provider is fully recovered.
Login is failing and the webapp is non-operational
This issue has been resolved.