Live / Chainalysis / Incident
Chainalysis: Sentinel alerting data delays
Chainalysis · chainalysis.comMinor incidentResolved2026-10-09 21:57 UTC
Public — what happened
Summary
Chainalysis reported a minor incident on October 9, 2026, starting at 20:40 UTC, in which the data pipelines behind its Sentinel alerting feature were running behind. The company said that alert rules and risk settings created or changed recently might not apply until the pipelines caught up, while alerts already in place kept working from data processed earlier. Chainalysis stated that no data was lost or damaged, and it did not give a cause. The incident was marked resolved at 21:57 the same day.
Affected
Sentinel
Timeline
- Started — 2026-10-09 20:40 UTC
- Investigating — 2026-10-09 20:40 UTC
- Resolved — 2026-10-09 21:57 UTC · 1h 17m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Chainalysis against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Chainalysis: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Chainalysis report →
More from Chainalysis
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.