Blockdaemon experienced a critical incident on August 31, 2026 affecting Cronos Native API and Cronos, lasting 23d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 31, 2026, 03:25 PM UTC
We want to inform you that we are currently experiencing issues with our Cronos nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Cronos nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments! If you have any questions or concerns, please reach out to your Customer Success Manager.
- monitoring Sep 03, 2026, 01:52 PM UTC
We’d like to share an update on this incident. The Cronos Network chain halt is a network-wide issue impacting the synchronization and availability of Cronos nodes. The Cronos team has advised that a network rule put in place during their incident response is still blocking connections. We continue to monitor the situation and will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding.
- resolved Sep 23, 2026, 04:41 PM UTC
We are pleased to inform you that the chain halt issue affecting the synchronization and availability of Cronos nodes has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!