There were 60 Alchemy outages since March 4, 2026 totaling 1105h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
Preliminary observation suggests this may have been a network-wide stall. The network has resumed and is producing blocks.
We are currently investigating degraded performance affecting Botanix Testnet. Our nodes are stalled at block 3,955,262 and not producing new blocks. This issue is network-wide and affects all Botanix Testnet RPC traffic. We are actively coordinating with the Botanix team and will provide updates as the situation develops.
This incident has been resolved.
We are currently investigating this issue.
We are currently investigating degraded performance on Ink Sepolia. Customers might experience elevated 503 error rates and latency.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating degraded performance on Rise Testnet. Customers might experience elevated 5xx error rates and latency.
This incident has been resolved.
We are currently investigating this issue, customers may experience elevated latency.
This incident has been resolved.
We are investigating a delay in our data indexing pipeline. This is resulting in degraded data freshness across the Token, NFT, and Transfers APIs on Base Mainnet.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency
This incident has been resolved.
We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency
This incident has been resolved.
We are currently investigating elevated latency for archival data on Arbitrum Mainnet
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
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.
Our Sonic mainnet RPC nodes are continuing to resync from the latest snapshot. During this process, all traffic is being routed through secondary infrastructure with updated binaries. Websocket connections are unavailable until the resync is complete, and customers may experience elevated latency or intermittent errors on RPC requests. We expect the resync to finish within the next several hours and will provide another update once primary nodes are back online and operating at full capacity.
Several nodes in our primary fleet have successfully resynced and are now serving traffic. However, we are not yet back to full capacity; customers may experience elevated latency or an intermittent error rate. We will provide a final update once all nodes are fully back online
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been resolved.
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
A fix has been implemented by the Base team and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
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
We are continuing to investigate this issue.
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.
This incident has been resolved.
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.
A fix has been applied and we are seeing reduction in error rates. We will continue to monitor and confirm full resolution.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
Some customers may be seeing outdated data returned by our NFT APIs across multiple networks. Our team has already restored accurate data for a subset of affected networks and is continuing to work through the remainder. We expect full resolution by end of this week. We will post updates as work continues. We apologize for any disruption.
This incident has been resolved.
We are investigating an issue causing webhook delivery delays affecting multiple chains, including BNB Mainnet and Base Mainnet. Customers may experience delayed or slow webhook notifications during this time. Our team is actively investigating and will provide updates as we learn more.
The team has identified the cause and is currently pushing a fix. We will update this page once the fix is deployed and the issue is confirmed resolved.
The fix is applied and our systems are catching up. We continue to monitor the performance.
This incident has been resolved.
Tempo Moderato is experiencing a network halt. We are working with the Tempo team to get this resolved for you ASAP!
This incident has been resolved.
We are currently investigating an issue causing Solana webhook notifications to stall. Deliveries may be delayed or not arriving at all. Our team is actively looking into this and will provide updates as we learn more.
Our team has identified the issue and is deploying a fix.
We are seeing an improvement and continue to monitor the situation.
This incident has been resolved.
This incident has been resolved.
A network wide incident is currently impacting Botanix Testnet - we're investigating
This incident has been resolved.
Pingoru polls Alchemy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required