Blockdaemon logo

Is Blockdaemon Down?

SaaSLive status, outages, and incident history

Partly. Some of Blockdaemon is down.

Blockdaemon is in a partial outage as of August 11, 2026. Some components are down and others are still running, so check the list below to see whether your region or feature is affected.

Partial OutageChecked 1h agoLive, rechecked every 60s2 active incidents
How we know: the official Blockdaemon status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Blockdaemon Component Status

The main Blockdaemon systems on this page. All 20 are operational right now.

1maintenance19operational
Blockdaemon RPC API » Arc Native API
Maintenance
Blockdaemon RPC API » Algorand Native API
Operational
Blockdaemon RPC API » Arbitrum Native API
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Blockdaemon RPC API » Avalanche Native API, Blockdaemon RPC API » Base Native API, Blockdaemon RPC API » Bitcoin Cash Native API, Blockdaemon RPC API » Bitcoin Native API, Blockdaemon RPC API » Celo Native API, Blockdaemon RPC API » Cosmos Native API, Blockdaemon RPC API » Cronos Native API, Blockdaemon RPC API » Dogecoin Native API, Blockdaemon RPC API » Ethereum Native API, Blockdaemon RPC API » Flow Native API, Blockdaemon RPC API » Ink Native API, Blockdaemon RPC API » Kusama Native API, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Blockdaemon Outages & Incidents

Incident history from the official Blockdaemon status page, including resolution updates.

Uptime history4 days observed
Aug 81.19% average · 4 days with incidentsAug 11
[Polkadot/Kusama/Westend] Sidecar API Deprecation NoticeScheduled for Aug 24, 2026 · 2h 0mScheduled

Parity, the maintainer of the Polkadot SDK, is deprecating the Substrate API Sidecar (substrate-api-sidecar)—the service that currently sits in front of Polkadot and Kusama nodes to simplify node access. It has been replaced by the Polkadot REST API, a rebuilt successor that offers the same core functionality. As a result, Blockdaemon will remove the Sidecar API from our dedicated nodes and API effective August 24, 2026. After this date, requests to the Sidecar endpoint will no longer be served. What you need to do The Polkadot REST API is broadly compatible with Sidecar, but the endpoint structure and some response formats differ. We recommend that you: Review the Polkadot REST API documentation and migration guide, and test it against your specific use cases before the cutover date. Migration Guide: https://github.com/paritytech/polkadot-rest-api/blob/main/docs/guides/MIGRATION.md Update any integrations that currently reference the Sidecar endpoint. References: https://docs.blockdaemon.com/docs/how-to-connect-to-polkadot#4-how-to-connect-via-rest-api https://docs.blockdaemon.com/docs/polkadot-via-polkadot-rest-api We're here to help Your Customer Success Manager is available to walk through the migration and discuss your specific setup, or you can reach our Support Team directly at support@blockdaemon.com.

**Urgent** [Algorand] - Upgrade Indexer to v.3.10.0 and Conduit v1.10.0Scheduled for Aug 13, 2026 · 1h 0mScheduled

We will be undergoing scheduled maintenance during this time. --- [2026-08-11T09:39:52.166Z] (scheduled) Blockdaemon will update Algorand indexer nodes to v3.10.0 and conduit to v1.10.0 on 08/13/2026 at 9:00 UTC. We are updating our nodes due to a release from the Algorand foundation. This update applies to all Blockdaemon Algorand Indexer nodes, there will be planned downtime of up to 15 minutes per node. We have tested the release and do not anticipate any unexpected downtime other than mentioned above as a result of the update. If you have any questions or concerns please reach out to your Customer Success Manager. If you want additional information please review the release notes here https://github.com/algorand/indexer/releases/tag/v3.10.0 https://github.com/algorand/conduit/releases/tag/v1.10.0

[Canton] Devnet Upgrade to Splice v0.7.1Scheduled for Aug 12, 2026 · 1h 0mScheduled

Blockdaemon will update all Canton Devnet nodes to Splice v0.7.1 on 08/12/2026 at 14:00 UTC. We are updating our nodes due to a release from the Canton foundation. This update applies to all Canton Devnet nodes; there will be planned downtime of up to 15 minutes per node. We have tested the release and do not anticipate any unexpected downtime other than mentioned above as a result of the update. If you have any questions or concerns, please reach out to your Customer Success Manager. If you want additional information, please review the release notes here: https://docs.canton.network/global-synchronizer/release-notes/splice#0-7-1

Live Blockdaemon Outage Reports

Problems reported by engineers using Blockdaemon. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Blockdaemon problems reported yet.

Are you seeing Blockdaemon problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Blockdaemon

Blockdaemon exposes 133 monitored components on its status page at status.blockdaemon.com — Blockdaemon Website, Algorand and Cardano Staking Reporting among them. Follow Blockdaemon downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Blockdaemon uptime at 98.30%. Response times, incident history, and SLA tracking for Blockdaemon are available on the PulsAPI dashboard.

Blockdaemon Status FAQ

Is Blockdaemon down right now?

PulsAPI checks Blockdaemon every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Blockdaemon status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Blockdaemon is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Blockdaemon recovers.

How do I check Blockdaemon uptime history?

PulsAPI tracks Blockdaemon uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 98.30%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Blockdaemon.

How fast does PulsAPI detect Blockdaemon outages?

PulsAPI polls the official Blockdaemon status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Blockdaemon components?

Yes. PulsAPI monitors 20 individual Blockdaemon components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Blockdaemon goes down?

Yes. Create a PulsAPI account and subscribe to Blockdaemon. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Blockdaemon status changes.

How do I report an issue with Blockdaemon to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Blockdaemon problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Blockdaemon?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Blockdaemon alongside up to 9 other services at pulsapi.com/signup.

Track Blockdaemon with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Blockdaemon status changes.

Start free trial