- 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 →
- Detected by Pingoru
- Apr 28, 2026, 12:56 PM UTC
- Resolved
- Apr 29, 2026, 07:40 PM UTC
- Duration
- 1d 6h
Affected: Blockdaemon Universal APIBase Native API
Timeline · 2 updates
-
investigating Apr 28, 2026, 12:56 PM UTC
We would like to inform you that we are experiencing an issue with the Basechain Mainnet 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
-
resolved Apr 29, 2026, 07:40 PM UTC
We are pleased to inform you that the issue affecting Basechain Mainnet 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
- Apr 14, 2026, 12:57 PM UTC
- Resolved
- Apr 14, 2026, 03:32 PM UTC
- Duration
- 2h 34m
Affected: Solana ValidatorSolana
Timeline · 2 updates
-
investigating Apr 14, 2026, 12:57 PM UTC
We want to inform you that we are currently experiencing issues with our Solana Devnet Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Solana Devnet 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 Apr 14, 2026, 03:32 PM UTC
The issue affecting Solana Devnet Nodes has been identified and fixed. Services are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 11:09 PM UTC
- Resolved
- Apr 01, 2026, 02:18 PM UTC
- Duration
- 5d 15h
Affected: AlgorandAlgorand Native APIBlockdaemon Universal APIAptosAvalanche ValidatorAptos Native APIArbitrumArbitrum Native APIArcArc Native APIAvalanche Native APIBase Native APIAvalancheBitcoin Native APIBabylonBaseBitcoinCronos Native APIDogecoin Native APIEthereum Native APIBNBEthereum ValidatorsCardanoCosmosCronosMonad Native APINear Native APIDogecoinOptimism Native APIPolkadot Native APIPolygon Native APIEthereumSolana Native APIStellar Native APIPolygon ValidatorProvenance ValidatorSolana ValidatorKusamaTON ValidatorNearOptimismPolkadotProvenanceSkaleSolanaStellarTron
Timeline · 3 updates
-
investigating Mar 26, 2026, 11:09 PM UTC
We are investigating an upstream network provider issue impacting nodes in the Amsterdam (AMS) region, which may result in connectivity issues. 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.
-
monitoring Mar 27, 2026, 12:25 AM UTC
A fix has been implemented for the issue affecting nodes in the Amsterdam (AMS) region, 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 reach out to your Customer Success Manager.
-
resolved Apr 01, 2026, 02:18 PM UTC
The issue affecting nodes in the Amsterdam (AMS) region has been resolved, and services are currently operating normally. We continue to monitor the environment to ensure ongoing stability. We are awaiting a detailed incident report from our infrastructure provider, which will include the root cause analysis and any follow-up actions to prevent recurrence. We will share further updates once this information is available. 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 or to our servicedesk via [email protected]
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 01:19 PM UTC
- Resolved
- Mar 25, 2026, 02:07 PM UTC
- Duration
- 47m
Affected: ArbitrumArbitrum Native API
Timeline · 2 updates
-
investigating Mar 25, 2026, 01:19 PM UTC
We want to inform you that we are currently experiencing issues with our Arbitrum Mainnet and 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 Mainnet and 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 Mar 25, 2026, 02:07 PM UTC
We are pleased to inform you that the issue affecting our Arbitrum Mainnet and 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
- Mar 19, 2026, 07:33 PM UTC
- Resolved
- Mar 20, 2026, 03:11 PM UTC
- Duration
- 19h 38m
Affected: ArcArc Native API
Timeline · 2 updates
-
investigating Mar 19, 2026, 07:33 PM UTC
We want to inform you that we are currently experiencing issues with our Arc Testnet Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Arc 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 Mar 20, 2026, 03:11 PM UTC
We are pleased to inform you that the issue affecting Arc 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
- Mar 18, 2026, 01:31 PM UTC
- Resolved
- Mar 19, 2026, 01:37 PM UTC
- Duration
- 1d
Affected: Ethereum Native API
Timeline · 2 updates
-
investigating Mar 18, 2026, 01:31 PM UTC
We are currently experiencing an issue affecting our Ethereum Mainnet RPC (Native endpoint), which may result in errors when retrieving historical block data. Our engineering team is actively investigating the issue and working to resolve it as quickly as possible. We will keep you informed of our progress and provide updates as soon as more information becomes available. We apologize 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.
-
resolved Mar 19, 2026, 01:37 PM UTC
We are pleased to inform you that the issue affecting our Ethereum Mainnet RPC (Native 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
- Feb 24, 2026, 02:20 PM UTC
- Resolved
- Mar 12, 2026, 02:26 PM UTC
- Duration
- 16d
Affected: AlgorandAptosAvalanche ValidatorAvalancheCosmos ValidatorBabylonCrypto.org ValidatorBNBEthereum ValidatorsMonad ValidatorEthereumPolkadot ValidatorFlareKusamaLineaTON ValidatorWemix ValidatorOptimismXRP ValidatorsPolygonSolanaStellar
Timeline · 2 updates
-
investigating Feb 24, 2026, 02:20 PM 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 Mar 12, 2026, 02:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 12:00 AM UTC
- Resolved
- Feb 21, 2026, 02:07 AM UTC
- Duration
- 2h 6m
Affected: Stellar Native APIStellar
Timeline · 3 updates
-
investigating Feb 21, 2026, 12:00 AM UTC
We are aware of a downtime issue affecting Stellar RPC instances. This is an upstream issue confirmed by the Stellar Development Foundation. The Stellar network itself is healthy and funds are safe. We are monitoring the situation and will provide updates as they become available. If you have any questions or concerns, please reach out to your Customer Success Manager.
-
investigating Feb 21, 2026, 12:01 AM UTC
We are continuing to investigate this issue.
-
resolved Feb 21, 2026, 02:07 AM UTC
We are pleased to inform you that the issue affecting Stellar 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
- Feb 20, 2026, 09:27 AM UTC
- Resolved
- Feb 20, 2026, 01:14 PM UTC
- Duration
- 3h 46m
Affected: AptosAvalanche Native APIEthereum ValidatorsEthereumXRP Native APITON ValidatorPolygonStellarTron
Timeline · 2 updates
-
investigating Feb 20, 2026, 09:27 AM UTC
We are investigating a reported loss of the majority of internet connectivity at our VAN1 location. 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 Feb 20, 2026, 01:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 11:08 AM UTC
- Resolved
- Feb 12, 2026, 04:32 PM UTC
- Duration
- 2d 5h
Affected: Blockdaemon Web App
Timeline · 2 updates
-
investigating Feb 10, 2026, 11:08 AM UTC
We are investigating an issue where API usage data is not visible in the dashboard for some customers. This may affect usage metrics across multiple dates and API keys. Our engineering teams are actively working to restore full visibility. No impact to API request processing has been identified. Further updates will be shared as we have more information.
-
resolved Feb 12, 2026, 04:32 PM UTC
We are pleased to inform you that the issue where API usage data was not visible in the dashboard for some customers has been resolved. API usage metrics are now visible as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while our engineering teams worked to restore full visibility. 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
- Feb 05, 2026, 12:58 PM UTC
- Resolved
- Feb 05, 2026, 04:07 PM UTC
- Duration
- 3h 8m
Affected: Stellar Native APIStellar
Timeline · 2 updates
-
investigating Feb 05, 2026, 12:58 PM UTC
We want to inform you that we are currently experiencing issues with our Stellar Horizon Testnet nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may experience synchronization issues with Stellar Testnet Horizon 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 Feb 05, 2026, 04:07 PM UTC
We are pleased to inform you that the issue affecting Stellar Testnet Horizon nodes has been resolved, and the service is now fully operational. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager!
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 11:04 AM UTC
- Resolved
- Jan 21, 2026, 01:36 PM UTC
- Duration
- 2h 32m
Affected: Canton Validator
Timeline · 2 updates
-
investigating Jan 21, 2026, 11:04 AM UTC
We want to inform you that TON Testnet is currently experiencing a block production stall. This issue appears to originate from the TON Testnet network and is outside of our direct control. Our team is 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 Jan 21, 2026, 01:36 PM UTC
The issue affecting TON Testnet has been resolved, and services are operating normally again. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 01:50 PM UTC
- Resolved
- Jan 16, 2026, 04:52 AM UTC
- Duration
- 7d 15h
Affected: Polygon Staking ReportingPolygon Staking APIPolygon Native APIPolygon ValidatorPolygon
Timeline · 2 updates
-
investigating Jan 08, 2026, 01:50 PM UTC
We want to inform you that we are currently experiencing issues with our Polygon nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Polygon nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments! If you have any questions or concerns, please reach out to your Customer Success Manager.
-
resolved Jan 16, 2026, 04:52 AM UTC
We are pleased to inform you that the issue affecting Polygon has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 01:35 PM UTC
- Resolved
- Jan 06, 2026, 02:38 PM UTC
- Duration
- 1h 3m
Affected: Tron Native APITron
Timeline · 3 updates
-
investigating Jan 06, 2026, 01:35 PM 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 block height issue with your Tron Nile Testnet nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments! If you have any questions or concerns, please reach out to your Customer Success Manager.
-
investigating Jan 06, 2026, 02:02 PM UTC
We wanted to inform you that we are going to update the nodes to GreatVoyage-v4.8.1-build2. The nodes are expected to experience a brief downtime during the update.
-
resolved Jan 06, 2026, 02:38 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
- Jan 05, 2026, 01:34 PM UTC
- Resolved
- Jan 06, 2026, 05:50 PM UTC
- Duration
- 1d 4h
Affected: Kusama Native APIKusama
Timeline · 3 updates
-
investigating Jan 05, 2026, 01:34 PM UTC
We are investigating an issue affecting the Kusama AssetHub Sidecar service. The issue has been identified and is related to an upstream dependency. We are coordinating with Parity to address the problem. The issue will remain until an update is released and deployed. We will provide further updates as more information becomes available. If you have any questions or need further assistance, please don't hesitate to contact your Customer Success Manager!
-
identified Jan 06, 2026, 04:48 PM UTC
Blockdaemon will perform an urgent update to the Substrate API Sidecar service, upgrading to v20.13.3, which includes fixes released by the Parity team. This update will be rolled out to all affected Kusama full nodes. During the update, customers may experience brief service interruptions on their nodes. This downtime is required to apply the fix and restore normal service operation. We have validated this release and expect the upgrade to fully resolve the incident without any additional impact beyond the brief interruptions noted above. Further updates will be posted here as the rollout progresses. If you have any questions or concerns, please contact your Customer Success Manager. Additional information: https://github.com/paritytech/substrate-api-sidecar/releases/tag/v20.13.3
-
resolved Jan 06, 2026, 05:50 PM UTC
The issue has been resolved following an upgrade to Substrate API Sidecar v20.13.3. All affected services are operating normally. If you have any questions or experience any additional issues, please contact your Customer Success Manager.
Read the full incident report →
- Detected by Pingoru
- Jan 01, 2026, 09:05 AM UTC
- Resolved
- Jan 06, 2026, 10:13 AM UTC
- Duration
- 5d 1h
Affected: XLayer Native APIXLayer
Timeline · 2 updates
-
investigating Jan 01, 2026, 09:05 AM UTC
Hello Team, We wanted to let you know that a service degradation has been identified affecting your Xlayer node, which is currently unhealthy and several thousand blocks behind. Our engineering team is actively investigating the situation and taking appropriate action to resolve the issue. We will continue to monitor the node closely and verify its health as mitigation efforts are applied. Further updates will be provided as more information becomes available. We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure stable and reliable node operations.
-
resolved Jan 06, 2026, 10:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 07:55 PM UTC
- Resolved
- Jan 07, 2026, 01:20 PM UTC
- Duration
- 20d 17h
Affected: Polygon Native APIPolygon
Timeline · 2 updates
-
investigating Dec 17, 2025, 07:55 PM UTC
We are currently investigating an upstream issue affecting the Polygon PoS network, specifically the Bor (block production and execution) layer, where multiple Bor nodes across the ecosystem are experiencing stalled behavior. This condition is resulting in degraded RPC availability for Polygon PoS across several infrastructure providers, including Blockdaemon. The Polygon PoS chain itself remains live and continues to produce blocks. Block production is not halted. Current Impact: - Intermittent or degraded Polygon PoS RPC responses - Potential delays or timeouts for read/write requests Mitigation & Next Steps: Our engineering team is actively monitoring the situation and coordinating with the Polygon core teams as mitigation efforts are underway. We will continue to provide updates as more information becomes available or when service levels change.
-
resolved Jan 07, 2026, 01:20 PM UTC
We are pleased to inform you that the issue affecting Polygon PoS network has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 10:24 AM UTC
- Resolved
- Dec 17, 2025, 11:10 AM UTC
- Duration
- 1d
Affected: Monad Native APIMonad Validator
Timeline · 2 updates
-
investigating Dec 16, 2025, 10:24 AM UTC
Blockdaemon is performing scheduled network reset today 12/16/2025, which will involve a network reset. During this reset window, Blockdaemon’s testnet validator will be unavailable, and access to the RPC API will also be temporarily unavailable. Our engineering teams are working closely with Monad and will continue to verify network and validator stability as the process progresses. Further updates will be shared on this status page as they become available. We appreciate your patience and understanding while we work to ensure a smooth and stable network restart.
-
resolved Dec 17, 2025, 11:10 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2025, 09:48 AM UTC
- Resolved
- Jan 07, 2026, 04:54 PM UTC
- Duration
- 26d 7h
Affected: Ethereum Native APIEthereum ValidatorsEthereum
Timeline · 2 updates
-
investigating Dec 12, 2025, 09:48 AM UTC
Blockdaemon is aware of an issue affecting Ethereum validators following the recent upgrade to Prysm v7.1.0, where some Prysm-based validators are experiencing increased missed attestations. The issue appears to be impacting a subset of our infrastructure Our engineering teams are actively investigating the issue and taking appropriate action We will continue to monitor the situation closely and verify validator health as mitigation efforts are applied. Further updates will be provided as more information becomes available. We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure stable and consistent validator operations
-
resolved Jan 07, 2026, 04:54 PM UTC
We are pleased to inform you that the issue affecting Ethereum validators has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 02:34 PM UTC
- Resolved
- Jan 07, 2026, 04:57 PM UTC
- Duration
- 34d 2h
Affected: ArbitrumArbitrum Native APIBase Native APICelo ValidatorBaseCelo Native APIInk Native APICeloOptimism Native APIPolygon Native APIPolygon ValidatorXLayer Native APIInkOptimismPolygonUnichainXLayer
Timeline · 2 updates
-
investigating Dec 04, 2025, 02:34 PM UTC
We are currently investigating an upstream issue introduced in the Ethereum Prysm (eth2) consensus client following the recent Fusaka network upgrade. This bug has caused unexpected behavior in the consensus layer and is producing downstream impact for services relying on Prysm nodes. Several Layer 2 networks may be affected, including: - Base - Optimism - Arbitrum - Unichain - Polygon - Celo - XLayer - Ink Depending on protocol and configuration, customers may experience disruptions such as delayed confirmations, degraded API performance, or unexpected consensus-related errors. Our engineering teams are actively working with upstream Prysm maintainers and monitoring all impacted networks for instability. We will provide further updates as more information becomes available.
-
resolved Jan 07, 2026, 04:57 PM UTC
We are pleased to inform you that this issue affecting Several Layer 2 networks has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!
Read the full incident report →
Critical December 3, 2025 - Detected by Pingoru
- Dec 03, 2025, 05:59 PM UTC
- Resolved
- Dec 15, 2025, 05:09 PM UTC
- Duration
- 11d 23h
Affected: TON Validator
Timeline · 4 updates
-
investigating Dec 03, 2025, 05:59 PM UTC
We want to inform you that Ton Testnet is currently suffering an outage due to a network issue out of our control. As a result, you may encounter difficulties accessing your Ton 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.
-
monitoring Dec 03, 2025, 06:46 PM UTC
We would like to inform you that we are seeing service return for Ton Testnet, we will continue to monitor the network to ensure stability. We will provide further updates once the monitoring period is complete and the issue is fully resolved. 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 Dec 03, 2025, 06:47 PM UTC
We are continuing to monitor for any further issues.
-
resolved Dec 15, 2025, 05:09 PM UTC
The issue has been fully resolved, and the network is operating normally. No further action is required.
Read the full incident report →