Chainstack incident

Cronos Mainnet degraded performance

Major Resolved

Chainstack experienced a major incident on May 6, 2026 affecting Cronos Global Nodes (Cronos Mainnet) and Cronos Trader Nodes (Cronos Mainnet Archive (Chainstack Cloud, Frankfurt)), lasting 2h 25m. The incident has been resolved; the full update timeline is below.

Started: May 06, 2026, 12:30 AM UTC
Resolved: May 06, 2026, 02:55 AM UTC
Duration: 2h 25m
Detected by Pingoru: May 06, 2026, 12:30 AM UTC

Affected components

Cronos Global Nodes (Cronos Mainnet)Cronos Trader Nodes (Cronos Mainnet Archive (Chainstack Cloud, Frankfurt))

Update timeline

investigating May 06, 2026, 12:30 AM UTC

We are currently investigating this incident.
identified May 06, 2026, 01:42 AM UTC

We are continuing to work on a fix for this incident.
monitoring May 06, 2026, 02:09 AM UTC

We implemented a fix and are currently monitoring the result.
resolved May 06, 2026, 02:55 AM UTC

This incident has been resolved.

Looking to track Chainstack downtime and outages?

Pingoru polls Chainstack's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Chainstack reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Chainstack alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Chainstack for free

5 free monitors · No credit card required