- Detected by Pingoru
- Dec 03, 2025, 02:20 PM UTC
- Resolved
- Dec 04, 2025, 05:09 AM UTC
- Duration
- 14h 49m
Affected: Event Steaming
Timeline · 2 updates
-
investigating Dec 03, 2025, 02:20 PM UTC
We are currently investigating an issue causing delays in event delivery for Ethereum Mainnet. Some customers may not be receiving expected event updates at this time. Our engineering team is actively working to restore normal service.
-
resolved Dec 04, 2025, 05:09 AM UTC
We are pleased to inform you that the issue affecting Ethereum 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!
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 11:16 AM UTC
- Resolved
- Nov 25, 2025, 11:37 AM UTC
- Duration
- 4d
Affected: Cardano Staking ReportingCardano Staking APICardano
Timeline · 2 updates
-
investigating Nov 21, 2025, 11:16 AM UTC
Blockdaemon is aware of an unexpected hard fork on the Cardano network that occurred on Cardano Mainnet earlier this morning. The Cardano Foundation and ecosystem teams are actively investigating the cause of the fork. Block production on the network has slowed, which may impact transactions and network responsiveness. We are upgrading all Blockdaemon Cardano nodes to cardano-node v10.5.2 immediately, as advised by the Cardano Foundation. We will continue to monitor the situation closely and provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience as we work to ensure continued network stability. For more information on the release please see the following release notes; https://github.com/IntersectMBO/cardano-node/releases/tag/10.5.2
-
resolved Nov 25, 2025, 11:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:14 PM UTC
- Resolved
- Nov 19, 2025, 01:02 PM UTC
- Duration
- 1d
Affected: Acala Native APIBlockdaemon Web AppAlgorand Native APIBlockdaemon Universal APIAptos Native APIArbitrum Native APIEvent SteamingAvalanche Native APIBase Native APIBitcoin Native APIBitcoin Cash Native APICelo Native APICosmos Native APICronos Native APIDogecoin Native APIEthereum Native APIEvmos Native APIInk Native APIJapan Open ChainKusama Native APIKarura Native APILitecoin Native APIMonad Native APINear Native APIOptimism Native APIPolkadot Native APIPolygon Native APISolana Native APISoneium Native APIStellar Native APITezos Native APITron Native APIXRP Native APIXLayer Native API
Timeline · 4 updates
-
investigating Nov 18, 2025, 12:14 PM UTC
We would like to inform you that a networking supplier is experiencing issues, may impact connectivity. We will monitor the situation, apply workarounds where possible and update throughout. You may also monitor the incident through their status page: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We apologise for any inconvenience this may cause and appreciate your patience and understanding. If you have any questions or need further assistance, please don’t hesitate to contact your Customer Success Manager.
-
identified Nov 18, 2025, 12:17 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 18, 2025, 02:31 PM UTC
Update: Cloudflare has identified the cause of the incident and is implementing a fix. We're monitoring for full resolution and will update as soon as the fix progresses.
-
resolved Nov 19, 2025, 01:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 11:18 AM UTC
- Resolved
- Nov 19, 2025, 03:18 PM UTC
- Duration
- 9d 4h
Affected: Polkadot Validator
Timeline · 2 updates
-
investigating Nov 10, 2025, 11:18 AM UTC
We would like to inform you that Polkadot is affected by an on chain issue resulting in reduction in staking rewards. Until a fix is deployed staking rewards are expected to be approximately 60% lower than normal. This issue is being worked on by the Parity Foundation and is expected to be resolved via a runtime update in the next few days. If you have any questions or concerns, please reach out to your Customer Success Manager.
-
resolved Nov 19, 2025, 03:18 PM UTC
We are pleased to inform you that the issue affecting Polkadot staking rewards 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 the matter is being resolved. 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!
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 06:07 AM UTC
- Resolved
- Nov 13, 2025, 06:03 AM UTC
- Duration
- 7d 23h
Affected: Ethereum Native API
Timeline · 2 updates
-
investigating Nov 05, 2025, 06:07 AM UTC
Blockdaemon will discontinue support for the Ethereum Holesky network following its official deprecation by the Ethereum Foundation. API services for Ethereum Holesky will be terminated on November 7, 2025. Customers currently using the Holesky network should migrate to the Hoodi network. Summary The Ethereum Foundation has announced the shutdown of the Holesky test network. Blockdaemon will align with this deprecation by terminating Holesky API services and transitioning to the new Hoodi test network. Old endpoint: https://svc.blockdaemon.com/ethereum/holesky/native New endpoint: https://svc.blockdaemon.com/ethereum/hoodi/native Additional Information For details on the Holesky network shutdown, please refer to: https://blog.ethereum.org/2025/09/01/holesky-shutdown-announcement If you have any questions or concerns, please reach out to your Customer Success Manager.
-
resolved Nov 13, 2025, 06:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 01:07 PM UTC
- Resolved
- Oct 20, 2025, 04:42 PM UTC
- Duration
- 3h 35m
Affected: Algorand Native API
Timeline · 4 updates
-
investigating Oct 20, 2025, 01:07 PM UTC
We are currently experiencing a degradation affecting the Algorand Indexer service via Blockdaemon RPC API. Users may be unable to retrieve the most recent Algorand block data, which can impact applications or integrations that rely on up-to-date blockchain information. Our engineering team is actively investigating the issue. Block indexing appears to be delayed, and recent blocks may not be accessible at this time. Further updates will be provided as the investigation progresses.
-
identified Oct 20, 2025, 01:25 PM UTC
We have identified the issue affecting access to the latest Algorand block data through our Indexer service. Our team is working on remediation and will provide further updates as recovery progresses.
-
monitoring Oct 20, 2025, 01:36 PM UTC
A fix has been applied, and block data has fully synced. We are monitoring the Algorand Indexer service to ensure stability and normal performance.
-
resolved Oct 20, 2025, 04:42 PM UTC
The Algorand Indexer service has fully recovered and block data is syncing as expected. The issue is resolved, and the service is operating normally.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 10:04 AM UTC
- Resolved
- Oct 20, 2025, 12:22 PM UTC
- Duration
- 2h 17m
Affected: Avalanche Staking APIBlockdaemon Web AppBNB Staking APICardano Staking APICosmos Staking APIEthereum Staking APINear Staking APIPolkadot Staking APIPolygon Staking APISolana Staking API
Timeline · 2 updates
-
monitoring Oct 20, 2025, 10:04 AM UTC
We wanted to inform you that due to an ongoing incident affecting Amazon Web Services (AWS), some of our services may experience temporary disruption or degraded performance. Our team is actively monitoring the situation and working closely with AWS to minimize any impact. https://health.aws.amazon.com/health/status At this time, there is no action required from your side. We will continue to provide updates as more information becomes available and normal operations are restored. Thank you for your understanding and patience. Best regards, The Blockdaemon Team
-
resolved Oct 20, 2025, 12:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 02:09 PM UTC
- Resolved
- Nov 14, 2025, 01:50 PM UTC
- Duration
- 29d 23h
Affected: XLayer Native APIXLayer
Timeline · 2 updates
-
identified Oct 15, 2025, 02:09 PM UTC
We have identified that the issue affecting xLayer Testnet is related to an underlying problem with the foundation. Our team is actively collaborating with the foundation's engineering team to work toward 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 understanding as we work with the foundation to resolve the matter. If you have any questions or need further assistance, please don’t hesitate to contact your Customer Success Manager! Thank you for your patience and support!
-
resolved Nov 14, 2025, 01:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 09:23 AM UTC
- Resolved
- Oct 09, 2025, 05:16 PM UTC
- Duration
- 7h 53m
Affected: Blockdaemon Web App
Timeline · 3 updates
-
investigating Oct 09, 2025, 09:23 AM UTC
We want to inform you that we are currently experiencing an issue with our web application product. Due to this issue, clients are unable to add dedicated RPC nodes to their portfolio. Our engineering team is actively investigating the issue and apologise for any inconvenience this may cause. We will keep you posted with any updates on the resolution progress. If you have any questions, please contact your customer success manager or reach out to [email protected] Thank you for your understanding!
-
investigating Oct 09, 2025, 09:24 AM UTC
We are continuing to investigate this issue.
-
resolved Oct 09, 2025, 05:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2025, 02:27 PM UTC
- Resolved
- Oct 02, 2025, 01:47 PM UTC
- Duration
- 23h 19m
Affected: Solana Staking ReportingSolana Staking APISolana Native APISolana ValidatorSolana
Timeline · 2 updates
-
investigating Oct 01, 2025, 02:27 PM UTC
As part of the stabilization process for Agave v3.0, the Solana Testnet will be halted on 2025-10-01 at 13:30 UTC. This is a scheduled and controlled halt to support the upgrade process. During this window, you will experience issues when attempting to access Solana Testnet nodes and related services. Validators and node operators are expected to stop voting at the scheduled time, and the cluster will remain halted until the restart is coordinated. Once restart instructions are published, we will act to return services. If you have any questions, please contact your Customer Success Manager.
-
resolved Oct 02, 2025, 01:47 PM UTC
We are pleased to inform you that the issue affecting Solana Testnet 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!
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 03:40 PM UTC
- Resolved
- Oct 01, 2025, 02:44 PM UTC
- Duration
- 1d 23h
Affected: Celo ValidatorCelo Native APICelo
Timeline · 3 updates
-
investigating Sep 29, 2025, 03:40 PM UTC
We want to inform you that we are currently experiencing issues with our Celo nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Celo 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.
-
monitoring Sep 30, 2025, 09:43 AM UTC
A fix has been implemented to address the degraded performance, and service has returned to normal. We are monitoring to ensure stability.
-
resolved Oct 01, 2025, 02:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 12:26 PM UTC
- Resolved
- Sep 30, 2025, 02:39 PM UTC
- Duration
- 1d 2h
Affected: XLayer Native APIXLayer
Timeline · 2 updates
-
investigating Sep 29, 2025, 12:26 PM UTC
We are currently investigating an issue affecting xLayer Testnet. Earlier today, xLayer Testnet underwent an unannounced chain fork which has caused a partial outage of our service on this network. This issue is limited to the xLayer Testnet environment only. Our team is actively assessing the changes introduced by the xLayer Testnet fork and working on the necessary adjustments to restore normal operation. Further updates will be provided as progress is made. 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.
-
resolved Sep 30, 2025, 02:39 PM UTC
The issue affecting the xLayer Testnet has been fully resolved. Services are now operating normally, and no further impact is expected.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2025, 10:17 AM UTC
- Resolved
- Sep 11, 2025, 11:27 AM UTC
- Duration
- 1d 1h
Affected: Polygon Staking APIPolygon Native APIPolygon
Timeline · 2 updates
-
investigating Sep 10, 2025, 10:17 AM UTC
Blockdaemon would like to make customers aware that Polygon mainnet is currently experiencing a network degredation. All nodes on the Polygon mainnet network are impacted. The foundation is currently investigating on this issue. If you have any questions or concerns please reach out to your Customer Success Manager.
-
resolved Sep 11, 2025, 11:27 AM UTC
We are pleased to inform you that the issue affecting Polygon 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!
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 01:39 PM UTC
- Resolved
- Sep 12, 2025, 08:23 AM UTC
- Duration
- 17d 18h
Affected: Near Native API
Timeline · 2 updates
-
investigating Aug 25, 2025, 01:39 PM UTC
We are currently experiencing syncing issues affecting Near archive nodes. Users may encounter delays or errors when submitting RPC requests. Our engineering team is actively investigating and working to resolve the issue. This incident impacts both dedicated Near archive nodes and the RPC API service. For further assistance, please contact your Customer Success Manager.
-
resolved Sep 12, 2025, 08:23 AM UTC
We are pleased to inform you that the issue affecting Near archive 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!
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 02:34 PM UTC
- Resolved
- Jan 16, 2026, 09:52 AM UTC
- Duration
- 154d 19h
Affected: $DOT - PolkadotPolkadot Staking ReportingPolkadot Staking APIKusama Native APIKusama ValidatorPolkadot Native APIPolkadot ValidatorKusamaPolkadot
Timeline · 2 updates
-
identified Aug 14, 2025, 02:34 PM UTC
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!
-
resolved Jan 16, 2026, 09:52 AM UTC
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!
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 11:43 AM UTC
- Resolved
- Aug 08, 2025, 05:30 PM UTC
- Duration
- 5h 46m
Affected: Tron Native API
Timeline · 2 updates
-
investigating Aug 08, 2025, 11:43 AM UTC
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 difficulties accessing your Tron Nile Testnet nodes 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.
-
resolved Aug 08, 2025, 05:30 PM UTC
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!
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2025, 11:41 PM UTC
- Resolved
- Aug 05, 2025, 11:53 AM UTC
- Duration
- 6d 12h
Affected: Blockdaemon Web App
Timeline · 3 updates
-
investigating Jul 29, 2025, 11:41 PM UTC
We want to inform you that we are currently experiencing issues with our Blockdaemon Web Application. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties launching your Dedicated 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.
-
monitoring Jul 30, 2025, 12:42 AM UTC
We would like to inform you that a fix has been implemented for the issue affecting Blockdaemon Web Application, and we are currently monitoring the service to ensure stability. We will provide further updates once the monitoring period is complete and the issue is fully resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience. If you have any questions or need assistance, please feel free to reach out to your Customer Success Manager! Thank you for your understanding!
-
resolved Aug 05, 2025, 11:53 AM UTC
We are pleased to inform you that the issue affecting Blockdaemon Web Application 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!
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2025, 04:27 PM UTC
- Resolved
- Jul 16, 2025, 10:10 AM UTC
- Duration
- 17h 43m
Affected: Blockdaemon Web App
Timeline · 2 updates
-
investigating Jul 15, 2025, 04:27 PM UTC
We want to inform you that we are currently experiencing an issue with our web application product. Due to this issue, clients are unable to view their newly deployed nodes until the nodes transitions from 'Syncing' to 'Running' state. Our engineering team is actively investigating the problem and working on deploying a fix as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you posted with any updates on the resolution progress. If you have any questions, please contact your customer success manager! Thank you for your understanding!
-
resolved Jul 16, 2025, 10:10 AM UTC
We are pleased to inform you that the issue affecting Web Application dashboard 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!
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2025, 09:24 AM UTC
- Resolved
- Aug 13, 2025, 11:09 AM UTC
- Duration
- 33d 1h
Affected: Polygon Staking ReportingPolygon Staking APIPolygon Native APIPolygon ValidatorPolygon
Timeline · 3 updates
-
investigating Jul 11, 2025, 09:24 AM UTC
We want to inform you that Polygon Mainnet is experiencing network instability. Our team is monitoring the issue and will advise when it stabilises. As a result, you may encounter difficulties accessing your Polygon Mainnet 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.
-
monitoring Jul 14, 2025, 10:16 AM UTC
We would like to inform you that a fix has been implemented for the issue affecting Polygon Mainnet, and we are currently monitoring the service to ensure stability. We will provide further updates once the monitoring period is complete and the issue is fully resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience. If you have any questions or need assistance, please feel free to reach out to your Customer Success Manager! Thank you for your understanding!
-
resolved Aug 13, 2025, 11:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2025, 02:58 PM UTC
- Resolved
- Jul 01, 2025, 09:44 PM UTC
- Duration
- 6h 46m
Affected: Acala/KaruraAlgorandAptosArbitrumBabylon ValidatorAudiusAvalancheBabylonBaseBitcoinBitcoin CashBitcoin LightningBNBEthereum ValidatorsCardanoCeloKusama ValidatorCosmosCronosCrypto.orgDashDogecoindYdXMultiversX (Elrond)Near ValidatorEthereumEthereum ClassicEvmosOsmosis ValidatorErigonPolkadot ValidatorPolygon ValidatorGnosis ChainFlareFlowSKALE ValidatorThe GraphSolana ValidatorJunoKusamaStride ValidatorLitecoinMobilecoinTON ValidatorNearNeutronXPLA ValidatorOptimismOsmosisPersistancePolkadotPolygonProvenancePythnetSkaleSolanaStellarSUITezosUnichainXRPXPLAZcashZetachain
Timeline · 3 updates
-
identified Jul 01, 2025, 02:58 PM UTC
We are aware of a cooling issue at a data centre in Amsterdam (AMS1), where ambient temperatures are elevated. Our team is closely monitoring the situation in coordination with the facility provider and will take further action if deemed necessary and appropriate. We will share updates as they become available.
-
monitoring Jul 01, 2025, 07:20 PM UTC
Ambient temperatures are now falling within AMS1. We believe that the risk of impact is over, but will continue to monitor the situation and provide updates until temperatures reach nominal levels.
-
resolved Jul 01, 2025, 09:44 PM UTC
Ambient temperatures at the AMS1 datacenter are now nominal once again per on-site monitoring. The facility provider has confirmed a solution was implemented and the cooling issue is now resolved. Blockdaemon's network and services remained available throughout the incident.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2025, 11:38 AM UTC
- Resolved
- Jul 01, 2025, 07:35 AM UTC
- Duration
- 19h 57m
Affected: Blockdaemon Web App
Timeline · 2 updates
-
investigating Jun 30, 2025, 11:38 AM UTC
We want to inform you that we are currently experiencing an issue with our web application product. Due to this issue, clients are unable to view their Nodes dashboard. Our engineering team is actively investigating the problem and working on deploying a fix as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you posted with any updates on the resolution progress. If you have any questions, please contact your customer success manager! Thank you for your understanding!
-
resolved Jul 01, 2025, 07:35 AM UTC
We are pleased to inform you that the issue affecting [Web application] - Nodes dashboard issue 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!
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2025, 09:34 AM UTC
- Resolved
- Jul 01, 2025, 03:12 PM UTC
- Duration
- 1d 5h
Affected: Blockdaemon Web App
Timeline · 2 updates
-
investigating Jun 30, 2025, 09:34 AM UTC
We want to inform you that we are currently experiencing an issue with our web application product. Due to this issue, some clients are unable to view their Ethereum staking dashboard. Our engineering team is actively investigating the problem and working on deploying a fix as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you posted with any updates on the resolution progress. If you have any questions, please contact your customer success manager! Thank you for your understanding!
-
resolved Jul 01, 2025, 03:12 PM UTC
We are pleased to inform you that the issue affecting our web application product 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!
Read the full incident report →