Is Alchemy Down Right Now? Discover if there is an ongoing service outage.

We are currently investigating occasional errors on BNB Chain. Customers may experience degraded performance.

We are currently investigating occasional errors on BNB Chain. Customers may experience degraded performance.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating occasional errors on BNB Chain. Customers may experience degraded performance.

We’re currently investigating elevated error rates for requests made to the legacy domain alchemyapi.io. This issue affects traffic routed through that domain. Requests sent to the new domain (*.g.alchemy.com) are not impacted and continue to perform as expected.

We’re aware of an ongoing issue impacting Unichain Mainnet. This is currently causing a stall in safe head progression and no new state root updates. Transactions may still be submitted but confirmations and finalized state updates may be delayed until mitigation is complete. The Unichain team has shared a tentative mitigation time of ~2 hours. We’re closely monitoring the situation and will provide updates as soon as more information becomes available!

We are continuing to investigate this issue.

We are currently observing intermittent latency and error rates on some requests routed through the US-East (IAD) region. Customers with traffic routed through US-East may see increased latency and occasional errors. This is tied to scheduled maintenance from one of our infrastructure providers Cloudflare - see status page here: https://www.cloudflarestatus.com/incidents/8m430h71zy9c We are monitoring the situation closely with Cloudflare team

Celo Alfajores block production is stalled on block 58410172 mined (Oct-02-2025 12:38:12 AM +UTC): https://alfajores.celoscan.io/block/58410172 This is a network wide incident and we'll keep this status page up to date

We're currently encountering latencies in USE1 Region. We're actively investigating with our eng team - we'll keep this page updated alongside our findings

The Linea Sepolia network will undergo the Shanghai hardfork. During this upgrade, downtime and stalls are expected for node operators (including our infrastructure). We will monitor the network closely throughout the maintenance and restore full functionality as soon as possible after the upgrade is complete.

We are currently observing SSL issues impacting customer traffic, with confirmed effects on Scroll and Shape chains and potential impact on additional chains. Our team is actively engaged with the Cloudflare team to identify the root cause and restore normal operations.

We are currently investigating this issue.

The issue has been identified and we are rolling out a fix.

We are currently investigating the issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

We are currently investigating this issue.

Scheduled Start: Monday, September 29, 2025, at 08:00 AM UTC Scheduled End: Monday, September 29, 2025, at 11:00 AM UTC Impact: No downtime expected Details: Polygon mainnet has announced a scheduled hard fork on October 8, 2025, at 14:12 UTC. To prepare for this event, we will be upgrading our Polygon mainnet nodes ahead of time on September 29, 2025, starting at 08:00 AM UTC. The upgrade is expected to take approximately 3 hours. This upgrade ensures our infrastructure is aligned with the Bor v2.3.0 and Heimdall v0.4.0 releases, part of the Rio hard fork for the Veblop upgrade. You can find more information here: https://forum.polygon.technology/t/bor-v2-3-0-and-heimdall-v0-4-0-release-rio-hard-fork-for-veblop-upgrade/21310

Start Time: 15:00 UTC End Time: 16:00 UTC The Linea Sepolia network will undergo the Pectra Upgrade during this window. As part of the upgrade, downtime and stalls are expected for node operators relying on Geth (including our infrastructure). We will monitor the network closely throughout the maintenance and restore full functionality as soon as possible after the upgrade is complete.

We are investigating increased latency in the USE1 region and are actively coordinating with the Cloudflare team to resolve the issue.

We are currently investigating this.

Block production stopped for upgrade window

Scheduled: Sep 17, 2025 – 15:00 to 17:00 UTC Components Affected: Flow Testnet RPC & related services Description: The Flow Testnet will undergo the Forte Network Upgrade, unlocking new composability and automation features for developers and AI agents. During this time, some testnet services on Alchemy may be temporarily unavailable. Impact: Testnet SendTransaction operations may be unavailable. Public endpoints will remain available for reading chain data. Mainnet services remain fully operational. More info: https://status.flow.com/incidents/2x404y0vkn8b

We are continuing to investigate this issue.

Status: Partial Mitigation / Upgrade in Progress Regions Affected: EUC, APAC Details: We recently observed elevated latencies and errors on ETH Mainnet due to an issue with a subset of Reth nodes. Mitigation steps have been applied: traffic is currently served from our Geth nodes in USE1, and Reth node upgrades are underway. Current Impact: Customers in the APAC region may experience slightly higher latencies while node upgrades are in progress. EUC region has been fully upgraded, and traffic is now being served normally. Next Steps: Complete rolling upgrade of Reth nodes in APAC. Re-enable all regions once upgrades are stable. Disable full forwarding for trace methods after the upgrade is fully complete to restore normal operation. Updates: We will provide further updates as the APAC region upgrade completes and all regions return to normal latencies. Please reach out if you have any questions!

We are currently investigating this issue.

Some customer may experience performance degradation. We are investigating this issue

We are currently investigating this issue.

We are currently investigating elevated errors on world chain related to our open incident on Ethereum mainnet.

We are currently investigating this issue.

We are currently investigating this issue.

We identified elevated latency problems on Linea due to greatly increased traffic. We made some adjustments and monitoring the results.

We are currently investigating this issue.

Cloudflare identified an incident across all of their products. Alchemy services may be interrupted and customers may see 503 errors.

We are currently investigating this issue.

We are currently seeing issues with our Zetachain Mainnet nodes. Our team is actively investigating.

Since the recent Starknet re-org we've seen issues across our Starknet nodes fleet. We are actively investigating solutions.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

The Starknet team has announced that the Grinta upgrade (v0.14) will take place on Monday, September 1st at 6:00 AM GMT. This is a chain-wide upgrade introducing a decentralized architecture, mempool, and preconfirmation support to improve the user experience. The Starknet team has acknowledged that a temporary downtime of approximately 15 minutes is expected during the upgrade. Thank you for your patience and understanding.

A network-wide issue is currently affecting ZkSync Mainnet, which is causing node crashes. Our team is actively collaborating with the ZkSync engineering team to resolve this as quickly as possible. Customers may observe elevated 5xx error rates as a result of this incident.

We're currently experiencing an elevated 503s errors on Rollups chains with Wallet Services / Account Abstractions endpoints and specifically with alchemy_requestGasAndPaymasterAndData. Will share updated as we'll uncover more!

We're currently being impacted by a Cloudflare incident. We're actively investigating with Cloudflare team and will update this status page with our latest findings!

We're currently investigating an underlying issue from Sei validators not created new blocks on chain and creating a backlog of pending transactions. We're working closely with Sei team to understand the root cause and assess impact

Polygon ZKEVM is currently experiencing a stall block production. The latest block produced was 24940457: https://zkevm.polygonscan.com/

We're currently seeing increased latencies with third party providers, we're investigating and we'll updates to this page!

We're currently seeing an elevated -32603 errors on Base Mainnet with getTransactionReceipts and Transfers API endpoints. We're actively investigating and we'll keep this status page updated!

The Base Sepolia chain is currently halted - this is a network wide incident reported by the Base team: https://status.base.org/incidents/hm21kw149p5x

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

We are currently investigating reports of increased latency affecting services on all network in the EUC1 (Europe Central) and APSE1 (Asia Pacific Southeast) regions. Our engineering team is working to identify the cause and mitigate impact. We will provide updates as soon as more information is available.

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

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

We are currently observing a partial service degradation impacting the Blast API segment of our infrastructure across multiple chains. Affected systems are experiencing elevated latency, intermittent request failures, and block propagation delays across multiple regions. This may result in: Authentication Failures: Users may be unable to log in due to timeouts or dropped authentication requests. Block Lag: Delayed synchronization with the latest chain state, potentially impacting transaction visibility and confirmation times. We will provide continuous updates as remediation progresses and full service performance is restored.

Monad BFT Consensus goes live on public testnet This is the first tail-fork-resistant consensus mechanism on the EVM Testnet will halt at 13:30 GMT for implementation

From 11:20 UTC to 11:41 UTC We're working on a few improvements to speed up routing & pushed a configuration that was slightly off in our European data centers. This has been fixed. We are adding guardrails to make sure this won't happen again!!

Due to an issue with an infra provider, we're seeing increased latencies for requests hitting our EU stack. We're working closely with our provider, as they resolve this issue on their end!

We're currently experiencing increased latency and timeout errors across our EAPI services including endpoints such as our Portfolio API. Our team is actively investigating the root cause and working to restore normal performance as quickly as possible.

We are currently observing a protocol-wide halt on the Polygon mainnet at block height 74,592,238. This disruption is impacting transaction finalization, block propagation, and all dependent network operations. Our engineering team is actively implementing a node upgrade to remediate the issue.

We are currently investigating.

We are currently investigating

Our infrastructure experienced a brief service disruption today between 06:05 AM UTC and 06:17 AM UTC across our EVM chains. During this window, we observed elevated error rates and increased latency due to unusually high traffic, due to an overloaded service. We've mitigated the issue by rate limiting the source, and everything is now fully stabilized. We apologize for any inconvenience this may have caused

We are currently investigating this issue.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We’re currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue!

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating increased latency and errors for NFT API endpoints.

We are currently investigating this issue.

This incident has been resolved.

We're seeing the block production halted on Flow Test at the network level

We are currently investigating this issue.

We're actively investigating issues impacting Lens Testnet

Cela Alfajores block production is stalled on block 51109972 - see explorer here: https://alfajores.celoscan.io/block/51109972 This is a network wide incident and we're working with Celo team for a fix!

We're seeing the Finalized block stalled on 21275800 since ~01:42 UTC This is related to this incident from Unichain: https://status.unichain.org/cmcvcwdwv001oc3nwefxc4k17 Our nodes are catching-up and will update this status page accordingly!

We are currently investigating this issue.

We're currently seeing Botanix Testnet block production stalled on block 3072275: https://3636.testnet.routescan.io/block/3072275 This is a network wide incident and we're working closely with Botanix team!

We have identified a network stall on Solana Devnet. Please note that this stall is only affecting Devnet - not Mainnet nor Testnet.

The Erigon portion of our Polygon Mainnet node fleet is currently stalled. This is a network-wide issue, and we're working closely with the Polygon team to fix it. As a result, you may experience 503 errors or request timeouts. We will provide regular updates as we resolve this.

The issue has been identified and a fix is being implemented.

We’ve observed elevated errors and latency across multiple networks for our NFT, Transfers, and Token Balances APIs. We are actively investigating the issue.

We’ve observed elevated 503 errors across multiple networks for our NFT, Transfers, and Token Balances APIs. We are actively investigating the issue.

We saw a short spike in latency from APAC region, and have recovered our nodes. We're actively monitoring a recovery now!

We've identified the issue and are applying a fix.

We are currently investigating this issue!

This incident has been resolved.

We are actively investigating this issue!

This incident has been resolved.

We are actively investigating this issue!

This incident has been resolved.

Working with zksync team to resolve network wide issues

This incident has been resolved.

Seeing network wide issues on Zksync Sepolia. We have flagged to the Zksync team and are actively investigating!

This incident has been resolved.

Working with zksync team to resolve network wide issues

This incident has been resolved.

Seeing network wide issues on Zksync Sepolia. We have flagged to the Zksync team and are actively investigating!

This incident has been resolved.

We observed that Unichain Sepolia is stuck on Block 21818269. This is a network wide incident: https://unichain-sepolia.blockscout.com/

This incident has been resolved.

We observed that Unichain Sepolia is stuck on Block 21818269. This is a network wide incident: https://unichain-sepolia.blockscout.com/

This incident has been resolved.

We're currently investigating on an elevated 503s currently happening on Matic Amoy

This incident has been resolved.

We're currently investigating on an elevated 503s currently happening on Matic Amoy

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

World will be conducting game day testing on World Chain Sepolia between 10:00am ET Wed 5/21 through 4:00pm ET Fri 5/23. You may see block production stall or reorgs on the chain during this time.

This incident has been resolved.

We are currently investigating an issue where the usage chart in the Alchemy Dashboard says "Deactivated App" for apps that are not deactivated. Please note that only the UI is affected - there are no issues processing requests to these apps.

This incident has been resolved.

We are currently investigating an issue where the usage chart in the Alchemy Dashboard says "Deactivated App" for apps that are not deactivated. Please note that only the UI is affected - there are no issues processing requests to these apps.

We are now fully upgraded to the newest RETH patch: v1.4.2.

We have downgraded our RETH nodes to v1.3.12, which has resolved the issue. We are continuing to work with the RETH team to patch v1.4.1, and will mark this incident as "Resolved" when we are able to re-upgrade to v1.4.1.

The issue has been identified, and is related to the v1.4.1 RETH upgrade. We are working with the RETH team to patch this upgrade and resolve the issue.

We are currently investigating an incident where eth_getLogs is returning no logs on certain chains, including Base Mainnet and Eth Sepolia

This incident has been resolved.

The Base team has identified an extremely large number of transactions in the mempool, which is causing the sequencer to accept transactions at a slower rate. This is a network-wide issue and we are actively monitoring it. You can reference Base's official status page as well for the latest updates: https://status.base.org/

This incident has been resolved.

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

We are currently investigating the issue

This incident has been resolved.

The sequencer has cleared, and we observe a significant improvement in the transaction landing time.

The Base team has identified an extremely large number of transactions in the mempool, which is causing the sequencer to accept transactions at a slower rate. This is a network-wide issue and we are actively monitoring it.

This incident has been resolved.

Seeing increased error rates on Sei Mainnet, we are investigating the issue.

This incident has been resolved.

We are currently investigating this issue.

From approximately 08:30 UTC to 09:30 UTC we experienced degraded performance on a subset of networks which would have manifested downstream as an 'Authentication failed' error. This impacted our Wallet Service and Subgraph products as well. Mitigation efforts have been completed and services are operational. We sincerely apologize for the disruption this may have caused.

We've isolated the issue and have begun mitigation efforts. We are seeing a decrease in 4XX response codes and services are re-syncing.

The elevated 401 response from networks is having downstream impact on RPC, Wallet Service, and Subgraph products. We are actively working to remediate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We're currently investigating delayed events for custom webhooks!

This incident has been resolved.

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

We are currently working through a issue with logging in to the Alchemy Dashboard.

This incident has been resolved. Starting at 07:54 UTC a Cloudflare maintenance event caused high latency figures across multiple networks and methods. This incident has been resolved as of 09:37UTC.

Latency metrics have stabilized, we're continuing to monitor the situation.

We are beginning to see a recovery in latency figures across networks. We are continuing to investigate.

We are actively investigating elevated latency across multiple methods and networks.

Starting at approximately 2025-04-28 10:07UTC, we experienced an issue related to log ingestion on Base which may have manifested as 'null' responses, or server errors. This incident has now been resolved as of 16:07UTC. We appreciate your patience as we worked through this.

A fix has been implemented and we are currently monitoring, metrics have stabilized.

We've identified the issue and are currently implementing a fix, node health is beginning to recover.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

Currently seeing some errors on Polygon ZkEVM which we are actively managing and investigating.

This incident has been resolved.

We're seeing some intermittent error rates across the board due to an underlying upgrade to our of systems. We're already seeing recovery on our end and will continue to monitor

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Blast Sepolia network is stalled on block 20155661: https://sepolia.blastexplorer.io/

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.

We are currently investigating an issue with Berachain Mainnet - the network is stalled and we'll share update here asap!

This incident has been resolved.

Flow testnet is encountering an incident at the network level

This incident has been resolved.

We are currently investigating an increased latencies for Europe traffic

Retroactive status page for elevated errors on user sign up and authentication with the signer. We have identified and resolved this issue.

This incident has been resolved.

We are seeing issues across base mainnet currently, https://status.base.org/

We are currently investigating this issue.

This incident, which mainly affected latency for eth_calls and alchemy_getTokenBalances, has now been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently experiencing an issue affecting internal transfer ingestion on Eth Sepolia, which has been halted. This issue is due to an ongoing problem at the node client level with Erigon on Sepolia: https://github.com/erigontech/erigon/issues/14089 Since this is an upstream issue, we are waiting for Erigon to deploy a fix! We'll keep this page up to date!

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating a dashboard issue -- you may see "Cannot read properties of undefined (reading 'json')"

This incident has been resolved.

A fix has been pushed and we are monitoring our systems.

We are currently investigating the issue.

This incident has been resolved.

Celo Mainnet will be migrating to an L2 starting on Tuesday, March 25th 7:45PM PST (2:45AM UTC Wednesday, March 26th). Expect downtime for a few hours.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are continuing to monitor for any further issues.

Alchemy Signer will not be operational on 3/19 for > 20 minutes due to scheduled maintenance on Turnkey. For reference: https://www.turnkey-status.com/ During this time: new user sign up, authentication, and signing transactions using alchemy signer will not work.

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.

We are currently investigating this issue.

This Incident has been resolved

The issue has been identified and a fix is being implemented.

This incident has been resolved.

Incident has been resolved.

A patch released by the Monad team has been deployed to our nodes. This, along with additional node resources coming online, has significantly improved our latency figures back to expected baselines. We will continue to monitor.

We are currently investigating some instability on Monad that can lead to high response time. We'll update this page alongside our findings! Thanks for your patience!

This incident has been resolved.

Following the Pectra upgrade, nodes on Blast Sepolia have been experiencing issues with eth_call. The testnet has been down, with block production also impacted. This is a network wide incident and our team is actively investigating the root cause! Further updates will be provided as soon as we have more details!

Block production has started again and our nodes have caught up!

Block production on Scroll Sepolia is stalled - latest block mined was 8486730 This is a network wide incident: https://sepolia.scrollscan.com/

This incident has been resolved.

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

We are currently observing elevated 5XX status codes with authentication on signer endpoints. Existing sessions should not be impacted. API calls and requests are not impacted.

This incident has been resolved.

Both Ink Mainnet and Sepoliare down. This is a network wide incident. We'll update this page as we discover more!

We’ve deployed a fix and the Dashboard is now fully operational again! 🚀 This incident did not impact your app’s functionality!

We saw a regression - currently investigating!

We deployed a fix and we are monitoring the situation!

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently encountering issues to log-in to the Alchemy Dahsboard! This does not prevent your app from working! Our eng team is on this and we'll share update soon! Sorry for the inconvenience!

This incident has been resolved.

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

Nodes on the current network have fallen behind the latest block number, and may return outdated block information. We're looking into the issue now and will provide an update ASAP!

This incident has been resolved.

Blocks are being mined and transactions are currently being processed.

Network wide incident on Shape Mainnet. Latest block mined #9937064. Continuing to monitor. https://shapescan.xyz/block/9937064

This incident has been resolved.

The latency seems to be related to traffic congestion on the chain. Traffic has decreased on the Monad chain as a whole and we are seeing improvements in the response times!

We are currently investigating higher latencies on Monad Testnet We'll share updates as soon as possible and appreciate your patience

The Avalanche team has released a new version (AvalancheGo v1.13.0-fuji) to address the instability issues affecting Fuji nodes: https://status.avax.network/incidents/n4dnd7sb1n6h We’ve now upgraded our nodes accordingly and everything should be running smoothly again!

Avalanche Testnet is undergoing a network wide issue Updates from Avalanche team: https://status.avax.network/incidents/n4dnd7sb1n6h