All Systems Operational

Ethereum Operational
Solana Operational
Abstract Operational
ADI Operational
Animechain Operational
Arbitrum Operational
ARC Operational
ApeChain Operational
Aptos Operational
Astar Operational
Avalanche C Chain Operational
Base Operational
Berachain Operational
Bitcoin Operational
Blast Operational
BNB Smart Chain Operational
BOB Operational
Boba Operational
Botanix Operational
Celestia Operational
Celo Operational
Citrea Operational
Clankermon Operational
Cronos Operational
CrossFi Operational
Degen Operational
EARNM Operational
Fantom Operational
Flow Operational
Fraxtal Operational
Galactica Operational
Geist Operational
Gensyn Operational
Gnosis Operational
Humanity Operational
HyperEVM Operational
Injective Operational
Ink Chain Operational
Kaia Operational
Kinto Operational
Lens Operational
Linea Operational
Mantle Operational
MegaETH Operational
Metis Operational
Mode Operational
Monad Operational
Moonbeam Operational
Mythos Operational
opBNB Operational
Optimism Operational
Pharos Operational
Plasma Operational
Polygon Operational
Polygon zkEVM Operational
Polynomial Operational
Rise Operational
Robinhood Operational
Ronin Operational
Rootstock Operational
Scroll Operational
SEI Operational
Settlus Operational
Shape Operational
Soneium Operational
Sonic Operational
Stable Operational
Starknet Operational
Stellar Operational
Story Operational
Sui Operational
Superseed Operational
Syndicate Operational
Tempo Operational
Tron Operational
Unichain Operational
Validator Operational
World Chain Operational
WorldMobile Operational
X-Layer Operational
XMTP Operational
Zetachain Operational
ZKsync Operational
Zora Operational
Alchemy Dashboard Operational
US East Operational
EU Central Operational
US West Operational
AP SE Operational
Katana Operational
Metal Operational
Codex Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

SEI Mainnet v6.6 Upgrade Aug 4, 2026 16:30-19:30 UTC

Sei is performing a coordinated v6.6 upgrade on pacific-1 (mainnet). Requests to SEI Mainnet may be briefly unavailable during the upgrade window.
Posted on Jul 31, 2026 - 14:13 UTC

Jul 31, 2026

Hyperliquid Mainnet - Degraded Performance in Asia Pacific Region
Resolved - This incident has been resolved.
Jul 31, 16:02 UTC
Update - We are continuing to investigate this issue.
Jul 31, 15:23 UTC
Investigating - A subset of requests on Hyperliquid Mainnet routed through our Asia Pacific region are seeing increased delays and elevated error rates.
Jul 31, 15:08 UTC
Monad Mainnet - Increased eth_getLogs Latency in EU Central Region
Resolved - This incident has been resolved.
Jul 31, 14:23 UTC
Investigating - A subset of eth_getLogs requests on Monad Mainnet routed through our EU Central region are seeing increased delays.
Jul 31, 13:19 UTC
Degraded Performance on Sui Mainnet
Resolved - This incident has been resolved.
Jul 31, 02:49 UTC
Update - We are continuing to investigate this issue.
Jul 31, 01:09 UTC
Investigating - We are investigating degraded performance affecting requests on Sui Mainnet.
Jul 31, 01:07 UTC

Jul 30, 2026

Robinhood Mainnet - Elevated Latency
Resolved - Between 22:35 and 22:55 UTC on July 30, a subset of requests on Robinhood Mainnet experienced elevated latency. This incident has been resolved.
Jul 30, 21:30 UTC
Hyperliquid Elevated Latency Europe Region
Resolved - This incident has been resolved.
Jul 30, 17:10 UTC
Investigating - A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet are seeing increased delays for requests routed through our EU Central region.
Jul 30, 16:04 UTC

Jul 29, 2026

Elevated Hyperliquid Latency in US East Region
Postmortem - Read details
Jul 29, 12:46 UTC
Resolved - This incident has been resolved.
Jul 29, 08:00 UTC
Investigating - Some requests to Hyperliquid Mainnet routed through our US East region may be experiencing elevated latency. We are investigating.
Jul 28, 14:06 UTC

Jul 28, 2026

[Network-Wide] Base Mainnet Safe Head Delayed
Resolved - This is resolved. Base Mainnet's Safe head has caught up and data batching to Ethereum L1 is back to normal. Block production was unaffected throughout. See the Base status page for their full update: https://status.base.org/incidents/j6y12tshwkcg
Jul 28, 15:33 UTC
Identified - This is a network-wide issue on Base Mainnet, not specific to Alchemy. The Safe head is delayed because data batching to Ethereum L1 is lagging. New block production on Base Mainnet is progressing normally, and requests against the latest block are unaffected. Only queries and workflows that depend on the safe or finalized block tag will see staleness. Refer to the Base status page for the latest updates: https://status.base.org/incidents/j6y12tshwkcg
Jul 28, 13:32 UTC
Investigating - We are investigating a network-wide stall affecting safe and finalized blocks on Base Mainnet.
Jul 28, 13:26 UTC
Polygon Amoy Testnet - Scheduled Load Testing
Completed - The scheduled maintenance has been completed.
Jul 28, 04:35 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 27, 18:35 UTC
Scheduled - Load and stress testing is being performed on Polygon Amoy Testnet during this window, resulting in higher-than-usual network load. No impact is expected, though some network-wide latency increase may occur on Amoy during the test.
Jul 27, 18:31 UTC

Jul 27, 2026

SEI Testnet v6.6 Upgrade
Completed - The scheduled maintenance has been completed.
Jul 27, 21:00 UTC
Scheduled - Sei is performing a coordinated v6.6 upgrade on atlantic-2 (testnet). Requests to SEI Testnet may be briefly unavailable during the upgrade window.
Jul 27, 18:32 UTC
Stable Mainnet - Degraded Performance
Resolved - Nodes have recovered and services are healthy again.
Jul 27, 06:51 UTC
Identified - Nodes were unable to progress, team carried out a restart of the nodes and are seeing recovery and improved performance on requests. Actively monitoring.
Jul 27, 06:32 UTC
Investigating - A subset of requests on Stable Mainnet are experiencing degraded
Jul 27, 03:39 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

Cronos Mainnet - Degraded performance
Resolved - Nodes have been rescyned with stable binary and services are back to healthy.
Jul 24, 12:49 UTC
Identified - A part of our Cronos nodes were down due to a binary issue.
Jul 24, 12:48 UTC
Update - We are continuing to investigate this issue.
Jul 24, 09:36 UTC
Investigating - A subset of requests on Cronos Mainnet are experiencing availability issues.
Jul 24, 09:36 UTC
Stable Mainnet - Degraded Performance
Resolved - This incident has been resolved.
Jul 24, 12:00 UTC
Update - Full nodes (at head) are seeing good traffic and stable performance!

Archive nodes are still being worked on - ETA 1 hour if things go well. We'll continue to provide updates as we make progress!
Jul 23, 13:20 UTC
Update - The team is aware Stable Mainnet nodes are down, actively investigating and recovering the nodes via snapshots.
Jul 23, 09:36 UTC
Identified - A subset of requests on Stable Mainnet are experiencing degraded performance.
Jul 23, 09:34 UTC
Robinhood Mainnet - Elevated Latency in Asia Pacific
Resolved - This incident has been resolved.
Jul 24, 11:09 UTC
Investigating - A subset of requests on Robinhood Mainnet routed through our Asia Pacific region may be experiencing increased latency.
Jul 23, 15:12 UTC

Jul 23, 2026

Jul 22, 2026

WebSocket Connectivity Issue in US West Region
Resolved - Traffic has been fully restored to the US West region. This incident is now resolved!
Jul 22, 21:00 UTC
Identified - We identified the root cause and the affected service has been failed over. We are monitoring for full recovery!
Jul 22, 19:18 UTC
Investigating - We're investigating an issue impacting WebSocket connectivity in US West region.
Jul 22, 15:51 UTC
[Network-Wide] Multiple Networks Stall
Resolved - Resolved: All impacted networks, including Mode Sepolia (testnet), have fully recovered and caught up. This incident is now resolved.
Jul 22, 18:42 UTC
Update - Update: All impacted networks have recovered except Mode Sepolia (testnet), which is still degraded. We are continuing to monitor Mode Sepolia.
Jul 22, 18:17 UTC
Monitoring - Update: Zora has recovered. Mode mainnet has recovered; Mode Sepolia (testnet) is still degraded. Ronin, BOB, Codex, and Superseed remain impacted. We are continuing to monitor.
Jul 22, 18:15 UTC
Update - We are investigating a network-wide stall affecting Zora, Ronin, BOB, Codex, Mode, and Superseed networks.
Jul 22, 18:13 UTC
Investigating - We are investigating a network-wide stall affecting Zora, Ronin, BOB, Katana, Mode, Metal, and Superseed networks.
Jul 22, 18:07 UTC
BNB Smart Chain Mainnet - Degraded Performance
Resolved - We have confirmed full recovery across our BNB Smart Chain Mainnet infrastructure. All nodes are healthy and serving traffic normally, with response times and error rates back to baseline. This incident is now resolved. Thank you for your patience!
Jul 22, 14:43 UTC
Identified - We experienced node-level failure on BNB Mainnet which caused a subset of our nodes to become unavailable. As a result, increased load was placed on our remaining infrastructure, further contributing to degraded response times. A node binary fix was deployed and we are seeing recovery.
Jul 22, 11:02 UTC
Investigating - We are investigating elevated error rates and increased latency on BNB Smart Chain Mainnet. Some requests may fail or respond slower than usual. Our team is actively working on a fix and we will post updates here as we learn more.
Jul 22, 07:45 UTC

Jul 21, 2026

Soneium Mainnet Service Degradation
Resolved - This incident has been resolved.
Jul 21, 22:42 UTC
Investigating - We are currently investigating an issue impacting transaction propagation on Soneium Mainnet.
Jul 21, 20:49 UTC

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

Resolved: Elevated latency on Polygon Mainnet
Resolved - Between approximately 23:20 UTC on July 17 and 03:30 UTC on July 18, some Polygon Mainnet requests experienced slower than normal response times, mainly for log queries. The issue was limited to the us-east-1 region.
The cause was an unusually heavy request load that put pressure on part of our infrastructure in the region. We added extra capacity and rebalanced traffic, after which performance returned to normal.

The issue is fully resolved. We apologize for the disruption.
Jul 17, 20:00 UTC
← Incident History Powered by Atlassian Statuspage