- Detected by Pingoru
- Sep 08, 2026, 11:21 PM UTC
- Resolved
- Sep 09, 2026, 06:16 PM UTC
- Duration
- 18h 54m
Affected: Cosmos Native APICosmos
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Sep 08, 2026, 12:01 PM UTC
- Resolved
- Sep 16, 2026, 05:54 AM UTC
- Duration
- 7d 17h
Affected: Solana Staking ReportingSolana Staking APISolana Native APISolana ValidatorSolana
Timeline · 2 updates
-
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!
-
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 →
- Detected by Pingoru
- Sep 02, 2026, 06:12 PM UTC
- Resolved
- Sep 10, 2026, 12:13 PM UTC
- Duration
- 7d 18h
Affected: Blockdaemon Universal APISolana
Timeline · 4 updates
-
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.
-
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.
-
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!
-
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 →
- Detected by Pingoru
- Aug 27, 2026, 12:28 PM UTC
- Resolved
- Sep 02, 2026, 01:07 PM UTC
- Duration
- 6d
Affected: Polkadot Native API
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Aug 24, 2026, 12:41 PM UTC
- Resolved
- Sep 01, 2026, 10:36 AM UTC
- Duration
- 7d 21h
Affected: Cardano Staking Reporting
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Aug 21, 2026, 10:23 AM UTC
- Resolved
- Aug 27, 2026, 12:33 PM UTC
- Duration
- 6d 2h
Affected: Base Native APIBase
Timeline · 2 updates
-
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!
-
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 →
- Detected by Pingoru
- Aug 14, 2026, 12:01 PM UTC
- Resolved
- Aug 16, 2026, 08:30 AM UTC
- Duration
- 1d 20h
Affected: Canton ValidatorBitcoin
Timeline · 3 updates
-
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.
-
investigating Aug 14, 2026, 12:58 PM UTC
We are continuing to investigate this issue.
-
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 →
- Detected by Pingoru
- Aug 12, 2026, 05:40 AM UTC
- Resolved
- Aug 13, 2026, 10:20 AM UTC
- Duration
- 1d 4h
Affected: Aptos ValidatorAlgorandAptosAvalanche ValidatorArbitrumBabylon ValidatorCanton ValidatorCardano ValidatorAvalancheCosmos ValidatorBabylonBaseCore ValidatorBitcoinCrypto.org ValidatorBitcoin CashdYdX ValidatorBNBEthereum ValidatorsCardanoFlow ConsensusFlow VerificationKusama ValidatorCosmosGear ValidatorCronosIka ValidatorMonad ValidatorDogecoinNear ValidatorEthereumPolkadot ValidatorPolygon ValidatorProvenance ValidatorFlowSKALE ValidatorSolana ValidatorStacks StackerStory ValidatorKusamaSUI ValidatorLineaLitecoinTON ValidatorNearWemix ValidatorOptimismXRP ValidatorsZero GravityPolkadotPolygonProvenanceSkaleSolanaSoneiumStellarSUIUnichainXLayerXRPTronTempo ValidatorBotanixCantonHyperliquidStoryzkSyncArc Validator
Timeline · 4 updates
-
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.
-
monitoring Aug 12, 2026, 05:41 AM UTC
We are continuing to monitor for any further issues.
-
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!
-
resolved Aug 13, 2026, 10:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 11:04 AM UTC
- Resolved
- Aug 13, 2026, 10:25 AM UTC
- Duration
- 2d 23h
Affected: Robinhood Chain
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Aug 04, 2026, 01:23 PM UTC
- Resolved
- Aug 04, 2026, 03:03 PM UTC
- Duration
- 1h 39m
Affected: Blockdaemon Universal API
Timeline · 2 updates
-
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
-
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 →
- Detected by Pingoru
- Jul 31, 2026, 12:13 PM UTC
- Resolved
- Aug 04, 2026, 10:22 AM UTC
- Duration
- 3d 22h
Affected: Robinhood Chain
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 29, 2026, 02:37 PM UTC
- Resolved
- Jul 31, 2026, 10:04 AM UTC
- Duration
- 1d 19h
Affected: Canton ValidatorCanton
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 29, 2026, 01:15 PM UTC
- Resolved
- Aug 06, 2026, 06:06 AM UTC
- Duration
- 7d 16h
Affected: Avalanche Native APIAvalanche
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 29, 2026, 10:32 AM UTC
- Resolved
- Aug 13, 2026, 09:59 AM UTC
- Duration
- 14d 23h
Affected: Blockdaemon Universal APIStellar Native APIStellar
Timeline · 3 updates
-
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.
-
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.
-
resolved Aug 13, 2026, 09:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 10:40 AM UTC
- Resolved
- Jul 28, 2026, 04:14 PM UTC
- Duration
- 5h 34m
Affected: Arbitrum Native API
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 22, 2026, 07:31 AM UTC
- Resolved
- Jul 23, 2026, 12:49 PM UTC
- Duration
- 1d 5h
Affected: Solana Native APISolana Validator
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 18, 2026, 01:09 AM UTC
- Resolved
- Jul 18, 2026, 02:32 AM UTC
- Duration
- 1h 22m
Affected: BNBEthereum ValidatorsKusama ValidatorEthereumPolkadot ValidatorKusamaTON ValidatorPolkadot
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 08, 2026, 05:04 PM UTC
- Resolved
- Jul 08, 2026, 07:41 PM UTC
- Duration
- 2h 37m
Affected: Cosmos ValidatorCosmos Native APICosmos
Timeline · 3 updates
-
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!
-
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!
-
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 →
- Detected by Pingoru
- Jul 02, 2026, 11:29 AM UTC
- Resolved
- Jul 02, 2026, 12:12 PM UTC
- Duration
- 42m
Affected: Avalanche Native APIAvalanche
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jun 26, 2026, 03:56 PM UTC
- Resolved
- Jun 30, 2026, 08:35 AM UTC
- Duration
- 3d 16h
Affected: Canton
Timeline · 2 updates
-
identified Jun 26, 2026, 03:56 PM UTC
We would like to inform customers that Canton Mainnet is currently under a Topology Freeze as part of an upstream Canton synchronizer upgrade. This is not a Blockdaemon-initiated change. The freeze began Friday, June 26 at 13:00 UTC and is expected to conclude just after 13:00 UTC on Saturday, June 27. During this period, topology changes are temporarily disabled. Customers attempting such operations may receive errors indicating the network is frozen. All other operations, including normal transaction processing, continue to function as expected. We are monitoring the situation closely and will provide further updates as they become available. If you have any questions or concerns please reach out to your Customer Success Manager.
-
resolved Jun 30, 2026, 08:35 AM UTC
We are pleased to inform you that the issue affecting Canton 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
- Jun 25, 2026, 06:04 PM UTC
- Resolved
- Jun 29, 2026, 09:06 AM UTC
- Duration
- 3d 15h
Affected: Base Native APIBase
Timeline · 3 updates
-
identified Jun 25, 2026, 06:04 PM UTC
Blockdaemon is aware of a network stall on the Base Mainnet. The issue has been identified and a fix is currently being implemented. We are monitoring the situation closely and will provide further updates as they become available. If you have any questions or concerns please reach out to your Customer Success Manager.
-
monitoring Jun 25, 2026, 06:54 PM UTC
We would like to inform you that a fix has been implemented for the issue affecting Base 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 Jun 29, 2026, 09:06 AM UTC
We are pleased to inform you that the issue affecting Base 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
- May 28, 2026, 08:37 PM UTC
- Resolved
- May 30, 2026, 11:18 PM UTC
- Duration
- 2d 2h
Affected: SUI ValidatorSUI
Timeline · 4 updates
-
identified May 28, 2026, 08:37 PM UTC
Blockdaemon is aware of a network stall on the SUI Mainnet. The issue has been identified and a fix is currently being implemented. We are monitoring the situation closely and will provide further updates as they become available. If you have any questions or concerns please reach out to your Customer Success Manager.
-
monitoring May 28, 2026, 08:54 PM UTC
We would like to inform you that a fix has been implemented for the issue affecting SUI 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!
-
monitoring May 30, 2026, 11:17 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 30, 2026, 11:18 PM UTC
We are pleased to inform you that the issue affecting 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!
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 12:54 PM UTC
- Resolved
- May 27, 2026, 03:46 PM UTC
- Duration
- 5d 2h
Affected: Cardano Staking Reporting
Timeline · 2 updates
-
investigating May 22, 2026, 12:54 PM UTC
We would like to inform you that Blockdaemon is currently experiencing a service degradation affecting the Cardano Staking Reporting API. This issue is causing the API to not return new reward information from epoch 630 onwards. Our team is actively working on resolving this problem and will provide an update once we have an estimated time for resolution. 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 May 27, 2026, 03:46 PM UTC
We are pleased to inform you that the issue affecting Cardano Staking Reporting API 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
- May 18, 2026, 09:47 AM UTC
- Resolved
- May 18, 2026, 11:59 AM UTC
- Duration
- 2h 12m
Affected: Ethereum Staking Reporting
Timeline · 2 updates
-
investigating May 18, 2026, 09:47 AM UTC
We would like to inform you that Blockdaemon is currently experiencing a service degradation affecting the Ethereum Staking Reporting API. This issue is causing the API to not return new reward information. Our team is actively working on resolving this problem and will provide an update once we have an estimated time for resolution. We apologize for any inconvenience this may cause and appreciate your patience. If you have any questions or need further assistance, please do not hesitate to contact your Customer Success Manager. Thank you for your understanding!
-
resolved May 18, 2026, 11:59 AM UTC
We are pleased to inform you that the issue affecting Ethereum Staking Reporting API 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
- May 05, 2026, 12:57 PM UTC
- Resolved
- May 06, 2026, 05:37 AM UTC
- Duration
- 16h 39m
Affected: Blockdaemon Universal API
Timeline · 3 updates
-
investigating May 05, 2026, 12:57 PM UTC
We would like to inform you that we are experiencing an issue with the Universal, Event-Streaming, Wallet-Transact, Portfolio API service on Ubiquity. 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
-
investigating May 05, 2026, 09:08 PM UTC
We are pleased to inform you that the issues affecting the Universal, Event-Streaming, Wallet-Transact, and Portfolio API services on Ubiquity have been fully resolved. All systems are now operating normally. We apologize for the disruption and thank you for your patience. If you continue to experience any issues, please reach out to your Customer Success Manager.
-
resolved May 06, 2026, 05:37 AM UTC
This incident has been resolved.
Read the full incident report →