Live  /  Chainalysis  /  Incident

Chainalysis: Cronos Data Delay

Chainalysis · chainalysis.comMinor incidentResolved2026-09-01 20:09 UTC
Public — what happened

Summary

Chainalysis reported a minor incident in which some Cronos data in its KYT and Reactor products could show as out of date, beginning on 2026-09-01 at 20:09 UTC. The company explained that the Cronos network had been stopped on August 30 after what it described as a DeFi-related attack and then reverted to block 90896189. Chainalysis said that while it was reloading Cronos data after the network restarted, it found further processing problems. The incident was listed as identified, with a resolution time recorded of 2026-09-03 at 05:42.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 37, 2026, our weekly internet health report.

The full archive is on the Chainalysis status & history page.

Related: Chainalysis status & history. SquidGrid is not affiliated with Chainalysis.