Alchemy Status

Investigating: We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency

Investigating: We are currently investigating elevated latency for archival data on Arbitrum Mainnet

Monitoring: An accidental hard fork occurred on the Sonic mainnet due to a consensus-breaking change introduced in Sonic client v2.1.6, related to an upgraded Ethereum library containing CVE security patches. Nodes running older client versions fell out of consensus at block 66,026,364, while the network itself continued producing blocks normally.

Our Sonic mainnet RPC nodes were affected. We have upgraded all nodes to v2.1.6 and initiated a full database resync from the latest snapshot. In the interim, traffic is being served through secondary infrastructure with updated binaries. Customers may experience intermittent errors or elevated latencies until primary nodes complete the resync process.

The Sonic network remains fully operational -- blocks continue to be produced, transactions are processing, and funds are safe.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Identified: The X-Layer team is currently conducting network-level load testing. This is causing intermittent performance issues across multiple RPC nodes. We are in direct communication with their team to mitigate the impact.

Investigating: We are currently investigating this issue.

Investigating: We are aware of an ongoing issue affecting Base Flashblocks on Mainnet. Base is currently not producing flashblocks. Standard block production on Base is unaffected.

This is a chain-wide incident originating with Base. We are monitoring the situation and will provide updates as they become available.

For the latest updates from Base directly, see their status page: https://status.base.org/incidents/dg4m8nxd622r

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: A bug in Nitro software caused a block divergence on Arbitrum Sepolia, leading to block production being halted as a precaution. This issue is affecting all Arbitrum Orbit rollups that depend on the same Nitro version. Other Impacted networks: Anime Sepolia ApeChain Curtis Mind Testnet Edge Testnet EARNM Testnet Additional Arbitrum-based rollups may also be affected

No user funds are at risk.

The team is actively working on an infrastructure update and a new Nitro release to restore block production.

Investigating: We are continuing to investigate this issue.

Investigating: Arbitrum Sepolia is currently experiencing a network-wide stall. All services that rely on network progress are impacted. We are working closely with the Arbitrum team to resolve this as quickly as possible

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been applied and we are seeing reduction in error rates. We will continue to monitor and confirm full resolution.

Investigating: We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency. We will share more updates as we have them.

Resolved: This incident has been resolved.

Investigating: We are currently investigating a chain-wide issue affecting Starknet Sepolia. Some requests may experience degraded performance or failures. We are actively working with the Starknet team to resolve this and will provide updates as we learn more.

Resolved: This incident has been resolved.

Investigating: We are currently investigating an issue where the finalized block tag on ZKsync Era and Abstract mainnet has stopped progressing. This appears to be an upstream network issue. We are monitoring for resolution and will provide updates as the situation develops.

Resolved: This incident has been resolved.

Investigating: We are currently investigating an issue affecting Abstract mainnet. The last confirmed block is 46887372. Customers may experience degraded performance or failures across all Abstract mainnet services, including JSON-RPC requests and other dependent functionality.

This appears to be a chain-wide issue. We are actively monitoring the situation and working to restore full service.