In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 02, 2026 - 14:01 UTC
Nov 02, 2026 - 14:01 UTC
Scheduled - We are performing scheduled maintenance across our platform and node infrastructure today, Monday 2nd November.
This work includes routine updates to our underlying infrastructure and will be rolled out progressively across all supported protocols. During the window, some services may be briefly rescheduled or reconnect as updates are applied, but these events should be transparent to most customers.
Our engineering teams are actively monitoring throughout the maintenance and we will post an update once the work is complete. If you notice anything unexpected, please contact our servicedesk via support@blockdaemon.com
Nov 2, 2026 14:00 - Nov 3, 2026 02:00 UTC
This work includes routine updates to our underlying infrastructure and will be rolled out progressively across all supported protocols. During the window, some services may be briefly rescheduled or reconnect as updates are applied, but these events should be transparent to most customers.
Our engineering teams are actively monitoring throughout the maintenance and we will post an update once the work is complete. If you notice anything unexpected, please contact our servicedesk via support@blockdaemon.com
Nov 2, 2026 14:00 - Nov 3, 2026 02:00 UTC
Monitoring - Following our previous notices regarding the October 26–27 validator incident, we are providing the latest findings from our ongoing investigation, conducted alongside two independent external incident response firms.
The forensic scope evaluated full disk and log collections from the affected validator hosts, a full year of secrets-management audit logs, password vault access records, and endpoint telemetry. This analysis confirmed no intrusion, exfiltration, or persistence on our validator hosts. Furthermore, the review identified no unauthorized access to the affected keys within our secrets-management systems, and no access to or export of the keys from our password vaults between October 2025 and the date of the incident.
The investigation has established the origin of the exposure. The affected validator credentials were all generated between 2020 and 2022. Forensic analysis determined that the key material originated from a local copy on a corporate device assigned to a former employee. Endpoint telemetry confirms that an unauthorized transfer of data took place from the device to personal systems, which our analysis indicates contained the legacy key material.
Relevant on-chain indicators have been shared directly with the Solana Foundation, and all impacted customers have been notified and engaged. We will issue a formal, comprehensive Root Cause Analysis (RCA) report as soon as the investigation formally concludes.
Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Nov 01, 2026 - 18:54 UTC
The forensic scope evaluated full disk and log collections from the affected validator hosts, a full year of secrets-management audit logs, password vault access records, and endpoint telemetry. This analysis confirmed no intrusion, exfiltration, or persistence on our validator hosts. Furthermore, the review identified no unauthorized access to the affected keys within our secrets-management systems, and no access to or export of the keys from our password vaults between October 2025 and the date of the incident.
The investigation has established the origin of the exposure. The affected validator credentials were all generated between 2020 and 2022. Forensic analysis determined that the key material originated from a local copy on a corporate device assigned to a former employee. Endpoint telemetry confirms that an unauthorized transfer of data took place from the device to personal systems, which our analysis indicates contained the legacy key material.
Relevant on-chain indicators have been shared directly with the Solana Foundation, and all impacted customers have been notified and engaged. We will issue a formal, comprehensive Root Cause Analysis (RCA) report as soon as the investigation formally concludes.
Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Nov 01, 2026 - 18:54 UTC
Update - Update as of 10/29/2026
Our investigation into the recent validator event remains ongoing in close coordination with independent external forensic specialists. While a final root cause has not yet been formally concluded, findings to date point directly to a historical key generation practice that was discontinued and no longer exists in our environment. This historical practice was strictly limited in scope.
Importantly, external forensic findings to date confirm that our present infrastructure, controls, and active environments have not been breached, and no current systems were accessed during this event.
The containment of this incident reflects our underlying architecture. Our Software Development Lifecycle enforces protocol isolation by design, accounting for the unique technical requirements and operational mechanics of each network. This model includes segregated delivery teams, isolated source code, and most critically, separate and independent key management for each protocol.
We will continue to provide updates and will publish verified findings as soon as the investigation formally concludes. If you have any questions, our support channels remain available.
Full details, FAQ and live updates: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 30, 2026 - 00:04 UTC
Our investigation into the recent validator event remains ongoing in close coordination with independent external forensic specialists. While a final root cause has not yet been formally concluded, findings to date point directly to a historical key generation practice that was discontinued and no longer exists in our environment. This historical practice was strictly limited in scope.
Importantly, external forensic findings to date confirm that our present infrastructure, controls, and active environments have not been breached, and no current systems were accessed during this event.
The containment of this incident reflects our underlying architecture. Our Software Development Lifecycle enforces protocol isolation by design, accounting for the unique technical requirements and operational mechanics of each network. This model includes segregated delivery teams, isolated source code, and most critically, separate and independent key management for each protocol.
We will continue to provide updates and will publish verified findings as soon as the investigation formally concludes. If you have any questions, our support channels remain available.
Full details, FAQ and live updates: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 30, 2026 - 00:04 UTC
Update - Following our October 27 notice about exposed operator keys on a small subset of our validators, here is an update on our security review.
Working with external digital forensics partners, we have found no indicators of compromise across our broader infrastructure, and no indication that any other Blockdaemon products, services, protocols or validators are affected. Customer data and assets remain uncompromised, and no client data or sensitive information was accessed.
As previously noted, delegated SOL remains safe in delegators’ own stake accounts.
The incident is limited to the operational accounts identified in our initial notice. All impacted customers have been notified, so if you did not receive a notification, you were not impacted. If you believe you were, contact support@blockdaemon.com.
Beyond the deactivation and re-delegation steps already recommended, no further client action is required. We are maintaining active monitoring across our infrastructure. For help re-delegating stake or other questions, contact Blockdaemon support or see our FAQ.
Validator address: The new validator’s vote account is 9ntyW2ufs5hGECKLwhR4p7PuQhqAbfKdAwNoYbgXsExn (https://solscan.io/account/9ntyW2ufs5hGECKLwhR4p7PuQhqAbfKdAwNoYbgXsExn).
Look-alike addresses are circulating on-chain, so only use the address published on our incident page or sent to you directly by Blockdaemon. Never copy a validator address from your transaction history, and verify the full address, not just the first and last few characters, before signing.
Full details, FAQ and live updates: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 28, 2026 - 21:13 UTC
Working with external digital forensics partners, we have found no indicators of compromise across our broader infrastructure, and no indication that any other Blockdaemon products, services, protocols or validators are affected. Customer data and assets remain uncompromised, and no client data or sensitive information was accessed.
As previously noted, delegated SOL remains safe in delegators’ own stake accounts.
The incident is limited to the operational accounts identified in our initial notice. All impacted customers have been notified, so if you did not receive a notification, you were not impacted. If you believe you were, contact support@blockdaemon.com.
Beyond the deactivation and re-delegation steps already recommended, no further client action is required. We are maintaining active monitoring across our infrastructure. For help re-delegating stake or other questions, contact Blockdaemon support or see our FAQ.
Validator address: The new validator’s vote account is 9ntyW2ufs5hGECKLwhR4p7PuQhqAbfKdAwNoYbgXsExn (https://solscan.io/account/9ntyW2ufs5hGECKLwhR4p7PuQhqAbfKdAwNoYbgXsExn).
Look-alike addresses are circulating on-chain, so only use the address published on our incident page or sent to you directly by Blockdaemon. Never copy a validator address from your transaction history, and verify the full address, not just the first and last few characters, before signing.
Full details, FAQ and live updates: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 28, 2026 - 21:13 UTC
Identified - Between 26 and 27 October, Blockdaemon identified that operator keys for a small set of our oldest running Solana validators were compromised. The attacker was able to change the withdrawal authority on the impacted validators and move a limited amount of operational assets from their operational accounts.
Your delegated SOL is safe. There is no indication of loss or risk to staked principal. Delegated SOL remains in each delegator’s own stake account and was not moved.
Reward impact: Because we cannot fund the voting accounts on the compromised validators, they will not earn rewards starting with epoch 1070.
Recommended action: The impacted validators must be replaced. A new validator is being prepared, and we will post its details here as soon as it is available. We are working directly with affected customers to move stakes to newly created validators quickly and minimise gaps in rewards.
If you need help deactivating, withdrawing or re-delegating, please contact Blockdaemon support - support@blockdaemon.com
Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 28, 2026 - 10:46 UTC
Your delegated SOL is safe. There is no indication of loss or risk to staked principal. Delegated SOL remains in each delegator’s own stake account and was not moved.
Reward impact: Because we cannot fund the voting accounts on the compromised validators, they will not earn rewards starting with epoch 1070.
Recommended action: The impacted validators must be replaced. A new validator is being prepared, and we will post its details here as soon as it is available. We are working directly with affected customers to move stakes to newly created validators quickly and minimise gaps in rewards.
If you need help deactivating, withdrawing or re-delegating, please contact Blockdaemon support - support@blockdaemon.com
Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Oct 28, 2026 - 10:46 UTC
Identified - We have identified an issue affecting Solana, and our team is actively working on a resolution.
We will keep you informed and share updates as progress is made. We sincerely apologize for any inconvenience this may be causing and appreciate your patience as we work to resolve the matter.
If you have any questions or need further assistance, please don’t hesitate to contact your Account Manager!
Thank you for your understanding!
Oct 26, 2026 - 15:19 UTC
We will keep you informed and share updates as progress is made. We sincerely apologize for any inconvenience this may be causing and appreciate your patience as we work to resolve the matter.
If you have any questions or need further assistance, please don’t hesitate to contact your Account Manager!
Thank you for your understanding!
Oct 26, 2026 - 15:19 UTC
About This Site
We continuously monitor the status of the Blockdaemon.com and all related services. If there are any interruptions in our service, an incident will be raised here.
Blockdaemon Website
Operational
Blockdaemon Web App
Under Maintenance
Blockdaemon Universal API
Under Maintenance
Event Streaming
Operational
Blockdaemon RPC API
Under Maintenance
Algorand Native API
Under Maintenance
Arbitrum Native API
Under Maintenance
Arc Native API
Under Maintenance
Avalanche Native API
Under Maintenance
Base Native API
Under Maintenance
Bitcoin Native API
Under Maintenance
Bitcoin Cash Native API
Under Maintenance
Celo Native API
Under Maintenance
Cosmos Native API
Under Maintenance
Cronos Native API
Under Maintenance
Dogecoin Native API
Under Maintenance
Ethereum Native API
Under Maintenance
Flow Native API
Under Maintenance
Hyperliquid Native API
Under Maintenance
Ink Native API
Under Maintenance
Kusama Native API
Under Maintenance
Litecoin Native API
Under Maintenance
Monad Native API
Under Maintenance
Near Native API
Under Maintenance
Optimism Native API
Under Maintenance
Polkadot Native API
Under Maintenance
Polygon Native API
Under Maintenance
Robinhood Chain
Under Maintenance
Solana Native API
Under Maintenance
Soneium Native API
Under Maintenance
Stellar Native API
Under Maintenance
Tempo Native API
Under Maintenance
Tron Native API
Under Maintenance
XLayer Native API
Under Maintenance
XRP Native API
Under Maintenance
Chain Watch
Under Maintenance
$BTC - Bitcoin
Under Maintenance
$BCH - Bitcoin Cash
Under Maintenance
$DOGE - Dogecoin
Under Maintenance
$DOT - Polkadot
Under Maintenance
$ETH - Ethereum
Under Maintenance
$LTC - Litecoin
Under Maintenance
$OP - Optimism
Under Maintenance
$POL - Polygon
Under Maintenance
$XLM - Stellar
Under Maintenance
Protocols (Dedicated Nodes)
Under Maintenance
Algorand
Under Maintenance
Aptos
Under Maintenance
Arbitrum
Under Maintenance
Arc
Under Maintenance
Avalanche
Under Maintenance
Babylon
Under Maintenance
Base
Under Maintenance
Bitcoin
Under Maintenance
Bitcoin Cash
Under Maintenance
BNB
Under Maintenance
Botanix
Under Maintenance
Canton
Operational
Cardano
Under Maintenance
Cosmos
Under Maintenance
Cronos
Under Maintenance
Dogecoin
Under Maintenance
Ethereum
Under Maintenance
Flow
Under Maintenance
Hyperliquid
Under Maintenance
Kusama
Under Maintenance
Linea
Under Maintenance
Litecoin
Under Maintenance
Near
Under Maintenance
Optimism
Under Maintenance
Polkadot
Under Maintenance
Polygon
Under Maintenance
Provenance
Under Maintenance
Skale
Under Maintenance
Solana
Under Maintenance
Soneium
Under Maintenance
Stellar
Under Maintenance
Story
Under Maintenance
SUI
Under Maintenance
Tron
Under Maintenance
Unichain
Under Maintenance
XLayer
Under Maintenance
XRP
Under Maintenance
zkSync
Under Maintenance
Blockdaemon Validator
Operational
Aptos Validator
Operational
Avalanche Validator
Operational
Babylon Validator
Operational
Canton Validator
Operational
Cardano Validator
Operational
Cosmos Validator
Operational
Core Validator
Operational
Crypto.org Validator
Operational
dYdX Validator
Operational
Ethereum Validators
Operational
Flow Consensus
Operational
Flow Verification
Operational
Gear Validator
Operational
Ika Validator
Operational
Kusama Validator
Operational
Monad Validator
Operational
Near Validator
Operational
Polkadot Validator
Operational
Polygon Validator
Operational
Provenance Validator
Operational
SKALE Validator
Operational
Solana Validator
Operational
Stacks Stacker
Operational
Story Validator
Operational
SUI Validator
Operational
Tempo Validator
Operational
TON Validator
Operational
Wemix Validator
Operational
XRP Validators
Operational
Zero Gravity
Operational
Arc Validator
Operational
Staking API
Under Maintenance
Avalanche Staking API
Under Maintenance
BNB Staking API
Under Maintenance
Cardano Staking API
Under Maintenance
Cosmos Staking API
Under Maintenance
Ethereum Staking API
Under Maintenance
Near Staking API
Under Maintenance
Polkadot Staking API
Under Maintenance
Polygon Staking API
Under Maintenance
Solana Staking API
Under Maintenance
Staking Reporting API
Under Maintenance
Cardano Staking Reporting
Under Maintenance
Cosmos Staking Reporting
Under Maintenance
Ethereum Staking Reporting
Under Maintenance
NEAR Staking Reporting
Under Maintenance
Polkadot Staking Reporting
Under Maintenance
Polygon Staking Reporting
Under Maintenance
Solana Staking Reporting
Under Maintenance
Blockdaemon Wallet
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
[Near] - Upgrade to Nearcore v2.14.0 Nov 3, 2026 10:00-11:00 UTC
Blockdaemon will update Near mainnet nodes to v2.14.0 on 11/03/2026. We are updating our nodes due to a release from the Near foundation. This update applies to all Blockdaemon Near mainnet 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 Account Manager.
If you want additional information please review the release note here:
https://github.com/near/nearcore/releases/tag/2.14.0
Posted on Oct 27, 2026 - 09:28 UTC
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 Account Manager.
If you want additional information please review the release note here:
https://github.com/near/nearcore/releases/tag/2.14.0
Posted on Oct 27, 2026 - 09:28 UTC
[Canton] - Testnet Network-Wide Topology Freeze (Upstream Event) Nov 3, 2026 14:00 - Nov 4, 2026 14:00 UTC
The Canton network is applying a topology freeze on Testnet in preparation for the Logical Synchronizer Upgrade (LSU). This is a network-wide event coordinated by the Canton Foundation, not Blockdaemon maintenance.
Window: November 03, 2026, 14:00 UTC to November 04, 2026, 14:00 UTC (until after the LSU completes; may extend slightly)
Impact:
Transactions continue to work normally.
Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads.
Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted.
If you have any questions or concerns please reach out to your account managers.
Posted on Oct 19, 2026 - 12:18 UTC
Window: November 03, 2026, 14:00 UTC to November 04, 2026, 14:00 UTC (until after the LSU completes; may extend slightly)
Impact:
Transactions continue to work normally.
Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads.
Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted.
If you have any questions or concerns please reach out to your account managers.
Posted on Oct 19, 2026 - 12:18 UTC
[xLayer] - Mainnet upgrade to xlayer-reth v0.0.7.3 and op-node xlayer v0.1.7 Nov 4, 2026 10:00-11:00 UTC
Blockdaemon will update xLayer mainnet nodes to xlayer-reth v0.0.7.3 and op-node xlayer v0.1.7 on 11/04/2026 between 10:00 UTC and 11:00 UTC. We are updating our nodes due to a release from the xLayer foundation. This update applies to all Blockdaemon xLayer mainnet 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 Account Manager.
If you want additional information please review the release notes here:
https://github.com/okx/xlayer-reth/releases/tag/v0.0.7.3
https://github.com/okx/optimism/releases/tag/xlayer%2Fv0.1.7
Posted on Oct 30, 2026 - 17:58 UTC
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 Account Manager.
If you want additional information please review the release notes here:
https://github.com/okx/xlayer-reth/releases/tag/v0.0.7.3
https://github.com/okx/optimism/releases/tag/xlayer%2Fv0.1.7
Posted on Oct 30, 2026 - 17:58 UTC
**Urgent**[Babylon]- Upgrade to testnet v4.7.0 Nov 4, 2026 11:45-12:45 UTC
Blockdaemon will update Babylon testnet nodes to v4.7.0 on 11/04/2026. We are updating our nodes due to a release from the Babylon foundation. This update applies to all Blockdaemon Babylon 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 Account Manager.
If you want additional information please review the release note here:
https://github.com/babylonlabs-io/babylon/releases/tag/v4.7.0
Posted on Nov 02, 2026 - 17:25 UTC
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 Account Manager.
If you want additional information please review the release note here:
https://github.com/babylonlabs-io/babylon/releases/tag/v4.7.0
Posted on Nov 02, 2026 - 17:25 UTC
**Urgent**[Canton] - Testnet Upgrade to Splice v0.9.4 Nov 4, 2026 14:00-15:00 UTC
Blockdaemon will update all Canton Testnet nodes to Splice v0.9.4 on 11/04/2026 at 14:00 UTC. We are updating our nodes due to a release from the Canton foundation. This update applies to all Canton 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.
If you want additional information, please review the release notes here:
https://docs.canton.network/global-synchronizer/release-notes/splice#0-9-4
Posted on Nov 02, 2026 - 14:27 UTC
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-9-4
Posted on Nov 02, 2026 - 14:27 UTC
**Urgent**[Canton] - Devnet Upgrade to Splice v0.10.0 Nov 4, 2026 14:00-15:00 UTC
Blockdaemon will update all Canton Devnet nodes to Splice v0.10.0 on 11/04/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-10-0
Posted on Nov 02, 2026 - 14:27 UTC
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-10-0
Posted on Nov 02, 2026 - 14:27 UTC
**Urgent**[Babylon]- Upgrade to mainnet v4.7.0 Nov 5, 2026 11:45-12:45 UTC
Blockdaemon will update Babylon mainnet nodes to v4.7.0 on 11/05/2026. We are updating our nodes due to a release from the Babylon foundation. This update applies to all Blockdaemon Babylon mainnet 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 Account Manager.
If you want additional information please review the release note here:
https://github.com/babylonlabs-io/babylon/releases/tag/v4.7.0
Posted on Nov 02, 2026 - 17:25 UTC
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 Account Manager.
If you want additional information please review the release note here:
https://github.com/babylonlabs-io/babylon/releases/tag/v4.7.0
Posted on Nov 02, 2026 - 17:25 UTC
[Canton] - Mainnet Network-Wide Topology Freeze (Upstream Event) Nov 6, 2026 14:00 - Nov 7, 2026 14:00 UTC
The Canton network is applying a topology freeze on Mainnet in preparation for the Logical Synchronizer Upgrade (LSU). This is a network-wide event coordinated by the Canton Foundation, not Blockdaemon maintenance.
Window: November 06, 2026, 14:00 UTC to November 07, 2026, 14:00 UTC (until after the LSU completes; may extend slightly)
Impact:
Transactions continue to work normally.
Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads.
Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted.
If you have any questions or concerns please reach out to your account managers.
Posted on Oct 19, 2026 - 12:20 UTC
Window: November 06, 2026, 14:00 UTC to November 07, 2026, 14:00 UTC (until after the LSU completes; may extend slightly)
Impact:
Transactions continue to work normally.
Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads.
Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted.
If you have any questions or concerns please reach out to your account managers.
Posted on Oct 19, 2026 - 12:20 UTC