- Detected by Pingoru
- Apr 23, 2026, 08:37 AM UTC
- Resolved
- Apr 23, 2026, 08:59 AM UTC
- Duration
- 22m
Affected: US - API - Transaction Monitoring
Timeline · 4 updates
-
investigating Apr 23, 2026, 08:37 AM UTC
Delays in publishing webhooks
-
identified Apr 23, 2026, 08:40 AM UTC
We have identified the root cause, and are working on a fix.
-
monitoring Apr 23, 2026, 08:52 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 23, 2026, 08:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 03:34 PM UTC
- Resolved
- Apr 22, 2026, 03:34 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 22, 2026, 03:34 PM UTC
Summary A Red Canary alert ([THREAT-164]) flagged anomalous identity behavior for [email protected] — a successful Entra authentication from suspicious VPN infrastructure on 2026-04-21 at 22:59 UTC. What We Found The authentication was legitimate. Lisa confirmed she is based in Mexico City and her husband recently enabled a VPN on their home network for his personal reasons/requirements. All devices on the network — including her TRM machine — are routing through the VPN, causing her Entra sign-ins to appear from CA/NV USA instead of Mexico City where they are currently. - VPN provider: Private Internet Access (PIA) - Router: GL iNet (VPN configured at the router level) GCP audit logs showed no suspicious production activity from this user during the 72-hour lookback window. AUP Concern TRM's AUP prohibits VPNs on TRM-managed machines without an approved exception. The current configuration likely constitutes a violation, and all home network traffic may be passing through a third-party VPN. This raises data exposure concerns. Next Steps - Lisa created a separate SSID (or equivalent network segmentation) to exclude TRM devices from VPN routing - this is still being confirmed. Status: Closed — This AUP violation shouldn't constitute an incident, is being addressed with Lisa so her TRM traffic won't go through the 3rd party VPN going forward (although it's still tunneled by ZScaler)
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 04:19 PM UTC
- Resolved
- Apr 21, 2026, 08:30 PM UTC
- Duration
- 4h 10m
Affected: US - API - Wallet ScreeningUS - API - Transaction Monitoring
Timeline · 4 updates
-
investigating Apr 21, 2026, 04:34 PM UTC
We are currently investigating this issue.
-
investigating Apr 21, 2026, 04:34 PM UTC
We are continuing to investigate this issue.
-
monitoring Apr 21, 2026, 05:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 21, 2026, 08:30 PM UTC
All systems remain healthy, resolving the incident.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 01:12 PM UTC
- Resolved
- Apr 20, 2026, 01:50 PM UTC
- Duration
- 38m
Affected: EU - Forensics on Web
Timeline · 2 updates
-
identified Apr 20, 2026, 01:45 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Apr 20, 2026, 02:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 06:50 AM UTC
- Resolved
- Apr 08, 2026, 08:50 AM UTC
- Duration
- 2h
Affected: US - Forensics on Web
Timeline · 2 updates
-
identified Apr 08, 2026, 06:50 AM UTC
Co-Case Agent is currently unavailable due to an outage on a third-party provider.
-
resolved Apr 08, 2026, 03:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 07:21 PM UTC
- Resolved
- Apr 06, 2026, 07:31 PM UTC
- Duration
- 9m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
investigating Apr 06, 2026, 07:21 PM UTC
We are currently investigating this issue.
-
monitoring Apr 06, 2026, 07:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 06, 2026, 07:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 12:42 AM UTC
- Resolved
- Apr 01, 2026, 02:37 AM UTC
- Duration
- 1h 54m
Affected: US - Forensics on WebEU - Forensics on Web
Timeline · 4 updates
-
identified Apr 01, 2026, 12:42 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Apr 01, 2026, 01:14 AM UTC
Forensics data for Bitcoin address transfers is currently not updating in real time. Customers investigating Bitcoin transactions may see stale or incomplete transfer data when using the Forensics product.
-
monitoring Apr 01, 2026, 01:48 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 01, 2026, 02:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 02:44 AM UTC
- Resolved
- Mar 27, 2026, 04:40 AM UTC
- Duration
- 1h 56m
Affected: US - Forensics on WebEU - Forensics on Web
Timeline · 3 updates
-
identified Mar 27, 2026, 02:44 AM UTC
We are currently experiencing delays in Forensics address transfers for the following chains: Cardano, Cosmos, Elrond, Tezos, TON Protocol, Unichain, Stellar, and Ripple.
-
monitoring Mar 27, 2026, 03:15 AM UTC
Delay has been remediated; we are monitoring the situation closely.
-
resolved Mar 27, 2026, 04:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 04:06 PM UTC
- Resolved
- Mar 27, 2026, 02:04 PM UTC
- Duration
- 21h 58m
Affected: US - API - Transaction Monitoring
Timeline · 4 updates
-
investigating Mar 26, 2026, 05:10 PM UTC
We are currently investigating this issue.
-
monitoring Mar 26, 2026, 05:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 26, 2026, 05:53 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 27, 2026, 02:04 PM UTC
We are continuing to monitor for any further issues.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 12:07 AM UTC
- Resolved
- Mar 26, 2026, 01:41 AM UTC
- Duration
- 1h 33m
Affected: US - Forensics on WebUS - API - Transaction Monitoring
Timeline · 3 updates
-
investigating Mar 26, 2026, 12:07 AM UTC
We're experiencing an elevated level of API errors and are currently looking into the issue.
-
monitoring Mar 26, 2026, 01:24 AM UTC
We have fixed the networking issue and errors have resolved. We are actively monitoring.
-
resolved Mar 26, 2026, 01:41 AM UTC
The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 12:47 PM UTC
- Resolved
- Mar 24, 2026, 07:11 PM UTC
- Duration
- 6h 24m
Affected: US - API - Wallet Screening
Timeline · 2 updates
-
investigating Mar 24, 2026, 12:47 PM UTC
We are currently investigating this issue.
-
resolved Mar 24, 2026, 07:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 09:13 PM UTC
- Resolved
- Mar 24, 2026, 05:48 AM UTC
- Duration
- 8h 34m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
investigating Mar 23, 2026, 09:13 PM UTC
We are currently investigating this issue.
-
monitoring Mar 23, 2026, 11:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 24, 2026, 05:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 04:09 PM UTC
- Resolved
- Mar 13, 2026, 11:26 PM UTC
- Duration
- 7h 17m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
investigating Mar 13, 2026, 04:09 PM UTC
We are currently investigating increased error rates on WS API.
-
monitoring Mar 13, 2026, 04:24 PM UTC
All error rates are normal and we are monitoring the situation and root-causing the alert.
-
resolved Mar 13, 2026, 11:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 05:15 PM UTC
- Resolved
- Mar 10, 2026, 06:00 PM UTC
- Duration
- 44m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
investigating Mar 10, 2026, 05:26 PM UTC
We are investigating metrics indicating degraded WS API performance.
-
monitoring Mar 10, 2026, 05:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 11, 2026, 10:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 06:32 PM UTC
- Resolved
- Mar 06, 2026, 08:05 PM UTC
- Duration
- 1h 32m
Affected: US - Forensics on Web
Timeline · 3 updates
-
investigating Mar 06, 2026, 06:32 PM UTC
We are currently investigating this issue.
-
investigating Mar 06, 2026, 07:02 PM UTC
We are continuing to investigate this issue.
-
resolved Mar 06, 2026, 08:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 05:55 PM UTC
- Resolved
- Feb 27, 2026, 12:17 AM UTC
- Duration
- 6h 22m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
investigating Feb 26, 2026, 07:42 PM UTC
We are currently investigating this issue.
-
monitoring Feb 26, 2026, 07:51 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 27, 2026, 12:17 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 12:02 AM UTC
- Resolved
- Feb 25, 2026, 12:04 AM UTC
- Duration
- 2m
Affected: US - Forensics on WebEU - Forensics on Web
Timeline · 3 updates
-
investigating Feb 24, 2026, 05:40 PM UTC
We are currently investigating this issue.
-
monitoring Feb 25, 2026, 07:18 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 25, 2026, 05:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 08:47 PM UTC
- Resolved
- Feb 21, 2026, 08:30 PM UTC
- Duration
- —
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.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 02:06 AM UTC
- Resolved
- Feb 19, 2026, 09:12 PM UTC
- Duration
- 19h 6m
Affected: US - API - Wallet Screening
Timeline · 3 updates
-
monitoring Feb 19, 2026, 02:06 AM UTC
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.
-
monitoring Feb 19, 2026, 06:58 AM UTC
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.
-
resolved Feb 19, 2026, 09:12 PM UTC
Fixes have landed. All systems back to normal.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 04:23 PM UTC
- Resolved
- Feb 09, 2026, 05:12 PM UTC
- Duration
- 48m
Affected: US - Forensics on Web
Timeline · 4 updates
-
investigating Feb 09, 2026, 04:23 PM UTC
Issues with plotting/loading Graph Visualizer
-
identified Feb 09, 2026, 04:42 PM UTC
The issue has been identified and we are working on a fix.
-
monitoring Feb 09, 2026, 04:44 PM UTC
A fix has been rolled out and Graph Visualizer is restored. We will continue to monitor.
-
resolved Feb 09, 2026, 05:12 PM UTC
The issue has been resolved with all functionality restored.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 04:49 AM UTC
- Resolved
- Feb 06, 2026, 06:43 PM UTC
- Duration
- 13h 54m
Affected: US - API - BLOCKINT
Timeline · 4 updates
-
investigating Feb 06, 2026, 04:49 AM UTC
Seeing intermittent high error rates on WS APIs. Investigating the issue.
-
identified Feb 06, 2026, 05:59 AM UTC
We have identified the issue. We are looking in to resolving it. Currently, there are no net new errors on the APIs.
-
monitoring Feb 06, 2026, 09:22 AM UTC
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.
-
resolved Feb 06, 2026, 06:43 PM UTC
The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 04:12 PM UTC
- Resolved
- Feb 05, 2026, 01:06 AM UTC
- Duration
- 8h 53m
Affected: EU - Forensics on Web
Timeline · 5 updates
-
investigating Feb 04, 2026, 04:12 PM UTC
We are seeing slowness and some occasional errors in EU Forensics. We are currently investigating.
-
identified Feb 04, 2026, 04:28 PM UTC
We have identified the issue and working on a fix.
-
identified Feb 04, 2026, 05:54 PM UTC
All errors on Forensics in EU have been resolved. We are looking in to any slowness concerns.
-
monitoring Feb 04, 2026, 06:59 PM UTC
Risk indicator issues are resolved as well and we see improved performance. Will continue to monitor.
-
resolved Feb 05, 2026, 01:06 AM UTC
The issue is resolved.
Read the full incident report →
