Blockdaemon Status
System status
Incident overview
Total incidents
19
Active now
2
Resolved
17
Avg. resolution
120h 39m
Recent incidents
View all →[Hyperliquid] - Degraded Performance
[Cronos] Archive Nodes – Slow Synchronization
[Stellar] - Testnet Network Halt
Degraded Performance - Avalanche Mainnet Native
[Cosmos] - Protocol wide chain halt
[Cosmos Hub] - Degraded Performance
[Solana] Testnet Network Halt
[Solana Mainnet] - Degraded Performance on Universal API
[Cronos] Service Halted
[Polkadot] - Westend Nodes Service Disruption
Frequently asked questions
Is Blockdaemon down right now?
Blockdaemon is currently experiencing issues with 2 active incidents. Current status: Degraded. Check the incident details above for more information.
What is Blockdaemon's current uptime?
Blockdaemon has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Blockdaemon's official status page data.
How many incidents has Blockdaemon had recently?
Blockdaemon has experienced 19 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 120h 39m. 2 incidents are currently active.
What components does Blockdaemon monitor?
DevHelm tracks 129 individual components for Blockdaemon, including Aptos Validator, Avalanche Staking API, Blockdaemon Website, Cardano Staking Reporting, Algorand Native API, and 124 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Blockdaemon outages?
You can subscribe to Blockdaemon's incident feed via Atom/RSS at devhelm.io/status/blockdaemon/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Blockdaemon as a dependency in your DevHelm workspace.
About Blockdaemon status monitoring
This page provides real-time operational status for Blockdaemon, powered by DevHelm's continuous monitoring infrastructure. We track Blockdaemon's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Blockdaemon status data is refreshed every 30 seconds. We currently track 129 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Blockdaemon in your stack
Get alerted when Blockdaemon has issues — before your users notice. Set up in 30 seconds.