Blockdaemon Outage History

Blockdaemon is up right now

Pingoru has recorded 65 incidents for Blockdaemon: 60 in the last 12 months and 18 in the last 90 days.

Source: status.blockdaemon.com

65incidents recorded
60last 12 months
18last 90 days
5 daystypical duration
Incidents per month
0510AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov100%
Pingoru began tracking Blockdaemon in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026248 of 720 (7%)
May 2026470 of 744 (9%)
June 202620 of 720 (0%)
July 20269100 of 744 (13%)
August 20268450 of 744 (61%)
September 20266413 of 720 (57%)
October 20264463 of 744 (62%)
November 2026026 of 26 (100%)

Incidents, newest first

Minor October 15, 2026 [Hyperliquid] - Degraded Performance 6d 19h Hyperliquid Native API

Started Oct 15, 2026, 02:08 PM UTC· resolved Oct 22, 2026, 09:22 AM UTC

  1. investigating Oct 15, 2026, 02:08 PM UTC

    We want to inform you that we are currently experiencing issues with our Hyperliquid nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Hyperliquid 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 Account Manager.

  2. monitoring Oct 16, 2026, 04:21 PM UTC

    We would like to inform you that a fix has been implemented for the issue affecting Hyperliquid nodes, 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 Account Manager! Thank you for your understanding!

  3. resolved Oct 22, 2026, 09:22 AM UTC

    We are pleased to inform you that the issue affecting Hyperliquid 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 Account Manager! Thank you for your understanding!

Read the full incident report →

Minor October 1, 2026 [Cronos] Archive Nodes – Slow Synchronization 7d 3h Cronos

Started Oct 01, 2026, 10:20 AM UTC· resolved Oct 08, 2026, 01:33 PM UTC

  1. investigating Oct 01, 2026, 10:20 AM UTC

    We want to inform you that we are currently experiencing issues with some Cronos node services. Specifically, our Cronos archive nodes are experiencing slow syncing, while full nodes are operating normally. As a result, you may encounter difficulties accessing the affected Cronos archive nodes. Our team is actively investigating the issue and working diligently to resolve it. 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 Account Manager.

  2. resolved Oct 08, 2026, 01:33 PM UTC

    We are pleased to inform you that the issue affecting Cronos node 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 Account Manager! Thank you for your understanding!

Read the full incident report →

Minor September 29, 2026 [Stellar] - Testnet Network Halt 1h 34m Stellar Native API, Stellar

Started Sep 29, 2026, 07:44 PM UTC· resolved Sep 29, 2026, 09:18 PM UTC

  1. investigating Sep 29, 2026, 07:44 PM UTC

    We want to inform you that we are currently experiencing issues with our Stellar Testnet Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Stellar 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.

  2. resolved Sep 29, 2026, 09:18 PM UTC

    We are pleased to inform you that the issue affecting Stellar 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 Account Manager.

Read the full incident report →

Minor September 23, 2026 Degraded Performance - Avalanche Mainnet Native 4h 25m Avalanche Validator, Avalanche Native API, Avalanche

Started Sep 23, 2026, 05:16 AM UTC· resolved Sep 23, 2026, 09:41 AM UTC

  1. identified Sep 23, 2026, 05:16 AM UTC

    We are currently investigating an issue affecting Avalanche Mainnet Native RPC, Archive, and Validator services. As a result, some requests to these endpoints may return errors or fail intermittently. A fix has been identified and is being rolled out. We will also be carrying out a brief maintenance window to complete this rollout across the nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. resolved Sep 23, 2026, 09:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 22, 2026 [Cosmos] - Protocol wide chain halt 1d 21h Cosmos Staking API, Cosmos Validator, Cosmos Native API, Cosmos and 1 more

Started Sep 22, 2026, 11:35 AM UTC· resolved Sep 24, 2026, 08:55 AM UTC

  1. identified Sep 22, 2026, 11:35 AM UTC

    We have identified that the issue affecting Cosmos 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!

  2. resolved Sep 24, 2026, 08:55 AM UTC

    We are pleased to inform you that the issue affecting Cosmos 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 →

Minor September 8, 2026 [Cosmos Hub] - Degraded Performance 18h 54m Cosmos Native API, Cosmos

Started Sep 08, 2026, 11:21 PM UTC· resolved Sep 09, 2026, 06:16 PM UTC

  1. identified Sep 08, 2026, 11:21 PM UTC

    We have identified an issue affecting our Cosmos Hub API nodes, full nodes, and archive nodes following a recent network upgrade. Our team has identified the root cause and is actively working on recovery. We will post updates as they become available. We apologize for the inconvenience and appreciate your patience and understanding. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. resolved Sep 09, 2026, 06:16 PM UTC

    We are pleased to inform you that the issue affecting Cosmos Hub API nodes, full nodes, and 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 →

Minor September 8, 2026 [Solana] Testnet Network Halt 7d 17h Solana Staking Reporting, Solana Staking API, Solana Native API, Solana Validator and 1 more

Started Sep 08, 2026, 12:01 PM UTC· resolved Sep 16, 2026, 05:54 AM UTC

  1. monitoring Sep 08, 2026, 12:01 PM UTC

    We want to provide an update regarding the ongoing halt of the Solana Testnet network, which the Solana Foundation initiated at the start of Epoch 1025 as part of the normal stabilization process for Agave v4.3. At this time, we are still waiting for the Solana Testnet reset. Our engineering team is actively monitoring the situation and will keep you informed as soon as the reset is completed. We greatly appreciate your continued patience and understanding during this time!

  2. resolved Sep 16, 2026, 05:54 AM UTC

    We are pleased to inform you that the issue affecting Solana Testnet 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!

Read the full incident report →

Minor September 2, 2026 [Solana Mainnet] - Degraded Performance on Universal API 7d 18h Blockdaemon Universal API, Solana

Started Sep 02, 2026, 06:12 PM UTC· resolved Sep 10, 2026, 12:13 PM UTC

  1. investigating Sep 02, 2026, 06:12 PM UTC

    Blockdaemon is currently investigating degraded performance and increased latency affecting the Universal API on Solana Mainnet. Specifically, customers may experience issues retrieving older blocks. We are actively working to identify the root cause and restore full performance as quickly as possible. We will provide further updates as our investigation progresses. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. identified Sep 03, 2026, 03:16 PM UTC

    We have identified an unusual spike in traffic as the contributing factor to the degraded performance and increased latency on the Universal API for Solana Mainnet. While the service is operating as expected, our team is actively drilling into the root cause of this traffic anomaly and will provide further updates as our investigation progresses. If you have any questions or concerns, please reach out to your Customer Success Manager.

  3. monitoring Sep 04, 2026, 02:54 PM UTC

    We would like to inform you that a fix has been implemented for the issue affecting the performance of Universal API on Solana 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!

  4. resolved Sep 10, 2026, 12:13 PM UTC

    We are pleased to inform you that the issue affecting Universal API for Solana 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 →

Critical August 31, 2026 [Cronos] Service Halted 23d 1h Cronos Native API, Cronos

Started Aug 31, 2026, 03:25 PM UTC· resolved Sep 23, 2026, 04:41 PM UTC

  1. investigating Aug 31, 2026, 03:25 PM UTC

    We want to inform you that we are currently experiencing issues with our Cronos nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Cronos 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.

  2. monitoring Sep 03, 2026, 01:52 PM UTC

    We’d like to share an update on this incident. The Cronos Network chain halt is a network-wide issue impacting the synchronization and availability of Cronos nodes. The Cronos team has advised that a network rule put in place during their incident response is still blocking connections. We continue to monitor the situation and will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding.

  3. resolved Sep 23, 2026, 04:41 PM UTC

    We are pleased to inform you that the chain halt issue affecting the synchronization and availability of Cronos 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 →

Minor August 27, 2026 [Polkadot] - Westend Nodes Service Disruption 6d Polkadot Native API

Started Aug 27, 2026, 12:28 PM UTC· resolved Sep 02, 2026, 01:07 PM UTC

  1. investigating Aug 27, 2026, 12:28 PM UTC

    We want to inform you that we are currently experiencing issues with our Polkadot Westend Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Polkadot Westend 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.

  2. resolved Sep 02, 2026, 01:07 PM UTC

    We are pleased to inform you that the issue affecting Polkadot Westend 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 →

Notice August 24, 2026 Cardano Staking Reporting – Service Disruption 7d 21h Cardano Staking Reporting

Started Aug 24, 2026, 12:41 PM UTC· resolved Sep 01, 2026, 10:36 AM UTC

  1. investigating Aug 24, 2026, 12:41 PM UTC

    We are currently investigating an issue affecting Cardano staking reporting. As a result, new staking data may not be available from the time the issue began. Historical data from before the issue started remains accessible. Our engineering team is actively working to restore the affected services. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. resolved Sep 01, 2026, 10:36 AM UTC

    We are pleased to inform you that the issue affecting Cardano Staking reporting 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 →

Notice August 21, 2026 Basechain Reth Archive Nodes – Degraded Performance 6d 2h Base Native API, Base

Started Aug 21, 2026, 10:23 AM UTC· resolved Aug 27, 2026, 12:33 PM UTC

  1. investigating Aug 21, 2026, 10:23 AM UTC

    We are currently investigating an issue affecting some Basechain Reth Archive nodes, which may cause nodes to fall behind the latest block height and result in delayed or degraded RPC responses. Our engineering team has completed the underlying migration and applied a mitigation across the affected nodes. We are continuing to closely monitor Basechain nodes to ensure they remain synchronized and stable. Customers may experience intermittent delays while affected nodes catch up with the latest block height. We will provide further updates as monitoring continues. Reference link: https://github.com/base/node/issues/1163 If you have any questions or need further assistance, please don't hesitate to contact your Customer Success Manager! Thank you for your understanding!

  2. resolved Aug 27, 2026, 12:33 PM UTC

    We are pleased to inform you that the issue affecting Basechain Reth 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 →

Minor August 14, 2026 [Canton] - Devnet Validator Node Service Disruption 1d 20h Canton Validator

Started Aug 14, 2026, 12:01 PM UTC· resolved Aug 16, 2026, 08:30 AM UTC

  1. investigating Aug 14, 2026, 12:01 PM UTC

    We want to inform you that we are currently experiencing issues with our Canton Devnet Validator Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Canton Devnet Validator 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.

  2. investigating Aug 14, 2026, 12:58 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 16, 2026, 08:30 AM UTC

    We are pleased to inform you that the issue affecting Canton Devnet Validator 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 →

Major August 12, 2026 Global Network Connectivity Issues 1d 4h Aptos Validator, Algorand, Aptos, Avalanche Validator and 64 more

Started Aug 12, 2026, 05:40 AM UTC· resolved Aug 13, 2026, 10:20 AM UTC

  1. monitoring Aug 12, 2026, 05:40 AM UTC

    We are investigating an issue with an upstream network provider that may be impacting connectivity to some nodes across multiple regions. The provider has identified the issue and restored service to the affected sites. We are actively monitoring our infrastructure and validating whether any of our nodes or services remain impacted. We will provide further updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. monitoring Aug 12, 2026, 05:41 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Aug 12, 2026, 03:21 PM UTC

    We would like to inform you that a fix has been implemented for the issue affecting our upstream network provider, 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!

  4. resolved Aug 13, 2026, 10:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 10, 2026 Robinhood Chain Mainnet Node Synchronization Issue 2d 23h Robinhood Chain

Started Aug 10, 2026, 11:04 AM UTC· resolved Aug 13, 2026, 10:25 AM UTC

  1. investigating Aug 10, 2026, 11:04 AM UTC

    We want to inform you that we are currently experiencing issues with our Robinhood Chain Mainnet nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Robinhood Chain Mainnet nodes, as the affected nodes have stopped processing new blocks. 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.

  2. resolved Aug 13, 2026, 10:25 AM UTC

    We want to inform you that our Robinhood Chain mainnet nodes are fully synced and currently operating in a healthy state, with no detected synchronization or performance issues at this time. If you experience any further issues or notice anything unusual, please reach out to your Customer Success Manager.

Read the full incident report →

Minor August 4, 2026 [Universal API] - Service Disruption 1h 39m Blockdaemon Universal API

Started Aug 04, 2026, 01:23 PM UTC· resolved Aug 04, 2026, 03:03 PM UTC

  1. investigating Aug 04, 2026, 01:23 PM UTC

    We would like to inform you that we are experiencing an issue with the Universal API service. Customers will experience errors when trying to use the service. Our engineering team is actively investigating the issue to find a resolution as quickly as possible. We will keep you updated on our progress and notify you once the issue is resolved. We apologize for any inconvenience this may cause and appreciate your understanding. If you have any questions or require further assistance, please reach out to your Customer Success Manager

  2. resolved Aug 04, 2026, 03:03 PM UTC

    We are pleased to inform you that the issue affecting Universal API service 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 →

Minor July 31, 2026 Robinhood Chain Testnet Native API Service Disruption 3d 22h Robinhood Chain

Started Jul 31, 2026, 12:13 PM UTC· resolved Aug 04, 2026, 10:22 AM UTC

  1. investigating Jul 31, 2026, 12:13 PM UTC

    We want to inform you that we are currently experiencing issues affecting the Robinhood-Chain testnet native API endpoint. Our team is actively investigating the issue and working to restore service as soon as possible. During this time, customers using the Robinhood-Chain testnet native API may experience difficulties accessing the service. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. resolved Aug 04, 2026, 10:22 AM UTC

    We are pleased to inform you that the issue affecting Robinhood-Chain testnet native API endpoint 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 →

Major July 29, 2026 [Canton] - Devnet Outage 1d 19h Canton Validator, Canton

Started Jul 29, 2026, 02:37 PM UTC· resolved Jul 31, 2026, 10:04 AM UTC

  1. identified Jul 29, 2026, 02:37 PM UTC

    Blockdaemon is aware that Canton DevNet is currently experiencing an outage following the SV LSU, which is preventing updated validators from reconnecting to the network. As a result, we are postponing the planned upgrade to v0.6.14 until the network is confirmed to be fully operational again. This applies to all Blockdaemon Canton DevNet nodes only, and Canton Mainnet and Testnet are unaffected. We are actively monitoring the situation and will provide updates as more information becomes available. If you have any questions or concerns please reach out to your Customer Success Manager.

  2. resolved Jul 31, 2026, 10:04 AM UTC

    We are pleased to inform you that the issue affecting Canton DevNet 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 →

Minor July 29, 2026 [Avalanche Testnet] Node Service Disruption 7d 16h Avalanche Native API, Avalanche

Started Jul 29, 2026, 01:15 PM UTC· resolved Aug 06, 2026, 06:06 AM UTC

  1. investigating Jul 29, 2026, 01:15 PM UTC

    We want to inform you that we are currently experiencing issues with our Avalanche Testnet Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Avalanche 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.

  2. resolved Aug 06, 2026, 06:06 AM UTC

    We are pleased to inform you that the issue affecting Avalanche 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 →

Major July 29, 2026 [Stellar] - Major Node Service Disruption 14d 23h Blockdaemon Universal API, Stellar Native API, Stellar

Started Jul 29, 2026, 10:32 AM UTC· resolved Aug 13, 2026, 09:59 AM UTC

  1. investigating Jul 29, 2026, 10:32 AM UTC

    We want to inform you that we are currently experiencing issues with our Stellar nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Stellar 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.

  2. monitoring Aug 05, 2026, 02:19 PM UTC

    Due to limitations in Stellar Horizon, we are currently unable to offer full history data. We have moved our shared API services to partial history nodes with 1.55m (~3 months) of ledger data to resume some level of service. We are currently exploring options with Stellar Foundation to fully restore service. We apologize for any inconvenience this may cause and appreciate your patience and understanding. If you have any questions or concerns, please reach out to your Customer Success Manager.

  3. resolved Aug 13, 2026, 09:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 28, 2026 [Arbitrum] - Sepolia nodes degraded performance 5h 34m Arbitrum Native API

Started Jul 28, 2026, 10:40 AM UTC· resolved Jul 28, 2026, 04:14 PM UTC

  1. investigating Jul 28, 2026, 10:40 AM UTC

    We want to inform you that we are currently experiencing issues with our Arbitrum Sepolia nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Arbitrum Sepolia 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.

  2. resolved Jul 28, 2026, 04:14 PM UTC

    We are pleased to inform you that the issue affecting Arbitrum Sepolia 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 →

Minor July 22, 2026 Solana Testnet - Service Degradation 1d 5h Solana Native API, Solana Validator

Started Jul 22, 2026, 07:31 AM UTC· resolved Jul 23, 2026, 12:49 PM UTC

  1. investigating Jul 22, 2026, 07:31 AM UTC

    We are aware of an ongoing issue affecting the Solana Testnet network. According to an upstream Solana Testnet announcement, a supermajority of the Testnet has gone delinquent, causing block finalization to stall. As a result, Blockdaemon's Solana Testnet services, including shared RPC endpoints, may experience stalled slot progression or delayed updates. We are actively monitoring the upstream network issue and will provide updates as more information becomes available.

  2. resolved Jul 23, 2026, 12:49 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 →

Minor July 18, 2026 SGP Network Connectivity Issues 1h 22m BNB, Ethereum Validators, Kusama Validator, Ethereum and 4 more

Started Jul 18, 2026, 01:09 AM UTC· resolved Jul 18, 2026, 02:32 AM UTC

  1. investigating Jul 18, 2026, 01:09 AM UTC

    We are investigating an upstream network provider issue impacting nodes in the Singapore (SGP) region, which may result in increased latency. We are actively monitoring the situation and will provide updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.

  2. resolved Jul 18, 2026, 02:32 AM UTC

    The issue affecting nodes in the Singapore (SGP) region has been resolved, and services are currently operating normally. We continue to monitor the environment to ensure ongoing stability. We sincerely apologize for any inconvenience caused and appreciate your continued patience. If you have any questions or need assistance, please reach out to your Customer Success Manager.

Read the full incident report →

Minor July 8, 2026 [Cosmos] - Degraded Performance 2h 37m Cosmos Validator, Cosmos Native API, Cosmos

Started Jul 08, 2026, 05:04 PM UTC· resolved Jul 08, 2026, 07:41 PM UTC

  1. identified Jul 08, 2026, 05:04 PM UTC

    We have identified the root cause of the issue affecting Cosmos Mainnet, 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 Customer Success Manager! Thank you for your understanding!

  2. monitoring Jul 08, 2026, 06:11 PM UTC

    We would like to inform you that a fix has been implemented for the issue affecting Cosmos 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!

  3. resolved Jul 08, 2026, 07:41 PM UTC

    We are pleased to inform you that the issue affecting Cosmos 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 →

Notice July 2, 2026 Service Degradation Affecting Avalanche Mainnet 42m Avalanche Native API, Avalanche

Started Jul 02, 2026, 11:29 AM UTC· resolved Jul 02, 2026, 12:12 PM UTC

  1. investigating Jul 02, 2026, 11:29 AM UTC

    We want to inform you that we are currently experiencing issues with our Avalanche mainnet endpoint which is resulting in 502 Bad Gateway responses. Our team is actively investigating the problem and working diligently to resolve it. 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.

  2. resolved Jul 02, 2026, 12:12 PM UTC

    We are pleased to inform you that the issue affecting Avalanche mainnet endpoint 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 →