[BSC] - Fermi Hard Fork
Investigating - BSC's Fermi Hard Fork will take place on 1/14/2026 @ 02:00 UTC, and brings a number of improvements to the protocol. You can find the list of changes here:
https://www.bnbchain.org/en/blog/fermi-hard-fork-accelerates-bsc-to-0-45-second-block-times

The Fermi hard fork includes the following BEPs:

BEP-590: Extended Voting Rules for Fast Finality Stability
BEP-619: Short Block Interval Phase Three (0.45 seconds)
BEP-592: Non-Consensus Based Block-Level Access List
BEP-593: Incremental Snapshot
BEP-610: Implement EVM Super Instruction


We do not expect any downtime as a result of the hard fork. If you have any questions, please contact your CSM (Customer Success Manager).
Jan 12, 2026 - 07:18 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.

Uptime over the past 90 days. View historical uptime.
Blockdaemon Website Operational
Blockdaemon Web App Operational
Blockdaemon Universal API Operational
Event Steaming Operational
NFT API Operational
Blockdaemon RPC API Operational
90 days ago
100.0 % uptime
Today
Acala Native API Operational
Algorand Native API Operational
Aptos Native API Operational
Arbitrum Native API Operational
Avalanche Native API Operational
Base Native API Operational
Bitcoin Native API Operational
Bitcoin Cash Native API Operational
Celo Native API Operational
Cosmos Native API Operational
Cronos Native API Operational
Dogecoin Native API Operational
Ethereum Native API Operational
Evmos Native API Operational
Ink Native API Operational
Japan Open Chain Operational
90 days ago
100.0 % uptime
Today
Kusama Native API Operational
Karura Native API Operational
Litecoin Native API Operational
Monad Native API Operational
Near Native API Operational
Optimism Native API Operational
Polkadot Native API Operational
Polygon Native API Operational
Solana Native API Operational
Soneium Native API Operational
Stellar Native API Operational
Tezos Native API Operational
Tron Native API Operational
XRP Native API Operational
XLayer Native API Operational
Chain Watch Operational
90 days ago
100.0 % uptime
Today
$BTC - Bitcoin Operational
$BCH - Bitcoin Cash Operational
90 days ago
100.0 % uptime
Today
$DOGE - Dogecoin Operational
90 days ago
100.0 % uptime
Today
$DOT - Polkadot Operational
$ETH - Ethereum Operational
$LTC - Litecoin Operational
90 days ago
100.0 % uptime
Today
$OP - Optimism Operational
90 days ago
100.0 % uptime
Today
$POL - Polygon Operational
90 days ago
100.0 % uptime
Today
Protocols (Dedicated Nodes) Operational
90 days ago
100.0 % uptime
Today
Acala/Karura Operational
Algorand Operational
Aptos Operational
Arbitrum Operational
Arc Operational
Astar/Shiden Operational
Audius Operational
Avalanche Operational
Babylon Operational
Base Operational
Bitcoin Operational
Bitcoin Cash Operational
Bitcoin Lightning Operational
BNB Operational
Cardano Operational
Celestia Operational
Celestia Operational
Celo Operational
Cosmos Operational
Cronos Operational
Crypto.org Operational
Dash Operational
Dogecoin Operational
dYdX Operational
MultiversX (Elrond) Operational
Ethereum Operational
Ethereum Classic Operational
Evmos Operational
Erigon Operational
Gnosis Chain Operational
Flare Operational
Flow Operational
The Graph Operational
Ink Operational
Juno Operational
Kusama Operational
Litecoin Operational
Mobilecoin Operational
Moonbeam/Moonriver Operational
Near Operational
Neutron Operational
Optimism Operational
Osmosis Operational
Persistance Operational
Polkadot Operational
Polygon Operational
Provenance Operational
Pythnet Operational
Skale Operational
Solana Operational
Soneium Operational
Stellar Operational
SUI Operational
Tezos Operational
Unichain Operational
XLayer Operational
XRP Operational
XPLA Operational
Zcash Operational
Zetachain Operational
Tron Operational
90 days ago
100.0 % uptime
Today
Blockdaemon Validators Operational
90 days ago
100.0 % uptime
Today
Aptos Validator Operational
Audius Validator Operational
Avalanche Validator Operational
Babylon Validator Operational
Canton Validator Operational
Cardano Validator Operational
Celestia Validator Operational
Celo Validator Operational
Cosmos Validator Operational
Core Validator Operational
Crypto.org Validator Operational
dYdX Validator Operational
Dymension Validator Operational
Ethereum Validators Operational
Evmos Validator Operational
Flow Consensus Operational
Flow Verification Operational
Kusama Validator Operational
Gear Validator Operational
Ika Validator Operational
Livepeer Validator Operational
Moonbeam Validator Operational
Moonriver Validator Operational
Near Validator Operational
Neutron Validator Operational
Oasys Validator Operational
Osmosis Validator Operational
Polkadot Validator Operational
Polygon Validator Operational
Provenance Validator Operational
SKALE Validator Operational
Solana Validator Operational
Stacks Stacker Operational
Story Validator Operational
Stride Validator Operational
SUI Validator Operational
Tezos Baker Operational
The Graph Validator Operational
TON Validator Operational
Wemix Validator Operational
XPLA Validator Operational
XRP Validators Operational
Zetachain Validator Operational
Xinfin Operational
90 days ago
100.0 % uptime
Today
Zero Gravity Operational
90 days ago
100.0 % uptime
Today
Monad Operational
90 days ago
100.0 % uptime
Today
Staking API Operational
Avalanche Staking API Operational
BNB Staking API Operational
Cardano Staking API Operational
Cosmos Staking API Operational
Ethereum Staking API Operational
Near Staking API Operational
Polkadot Staking API Operational
Polygon Staking API Operational
Solana Staking API Operational
Staking Reporting API Operational
Avalanche Staking Reporting Operational
Cardano Staking Reporting Operational
Ethereum Staking Reporting Operational
NEAR Staking Reporting Operational
Polkadot Staking Reporting Operational
Polygon Staking Reporting Operational
Solana Staking Reporting Operational
Blockdaemon Wallet Operational
90 days ago
100.0 % uptime
Today
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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[Solana] - Mainnet upgrade to v3.0.14 Jan 19, 2026 10:00-16:00 UTC

Blockdaemon will update Solana mainnet nodes to v3.0.14 on 01/19/2026. We are updating our nodes due to a release from the Solana foundation. This update applies to all Blockdaemon Solana mainnet nodes, there will be planned downtime of up to 60 minutes per node. Please be aware that depending on the geographic location, some nodes may require more than 60 minutes to fully sync with the network after the upgrade.

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/anza-xyz/agave/releases/tag/v3.0.14
Posted on Jan 15, 2026 - 09:28 UTC

[Solana] - Testnet & Devnet to v3.1.6 Jan 19, 2026 10:00-12:00 UTC

Blockdaemon will update Solana Testnet & Devnet to v3.1.6 on 01/19/2026. We are updating our nodes due to a release from the Solana foundation. This update applies to all Blockdaemon Solana Testnet & Devnet nodes, there will be planned downtime of up to 10 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/anza-xyz/agave/releases/tag/v3.1.6
Posted on Jan 15, 2026 - 09:31 UTC
Jan 16, 2026
[Polkadot & Kusama] - Intermittent issues
Resolved - The latest update to Polkadot v1.21.0 has resolved the issue causing intermittent errors for RPC Requests. We will continue monitoring for signs of regression.

If you have any questions or need further assistance, please don't hesitate to contact your Customer Success Manager!
Jan 16, 09:52 UTC
Identified - We are currently experiencing intermittent issues across our Polkadot and Kusama nodes. Some users may experience delays or errors when making RPC requests. The issue is known in the polkadot codebase, which the Parity team is actively working to resolve.

If you have any questions or need further assistance, please don’t hesitate to contact your Customer Success Manager!
Aug 14, 14:34 UTC
[Polygon] - Nodes performance instability
Resolved - We are pleased to inform you that the issue affecting Polygon has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 16, 04:52 UTC
Investigating - We want to inform you that we are currently experiencing issues with our Polygon nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Polygon nodes.

We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments!

If you have any questions or concerns, please reach out to your Customer Success Manager.
Jan 8, 13:50 UTC
Jan 15, 2026
*Urgent* Aptos Mainnet upgrade to v1.39.2
Completed - The scheduled maintenance has been completed.
Jan 15, 12:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 12:00 UTC
Scheduled - Blockdaemon will update Aptos Mainnet nodes to v1.39.2 today 01/15/26. We are updating our nodes due to a release from the Aptos-foundation. This update applies to all Blockdaemon Aptos 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 Customer Success Manager.

If you want additional information please review the release notes here:
https://github.com/aptos-labs/aptos-core/releases/tag/aptos-node-v1.39.2
Jan 15, 08:25 UTC
[Maintenance] – System Update
Completed - The scheduled maintenance has been completed.
Jan 15, 12:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 14, 12:15 UTC
Scheduled - We will be performing a routine operating system upgrade today as part of our ongoing maintenance program. This update is intended to ensure continued stability, security, and alignment with supported platforms.

Services will be checked after each update to confirm everything is operating normally throughout the process.

The upgrade has been tested in development environments, and no downtime is expected as a result of this maintenance.

If you have any questions or concerns, please contact your Customer Success Manager or reach out to our servicedesk - support@blockdaemon.com
Thank You.
Jan 14, 12:12 UTC
[Moonbeam] - Upgrade to v0.49.3
Completed - The scheduled maintenance has been completed.
Jan 15, 12:02 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 11:00 UTC
Scheduled - Blockdaemon will update all Moonbeam nodes to v0.49.3 on 01/15/26. We are updating our nodes due to a release from the Moonbeam foundation. This update applies to all Blockdaemon Moonbeam nodes. There will be planned downtime of up to 10 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.

Please be aware, this update includes multiple releases. All release notes can be found here;
https://github.com/moonbeam-foundation/moonbeam/releases/tag/v0.49.3
https://github.com/moonbeam-foundation/moonbeam/releases/tag/v0.49.2
Jan 12, 16:25 UTC
*Urgent*[OP Superchains] - upgrade to OP-node v1.16.5 / OP-geth v1.101605.0
Completed - The scheduled maintenance has been completed.
Jan 15, 12:02 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 10:01 UTC
Scheduled - Blockdaemon will perform scheduled protocol upgrades for all OP Superchains, including Optimism, Base, Unichain, Ink, and Soneium, January 14th, 2026, at 10:00 UTC.
These updates include OP-node v1.16.5, and OP-geth v1.101605.0

Impact:
During the maintenance window, customers may experience up to 10 minutes of downtime per node while upgrades are applied.
All services will automatically resume normal operation once completed.

Additional Information:
This upgrade addresses bugs found in the upsteam Ethereum geth client
For protocol details please refer to the following release notes:
https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101605.0
https://github.com/ethereum/go-ethereum/releases/tag/v1.16.5

If you have any questions or concerns, please reach out to your Customer Success Manager.
Jan 15, 05:04 UTC
[Polkadot] - Update to Polkadot v1.21.0 & Sidecar API v20.13.3
Completed - The scheduled maintenance has been completed.
Jan 15, 12:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 10:00 UTC
Scheduled - Blockdaemon will update Westend, Kusama and Polkadot nodes to v1.21.0 and Sidecar API to v20.13.3 on 01/15/26. We are updating our nodes due to a release from the Parity foundation. This update applies to all Blockdaemon Westend, Kusama and Polkadot nodes, there will be planned downtime of up to 10 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/paritytech/polkadot-sdk/releases/tag/polkadot-stable2512
https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-stable2509-3
https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.3
https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.2
https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.1
https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.0
Jan 12, 15:59 UTC
[SUI] Mainnet Stall
Resolved - We are pleased to inform you that the issue affecting network stall on the SUI Mainnet has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 15, 01:57 UTC
Update - Blockdaemon is aware of a network stall on the SUI Mainnet. As per the recommendation of the SUI Foundation, we are temporarily halting our validator operations as a precautionary measure.

Walrus and Ika are also currently disrupted as a result of this stall. These protocols rely on the SUI network for coordination and settlement.

We are closely monitoring the situation across all affected services and will provide further updates as soon as more information becomes available.

If you have any questions, please reach out to your Customer Success Manager.
Jan 14, 23:23 UTC
Investigating - Blockdaemon is aware of a network stall on the SUI Mainnet. Per the recommendation of the SUI Foundation, we are temporarily halting our validator operations as a precautionary measure.

We are closely monitoring the situation and will provide further updates as soon as more information becomes available.

If you have any questions, please reach out to your Customer Success Manager.
Jan 14, 16:12 UTC
Jan 14, 2026
Jan 13, 2026
**Urgent**[Polygon] - Upgrade to Heimdal v0.5.6, Erigon v3.3.7 and Bor v2.5.7
Completed - The scheduled maintenance has been completed.
Jan 13, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 20:00 UTC
Scheduled - Blockdaemon will update Polygon mainnet nodes to Heimdall v0.5.6, Erigon v3.3.7 and Bor v2.5.7 on 1/13/2026. We are updating our nodes due to a critical release from the Polygon foundation. This update applies to all Blockdaemon Polygon nodes, there may be up to 10 minutes of downtime across our Polygon nodes.

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 Technical Account Manager.

If you want additional information please review the release notes here:
https://github.com/0xPolygon/heimdall-v2/releases/tag/v0.5.6
https://github.com/0xPolygon/bor/releases/tag/v2.5.7
https://github.com/0xPolygon/erigon/releases/tag/v3.3.7
Jan 13, 19:11 UTC
**Urgent**[NEAR] - Upgrade to 2.10.4
Completed - The scheduled maintenance has been completed.
Jan 13, 20:05 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 19:05 UTC
Scheduled - Blockdaemon will update Near mainnet nodes to v2.10.4 on 01/13/2026. We are updating our nodes due to a critical release from the Near foundation. This update applies to all Blockdaemon Near mainnet nodes, there will be planned downtime of up to 10 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/near/nearcore/releases/tag/2.10.4
Jan 13, 19:01 UTC
*Urgent* [Ethereum-Geth] - upgrade to v1.16.8
Completed - The scheduled maintenance has been completed.
Jan 13, 20:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 18:00 UTC
Scheduled - Blockdaemon will update all ethereum nodes running the Geth client to v1.16.8 on 01/13/26. We are updating our nodes due to a critical release from the Ethereum Foundation. This update applies to all Blockdaemon Ethereum-Geth Testnet and Mainnet nodes.

We do not anticipate any unexpected downtime other than the maintenance window described. If you have any questions or concerns please reach out to your Customer Support Manager.

As this is a sensitive release, the release will only be available after 16:00 UTC and will be available for review here;
https://github.com/ethereum/go-ethereum/releases/tag/v1.16.8
Jan 12, 14:03 UTC
*Urgent*[Polygon] - upgrade to heimdall v0.5.6
Completed - This upgrade has been cancelled and will take place in https://status.blockdaemon.com/incidents/16myt9jys6mb instead.
Jan 13, 19:13 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 17:30 UTC
Scheduled - Blockdaemon will update Polygon mainnet nodes to heimdall v0.5.6 on 1/13/2026. We are updating our nodes due to a critical release from the Polygon foundation. This update applies to all Blockdaemon Polygon nodes, there may be up to 10 minutes of downtime across our Polygon nodes.

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 Technical Account Manager.

If you want additional information please review the release notes here:
https://github.com/0xPolygon/heimdall-v2/releases/tag/v0.5.6
Jan 13, 17:00 UTC
Jan 12, 2026
*Urgent*[Polygon] - downgrade to heimdall v0.5.4
Completed - The scheduled maintenance has been completed.
Jan 12, 20:05 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 19:05 UTC
Scheduled - Blockdaemon will downgrade Polygon nodes to heimdall v0.5.4 on 1/12/2026 due to reported bugs in v0.5.5. There may be up to 10 minutes of downtime across our Polygon nodes.

If you want additional information please review the release notes here:
https://github.com/0xPolygon/heimdall-v2/releases/tag/v0.5.4
Jan 12, 19:03 UTC
*Urgent*[Cosmos] - upgrade to v25.3.0
Completed - The scheduled maintenance has been completed.
Jan 12, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 14:30 UTC
Scheduled - Blockdaemon will update Cosmos mainnet nodes to v25.3.0 on 1/12/2026. We are updating our nodes due to a release from the Cosmos foundation. This update applies to all Blockdaemon Cosmos nodes, there may be up to 15 minutes of downtime across our cosmos nodes.

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 Technical Account Manager.

If you want additional information please review the release notes here:
https://github.com/cosmos/gaia/releases/tag/v25.3.0
Jan 12, 08:01 UTC
*Urgent*[Polygon] - upgrade to heimdall v0.5.5
Completed - The scheduled maintenance has been completed.
Jan 12, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 15:00 UTC
Scheduled - Blockdaemon will update Polygon nodes to heimdall v20.5.5 on 1/12/2026. We are updating our nodes due to a critical security release from the Polygon foundation. This update applies to all Blockdaemon Polygon nodes, there may be up to 10 minutes of downtime across our Polygon nodes.

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 Technical Account Manager.

If you want additional information please review the release notes here:
https://github.com/0xPolygon/heimdall-v2/releases/tag/v0.5.5
Jan 12, 14:54 UTC
[Avalanche] - upgrade to v1.14.1
Completed - The scheduled maintenance has been completed.
Jan 12, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 10:00 UTC
Scheduled - Blockdaemon will update Avalanche mainnet and testnet nodes to v1.14.1 on 01/12/2026. We are updating our nodes due to a release from the Avalanche foundation. This update applies to all Blockdaemon Avalanche mainnet and testnet nodes, there will be planned downtime of up to 10 minutes per node.

We have tested the release and do not anticipate any downtime as a result of the update. If you have any questions or concerns please reach out to your Technical Account Manager.

If you want additional information please review the release notes here:
https://github.com/ava-labs/avalanchego/releases/tag/v1.14.1
Jan 8, 13:44 UTC
Jan 11, 2026

No incidents reported.

Jan 10, 2026

No incidents reported.

Jan 9, 2026

No incidents reported.

Jan 8, 2026
**Urgent**[Polygon] - Upgrade to Erigon v3.3.6 and Bor v2.5.6
Completed - The scheduled maintenance has been completed.
Jan 8, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 8, 10:00 UTC
Scheduled - Blockdaemon will update all Polygon Mainnet nodes to Erigon v3.3.6 and Bor v2.5.6 on January 08, 2026 at 10:00 UTC.
We are updating our nodes due to the official release for Polygon. There may be planned downtime of up to ten minutes.

Customer Impact
During the upgrade window, Polygon-based services hosted by Blockdaemon may be temporarily unavailable for up to ten minutes while nodes are restarted and updated. Customers may experience temporary errors, failed or delayed transaction submissions, and intermittent issues when querying Polygon network data until the upgrade is complete.

Additional Information
Blockdaemon has validated this release and does not anticipate unexpected disruptions beyond any stated downtime.


Release notes:
https://github.com/0xPolygon/erigon/releases/tag/v3.3.6
https://github.com/0xPolygon/bor/releases/tag/v2.5.6
Jan 8, 01:07 UTC
Jan 7, 2026
ETH2 Prysm Client Degradation Following Fusaka Upgrade Impacting L2 Networks
Resolved - We are pleased to inform you that this issue affecting Several Layer 2 networks has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 7, 16:57 UTC
Investigating - We are currently investigating an upstream issue introduced in the Ethereum Prysm (eth2) consensus client following the recent Fusaka network upgrade. This bug has caused unexpected behavior in the consensus layer and is producing downstream impact for services relying on Prysm nodes.

Several Layer 2 networks may be affected, including:
- Base
- Optimism
- Arbitrum
- Unichain
- Polygon
- Celo
- XLayer
- Ink

Depending on protocol and configuration, customers may experience disruptions such as delayed confirmations, degraded API performance, or unexpected consensus-related errors.

Our engineering teams are actively working with upstream Prysm maintainers and monitoring all impacted networks for instability.
We will provide further updates as more information becomes available.
Dec 4, 14:34 UTC
Ethereum Validator Performance Degradation
Resolved - We are pleased to inform you that the issue affecting Ethereum validators has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 7, 16:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 10, 10:59 UTC
Investigating - Blockdaemon is aware of an issue affecting Ethereum validators following the recent Fusaka hard fork, where certain Prysm-based validators are experiencing missing attestations and occasional missed blocks due to post-fork synchronization problems. The Prysm team has acknowledged the issue and has released updated guidance to address the syncing behavior.

In alignment with the Prysm team's recommendations, we are in the process of applying the required additional Prysm startup flag across all impacted validators to restore both attestation performance and block production stability.

We will continue to monitor the situation closely and verify validator health as the patch is deployed. Further updates will be provided as more information becomes available.

We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure stable and consistent validator operations.
Dec 4, 09:46 UTC
Ethereum Validator Attestation Issue
Resolved - We are pleased to inform you that the issue affecting Ethereum validators has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 7, 16:54 UTC
Investigating - Blockdaemon is aware of an issue affecting Ethereum validators following the recent upgrade to Prysm v7.1.0, where some Prysm-based validators are experiencing increased missed attestations. The issue appears to be impacting a subset of our infrastructure

Our engineering teams are actively investigating the issue and taking appropriate action

We will continue to monitor the situation closely and verify validator health as mitigation efforts are applied. Further updates will be provided as more information becomes available.

We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure stable and consistent validator operations
Dec 12, 09:48 UTC
[Cronos Archive nodes falling behind]
Resolved - An issue that caused Cronos archive nodes to fall behind network state has been successfully remediated. All affected nodes have been brought back into sync and validated across the network.

If you have any questions or experience any additional issues, please contact your Customer Success Manager.
Jan 7, 13:33 UTC
Investigating - We are currently aware of an issue where Cronos archive nodes are falling behind the latest block height. This appears to be a network-wide issue.
Our engineering team is actively investigating the root cause and working to restore full synchronization as quickly as possible.
Clients relying on Cronos archive nodes may experience temporary delays or service interruptions during this period.
We will provide updates as more information becomes available.
We apologize for the inconvenience and appreciate your patience.
Nov 14, 12:05 UTC
Polygon – Degraded RPC Performance
Resolved - We are pleased to inform you that the issue affecting Polygon PoS network has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 7, 13:20 UTC
Investigating - We are currently investigating an upstream issue affecting the Polygon PoS network, specifically the Bor (block production and execution) layer, where multiple Bor nodes across the ecosystem are experiencing stalled behavior.

This condition is resulting in degraded RPC availability for Polygon PoS across several infrastructure providers, including Blockdaemon.
The Polygon PoS chain itself remains live and continues to produce blocks. Block production is not halted.

Current Impact:
- Intermittent or degraded Polygon PoS RPC responses
- Potential delays or timeouts for read/write requests

Mitigation & Next Steps:
Our engineering team is actively monitoring the situation and coordinating with the Polygon core teams as mitigation efforts are underway.

We will continue to provide updates as more information becomes available or when service levels change.
Dec 17, 19:55 UTC
Jan 6, 2026
[Kusama] – Sidecar Staking Endpoint Error
Resolved - The issue has been resolved following an upgrade to Substrate API Sidecar v20.13.3. All affected services are operating normally.

If you have any questions or experience any additional issues, please contact your Customer Success Manager.
Jan 6, 17:50 UTC
Identified - Blockdaemon will perform an urgent update to the Substrate API Sidecar service, upgrading to v20.13.3, which includes fixes released by the Parity team. This update will be rolled out to all affected Kusama full nodes.

During the update, customers may experience brief service interruptions on their nodes. This downtime is required to apply the fix and restore normal service operation.

We have validated this release and expect the upgrade to fully resolve the incident without any additional impact beyond the brief interruptions noted above.

Further updates will be posted here as the rollout progresses. If you have any questions or concerns, please contact your Customer Success Manager.

Additional information:
https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.3
Jan 6, 16:48 UTC
Investigating - We are investigating an issue affecting the Kusama AssetHub Sidecar service.

The issue has been identified and is related to an upstream dependency. We are coordinating with Parity to address the problem.

The issue will remain until an update is released and deployed. We will provide further updates as more information becomes available.

If you have any questions or need further assistance, please don't hesitate to contact your Customer Success Manager!
Jan 5, 13:34 UTC
[Tron] Nile Testnet Nodes Stuck in Block
Resolved - We are pleased to inform you that the issue affecting Tron Nile Testnet nodes has been resolved, and the service is now fully operational.

We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter.

If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!

Thank you for your understanding!
Jan 6, 14:38 UTC
Update - We wanted to inform you that we are going to update the nodes to GreatVoyage-v4.8.1-build2. The nodes are expected to experience a brief downtime during the update.
Jan 6, 14:02 UTC
Investigating - We want to inform you that we are currently experiencing issues with our Tron Nile Testnet nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter block height issue with your Tron Nile Testnet nodes.

We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments!

If you have any questions or concerns, please reach out to your Customer Success Manager.
Jan 6, 13:35 UTC
[Stellar] - Testnet update to v25.0.0
Completed - The scheduled maintenance has been completed.
Jan 6, 12:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 10:01 UTC
Scheduled - Blockdaemon will update all Stellar Testnet nodes to Stellar Core v25.0.0, Stellar Horizon v25.0.0 and Stellar Soroban v25.0.0 on 01/06/26. We are updating our nodes due to an release from the Stellar foundation. This update applies to all Blockdaemon Stellar Testnet nodes, there will be planned downtime of up to 30 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 Service Manager.

If you want additional information please review the release notes here:
https://github.com/stellar/stellar-rpc/releases/tag/v25.0.0
https://github.com/stellar/stellar-core/releases/tag/v25.0.0
Dec 15, 18:57 UTC
[Stellar] - Mainnet update to v25.0.0
Completed - The scheduled maintenance has been completed.
Jan 6, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 10:00 UTC
Scheduled - Blockdaemon will update all Stellar Mainnet nodes to Stellar Core v25.0.0, Stellar Horizon v25.0.0 and Stellar Soroban v25.0.0 on 01/06/26. We are updating our nodes due to a release from the Stellar foundation. This update applies to all Blockdaemon Stellar Mainnet nodes, there will be planned downtime of up to 30 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 Service Manager.

If you want additional information please review the release notes here;
https://github.com/stellar/stellar-core/releases/tag/v25.0.0
https://github.com/stellar/stellar-rpc/releases/tag/v25.0.0
Dec 15, 18:42 UTC
[BSC Erigon] - upgrade mainnet to v1.4.3
Completed - The scheduled maintenance has been completed.
Jan 6, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 10:00 UTC
Scheduled - Blockdaemon will update all mainnet BSC Erigon RPC nodes to v1.4.3 on January 6th, 2026 at 10:00 AM UTC.

*Scheduled Downtime*
A brief service restart may occur during rollout. Requests during restart will receive temporary errors.

*Customer Action Required*
No Action Required. This upgrade improves service reliability.

*Changes Affecting Your Integration (RPC/API)*
• BEP-619: Implementation of Short Block Interval Phase Three, reducing the block interval to 0.45 seconds, improving network speed and finality.

*Validator & Rewards Impact*
• Protocol changes to lower the minimum slash amount and adjust other SystemContract limitations.

*Additional Information*
Blockdaemon has validated this release in our staging environment. We recommend implementing retry logic for requests during the maintenance window.

Release notes:
https://github.com/node-real/bsc-erigon/releases/tag/v1.4.3
https://forum.bnbchain.org/t/bnb-chain-roadmap-mainnet/936

Questions or concerns? Contact your Customer Success Manager or reach out to support@blockdaemon.com.
Dec 9, 21:23 UTC
[Xlayer] – Service Degradation
Resolved - This incident has been resolved.
Jan 6, 10:13 UTC
Investigating - Hello Team,

We wanted to let you know that a service degradation has been identified affecting your Xlayer node, which is currently unhealthy and several thousand blocks behind.

Our engineering team is actively investigating the situation and taking appropriate action to resolve the issue. We will continue to monitor the node closely and verify its health as mitigation efforts are applied. Further updates will be provided as more information becomes available.

We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure stable and reliable node operations.
Jan 1, 09:05 UTC
Jan 5, 2026
Jan 4, 2026

No incidents reported.

Jan 3, 2026

No incidents reported.

Jan 2, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage