Blockdaemon incident

[Cronos] Archive Nodes – Slow Synchronization

Minor Resolved View vendor source →

Blockdaemon experienced a minor incident on October 1, 2026 affecting Cronos, lasting 7d 3h. The incident has been resolved; the full update timeline is below.

Started
Oct 01, 2026, 10:20 AM UTC
Resolved
Oct 08, 2026, 01:33 PM UTC
Duration
7d 3h
Detected by Pingoru
Oct 01, 2026, 10:20 AM UTC

Affected components

Cronos

Update timeline

  1. investigating Oct 01, 2026, 10:20 AM UTC

    We want to inform you that we are currently experiencing issues with some Cronos node services. Specifically, our Cronos archive nodes are experiencing slow syncing, while full nodes are operating normally. As a result, you may encounter difficulties accessing the affected Cronos archive nodes. Our team is actively investigating the issue and working diligently to resolve it. 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 Account Manager.

  2. resolved Oct 08, 2026, 01:33 PM UTC

    We are pleased to inform you that the issue affecting Cronos node 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 Account Manager! Thank you for your understanding!