TRM Labs Outage History

TRM Labs is up right now

Pingoru has recorded 97 incidents for TRM Labs: 96 in the last 12 months and 25 in the last 90 days.

Source: status.trmlabs.com

97incidents recorded
96last 12 months
25last 90 days
5 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking TRM Labs in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026820 of 720 (3%)
May 2026519 of 744 (3%)
June 2026721 of 720 (3%)
July 2026757 of 744 (8%)
August 20261453 of 744 (7%)
September 2026826 of 720 (4%)
October 2026319 of 578 (3%)

Incidents, newest first

Critical October 21, 2026 Delayed Initial Transaction Screenings 9h 45m EU - API - Transaction Monitoring

Started Oct 21, 2026, 07:13 AM UTC· resolved Oct 21, 2026, 04:58 PM UTC

  1. identified Oct 21, 2026, 07:13 AM UTC

    Beginning October 20, 2026, at 6:03 PM EDT, initial transaction screenings in Transaction Monitoring 2.0 in the EU region remained in PROCESSING without completing.

  2. identified Oct 21, 2026, 07:15 AM UTC

    We have identified the cause and are restarting the affected services to process queued transfers.

  3. identified Oct 21, 2026, 07:16 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Oct 21, 2026, 07:21 AM UTC

    Recovering is confirmed. Monitoring.

  5. resolved Oct 21, 2026, 04:58 PM UTC

    Fully resolved outage.

Read the full incident report →

Critical October 20, 2026 Delayed Detect Alerts and Email Notifications 18h 57m EU - Detect, US - Detect

Started Oct 20, 2026, 10:00 PM UTC· resolved Oct 21, 2026, 04:58 PM UTC

  1. monitoring Oct 21, 2026, 07:17 AM UTC

    Beginning October 20, 2026, at 6:03 PM EDT, an issue interrupted processing of certain Detect evaluations, alerts, and email notifications in the US and EU regions. Real-time Detect evaluation remained operational. US processing was restored on October 21 at 2:40 AM EDT. We are restoring processing in the EU region and verifying recovery of queued work.

  2. monitoring Oct 21, 2026, 07:28 AM UTC

    All detect regions are confirmed operational

  3. resolved Oct 21, 2026, 04:58 PM UTC

    Fully resolved outage.

Read the full incident report →

Major September 17, 2026 Graph Visualizer graphs may not save correctly 49m US - Forensics on Web, EU - Forensics on Web

Started Sep 17, 2026, 09:09 PM UTC· resolved Sep 17, 2026, 09:58 PM UTC

  1. investigating Sep 17, 2026, 09:09 PM UTC

    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.

  2. investigating Sep 17, 2026, 09:11 PM UTC

    Updated the components affected.

  3. identified Sep 17, 2026, 09:28 PM UTC

    We identified the issue was with the saving functionality and are landing a fix.

  4. resolved Sep 17, 2026, 09:58 PM UTC

    The fix has been verified and the issue has been resolved.

Read the full incident report →

Major September 17, 2026 Delayed Beacon alerts 14h 27m US - Detect

Started Sep 17, 2026, 06:46 AM UTC· resolved Sep 17, 2026, 09:14 PM UTC

  1. monitoring Sep 17, 2026, 06:46 AM UTC

    Between September 13 at 02:08am UTC and September 17 at approximately 05:45am UTC, some Beacon Network alerts were delayed and did not reach customers as expected. Alert delivery has been restored, and all alerts from the affected period have now been delivered. No alert data was lost, although affected alerts may have arrived later than usual and in a burst. We apologize for the disruption. We are continuing to monitor the service and reviewing our alerting and workflow safeguards to help prevent a recurrence.

  2. resolved Sep 17, 2026, 09:14 PM UTC

    Systems are stable. Closing the incident.

Read the full incident report →

Minor September 10, 2026 ARC Transfer Screenings Stuck 2h 57m US - API - Transaction Monitoring

Started Sep 10, 2026, 06:01 PM UTC· resolved Sep 10, 2026, 08:58 PM UTC

  1. identified Sep 10, 2026, 06:01 PM UTC

    All ARC transfers within the ~last hour are unable to be resolved within our backend and do not complete screening. We have escalated the issue to the third-party dependency and are working on a fix.

  2. resolved Sep 10, 2026, 08:58 PM UTC

    We've determined that the failure rate seen on Transaction Monitoring was inaccurate and driven by an influx of invalid Arc transfers. No outage identified.

Read the full incident report →

Minor September 10, 2026 Elevated API Errors 1h 45m

Started Sep 10, 2026, 02:20 AM UTC· resolved Sep 10, 2026, 04:06 AM UTC

  1. investigating Sep 10, 2026, 02:20 AM UTC

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

  2. identified Sep 10, 2026, 02:30 AM UTC

    We've identified the cause of the elevated error rate and are working on a fix.

  3. monitoring Sep 10, 2026, 03:58 AM UTC

    We have deployed a fix and are monitoring the currently-falling error rate.

  4. resolved Sep 10, 2026, 04:06 AM UTC

    We have confirmed that the error rate has fallen back to before-incident levels.

Read the full incident report →

Minor September 4, 2026 Users unable to switch environments 2h 48m

Started Sep 04, 2026, 01:15 AM UTC· resolved Sep 04, 2026, 04:03 AM UTC

  1. investigating Sep 04, 2026, 01:15 AM UTC

    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.

  2. monitoring Sep 04, 2026, 04:02 AM UTC

    We deployed a fix and validated that the environment switch flow now routes correctly and opens the environment switcher, as expected.

  3. resolved Sep 04, 2026, 04:03 AM UTC

    Issue is fixed

Read the full incident report →

Minor September 4, 2026 Wallet Screening API - degraded performance detected 2h 10m US - API - Wallet Screening, EU - API - Wallet Screening

Started Sep 04, 2026, 12:49 AM UTC· resolved Sep 04, 2026, 02:59 AM UTC

  1. monitoring Sep 04, 2026, 12:49 AM UTC

    We are investigating an issue causing an elevated rate of HTTP errors for Wallet Screening. The issue has been mitigated, and our engineering team is actively assessing the scope and cause of the issue.

  2. monitoring Sep 04, 2026, 01:08 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Sep 04, 2026, 02:59 AM UTC

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

Read the full incident report →

Notice August 27, 2026 Brief spike in error rates across Graph Visualizer, Wallet Screening and Transaction Monitoring. 2h 55m US - Forensics on Web, US - API - Wallet Screening, US - API - Transaction Monitoring

Started Aug 27, 2026, 11:01 PM UTC· resolved Aug 28, 2026, 01:56 AM UTC

  1. investigating Aug 27, 2026, 11:01 PM UTC

    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.

  2. resolved Aug 28, 2026, 01:56 AM 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.

Read the full incident report →

Major August 27, 2026 Resolved: intermittent TRM login issues 8m US - Forensics on Web

Started Aug 27, 2026, 11:36 AM UTC· resolved Aug 27, 2026, 11:45 AM UTC

  1. monitoring Aug 27, 2026, 11:36 AM UTC

    Some customers and internal users were intermittently unable to log in to TRM for approximately 38 minutes on 27 August 2026, from around 3:15pm to 3:53pm PDT. The issue was caused by an intermittent outage affecting one of our authentication service providers. The provider has restored service, and TRM login access has been restored and validated. We are continuing to monitor the service. We apologize for the disruption.

  2. resolved Aug 27, 2026, 11:45 AM UTC

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

Read the full incident report →

Minor August 26, 2026 Graph Visualizer degraded performance 2h 5m US - Forensics on Web, EU - Forensics on Web

Started Aug 26, 2026, 04:25 AM UTC· resolved Aug 26, 2026, 06:30 AM UTC

  1. investigating Aug 26, 2026, 04:25 AM UTC

    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.

  2. investigating Aug 26, 2026, 05:11 AM UTC

    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.

  3. identified Aug 26, 2026, 05:49 AM UTC

    We have identified the cause of the degraded performance affecting Graph Visualizer, where some requests may be slow or return an error. A scheduled background data process is placing elevated load on a supporting database, and we are actively working to reduce that load and restore normal performance.

  4. monitoring Aug 26, 2026, 06:07 AM UTC

    The steps we took to reduce load on the affected database have taken effect, and Graph Visualizer error rates and response times have returned to normal levels. We are continuing to monitor closely to confirm performance remains stable before marking this resolved.

  5. resolved Aug 26, 2026, 06:30 AM UTC

    All systems continue to look healthy. Resolving the incident.

Read the full incident report →

Major August 24, 2026 Graph Visualizer service degraded 5h 8m US - Forensics on Web, EU - Forensics on Web

Started Aug 24, 2026, 06:24 PM UTC· resolved Aug 24, 2026, 11:32 PM UTC

  1. investigating Aug 24, 2026, 06:24 PM UTC

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

  2. identified Aug 24, 2026, 06:44 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 24, 2026, 09:47 PM UTC

    The fix for the Graph Visualizer performance issue has been deployed to production. We are monitoring the rollout and verifying that large graphs load and respond normally when customers add or move elements.

  4. monitoring Aug 24, 2026, 09:55 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  5. monitoring Aug 24, 2026, 09:56 PM UTC

    The fix for the Graph Visualizer performance issue has been deployed to production. We are monitoring the rollout and verifying that large graphs load and respond normally when customers add or move elements.

  6. resolved Aug 24, 2026, 11:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 21, 2026 Degraded Transaction Query Performance 3h 39m US - Forensics on Web, EU - Forensics on Web

Started Aug 21, 2026, 02:53 PM UTC· resolved Aug 21, 2026, 06:33 PM UTC

  1. investigating Aug 21, 2026, 02:53 PM UTC

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

  2. investigating Aug 21, 2026, 03:12 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 21, 2026, 03:13 PM UTC

    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.

  4. investigating Aug 21, 2026, 03:49 PM UTC

    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.

  5. monitoring Aug 21, 2026, 05:21 PM UTC

    Monitoring: degraded Graph Visualizer transaction queries The issue affecting transaction-based Graph Visualizer plots has been resolved. Requests to the transaction query endpoint are now responding normally, and Graph Visualizer plots should load as expected. We'll continue monitoring the service and are also completing a longer-term fix to prevent the issue from recurring. We're sorry for the disruption.

  6. resolved Aug 21, 2026, 06:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 21, 2026 Brief interruption due to backend database outage –

Started Aug 21, 2026, 05:30 AM UTC· resolved Aug 21, 2026, 05:30 AM UTC

  1. resolved Aug 21, 2026, 06:20 AM 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.

Read the full incident report →

Minor August 21, 2026 Wallet Screening performance 5h 47m US - API - Wallet Screening, EU - API - Wallet Screening

Started Aug 21, 2026, 12:33 AM UTC· resolved Aug 21, 2026, 06:21 AM UTC

  1. investigating Aug 21, 2026, 12:33 AM UTC

    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.

  2. monitoring Aug 21, 2026, 12:54 AM UTC

    We think the impact from the issue is over.

  3. resolved Aug 21, 2026, 06:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026 TM2 degradation 13m US - API - Transaction Monitoring, EU - API - Transaction Monitoring

Started Aug 14, 2026, 06:37 PM UTC· resolved Aug 14, 2026, 06:50 PM UTC

  1. investigating Aug 14, 2026, 06:37 PM UTC

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

  2. resolved Aug 14, 2026, 06:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 10, 2026 Delayed retry screening for Injective Chain transaction monitoring 22h 51m US - API - Transaction Monitoring, EU - API - Transaction Monitoring

Started Aug 10, 2026, 04:18 PM UTC· resolved Aug 11, 2026, 03:09 PM UTC

  1. investigating Aug 10, 2026, 04:18 PM UTC

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

  2. resolved Aug 11, 2026, 03:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 7, 2026 Some of our systems are experiencing issues 19m US - Forensics on Web, EU - Forensics on Web, US - API - Transaction Monitoring, US - API - BLOCKINT and 2 more

Started Aug 07, 2026, 10:16 PM UTC· resolved Aug 07, 2026, 10:35 PM UTC

  1. investigating Aug 07, 2026, 10:16 PM UTC

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

  2. monitoring Aug 07, 2026, 10:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 07, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 7, 2026 Graph Visualizer Performance Degradation 21m US - Forensics on Web

Started Aug 07, 2026, 09:54 PM UTC· resolved Aug 07, 2026, 10:15 PM UTC

  1. investigating Aug 07, 2026, 09:54 PM UTC

    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.

Read the full incident report →

Minor August 7, 2026 Data freshness issues 1h 15m

Started Aug 07, 2026, 04:33 PM UTC· resolved Aug 07, 2026, 05:48 PM UTC

  1. investigating Aug 07, 2026, 04:33 PM UTC

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

  2. monitoring Aug 07, 2026, 04:52 PM UTC

    We are experiencing some data freshness issues. All services remain available. The team has implemented the fix and we are seeing recovery and are monitoring for further issues.

  3. resolved Aug 07, 2026, 05:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 5, 2026 Elevated error rates on an API 33m US - Forensics on Web, EU - Forensics on Web

Started Aug 05, 2026, 03:03 PM UTC· resolved Aug 05, 2026, 03:37 PM UTC

  1. investigating Aug 05, 2026, 03:03 PM UTC

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

  2. identified Aug 05, 2026, 03:11 PM UTC

    We have identified the issues, and rolling forward with the fix.

  3. monitoring Aug 05, 2026, 03:24 PM UTC

    We have rolled out the fix and monitoring for recovery.

  4. resolved Aug 05, 2026, 03:37 PM UTC

    Error rates on the single API are back to normal.

Read the full incident report →

Notice July 24, 2026 Degraded service: Address to address unplotted flows unavailable –

Started Jul 24, 2026, 11:00 PM UTC· resolved Jul 24, 2026, 11:00 PM UTC

  1. resolved Jul 25, 2026, 12:06 AM UTC

    We investigated errors affecting address-to-address un-plotted flows (if toggled on). Affected Forensics Web showed an error message, but were able to complete investigations. We suppressed the erroneous code and everything is now functional. All other services were unaffected.

Read the full incident report →

Minor July 17, 2026 Transaction Monitoring API might be experiencing some degradation 5h 23m US - API - Transaction Monitoring, EU - API - Transaction Monitoring

Started Jul 17, 2026, 07:00 PM UTC· resolved Jul 18, 2026, 12:24 AM UTC

  1. investigating Jul 17, 2026, 10:33 PM UTC

    We are investigating reports of 502 Bad Gateway errors.

  2. investigating Jul 17, 2026, 11:03 PM UTC

    We are continuing to investigate the issue.

Read the full incident report →

Critical July 17, 2026 Users unable to login and add/remove users from their organization. 4h 3m US - Forensics on Web, EU - Forensics on Web

Started Jul 17, 2026, 04:12 PM UTC· resolved Jul 17, 2026, 08:16 PM UTC

  1. identified Jul 17, 2026, 04:12 PM UTC

    We identified the issue and rolling back the changes to unblock.

  2. identified Jul 17, 2026, 04:13 PM UTC

    This affects web surfaces only. API access is still working as intended.

  3. identified Jul 17, 2026, 04:43 PM UTC

    The rollback unblocked certain login flows not all, the fix is continuing to propagate to unblock all flows.

  4. monitoring Jul 17, 2026, 04:58 PM UTC

    All user login and management flows are now working. We are continuing to monitor.

  5. resolved Jul 17, 2026, 08:16 PM UTC

    All green for the last few hours. Resolving.

Read the full incident report →

Minor July 17, 2026 Transaction Monitoring API degraded service 1h 40m US - API - Transaction Monitoring

Started Jul 17, 2026, 02:39 AM UTC· resolved Jul 17, 2026, 04:19 AM UTC

  1. investigating Jul 17, 2026, 02:39 AM UTC

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

  2. monitoring Jul 17, 2026, 03:23 AM UTC

    Service is back to 100%. Stuck workers were restarted and no lag is being noticed. Monitoring.

  3. resolved Jul 17, 2026, 04:19 AM UTC

    Services continue to remain healthy. Resolving.

Read the full incident report →