Blockdaemon logo

Is Blockdaemon Down?

SaaSLive status, outages, and incident history

No. Blockdaemon is up right now.

Every monitored Blockdaemon system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Blockdaemon breaks

Blockdaemon is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Blockdaemon status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Blockdaemon Component Status

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

128operational
Blockdaemon RPC API » Algorand Native API
Operational
Blockdaemon RPC API » Arbitrum Native API
Operational
Blockdaemon RPC API » Arc Native API
Operational

125 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 113 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Blockdaemon Outages & Incidents

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

Ethereum Sepolia - Glamsterdam Hard Fork upgradeScheduled for Oct 1, 2026 · 1h 0mScheduled

Blockdaemon will update all Ethereum Sepolia nodes to be Glamsterdam Hard Fork comptaible on 10/01/2026, between 18:00 – 20:00 UTC. We are updating our nodes due to the Ethereum Glamsterdam hard fork. This update applies to all Blockdaemon Ethereum Sepolia nodes; there will be planned downtime of up to 10 minutes per node. 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/paradigmxyz/reth/releases/tag/v2.6.0 https://github.com/ethereum/go-ethereum/releases/tag/v1.17.6 https://github.com/nethermindeth/nethermind/releases#release-2.0.0

[Polygon] - Mainnet upgrade to Heimdal v0.12.1Scheduled for Sep 28, 2026 · 1h 0mScheduled

Blockdaemon will update Polygon mainnet nodes to Heimdall v0.12.1 on 09/28/2026. We are updating our nodes due to a release from the Polygon Foundation. This update applies to all Blockdaemon Polygon mainnet nodes, there may be up to 10 minutes of downtime across our Polygon mainnet nodes. If you have any questions or concerns, please reach out to your Customer Success Manager.

[Tempo] - Internal MaintenanceScheduled for Sep 28, 2026 · 2h 0mScheduled

Blockdaemon will be carrying out essential maintenance to the following Tempo Mainnet and Testnet nodes on 09/28/26. This update applies to all Blockdaemon Tempo Mainnet and Testnet 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

Blockdaemon Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Blockdaemon incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 37 days with incidentsSep 25

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.

Something wrong with Blockdaemon on your end?

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.66%. Response times, incident history, and SLA tracking for Blockdaemon are available on the PulsAPI dashboard.

Blockdaemon Status FAQ

Is Blockdaemon down right now?

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. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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.66%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Blockdaemon changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Blockdaemon outages?

PulsAPI reads the official Blockdaemon status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Blockdaemon components?

Yes. PulsAPI monitors 128 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 free account and subscribe to Blockdaemon: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Blockdaemon plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Blockdaemon with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services