Blockdaemon incident

ETH2 Prysm Client Degradation Following Fusaka Upgrade Impacting L2 Networks

Blockdaemon experienced a minor incident on December 4, 2025 affecting Arbitrum and Arbitrum Native API and 1 more component, lasting 34d 2h. The incident has been resolved; the full update timeline is below.

Started: Dec 04, 2025, 02:34 PM UTC
Resolved: Jan 07, 2026, 04:57 PM UTC
Duration: 34d 2h
Detected by Pingoru: Dec 04, 2025, 02:34 PM UTC

Affected components

ArbitrumArbitrum Native APIBase Native APICelo ValidatorBaseCelo Native APIInk Native APICeloOptimism Native APIPolygon Native API

Update timeline

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!