Alchemy Outage History
Alchemy is up right nowPingoru has recorded 199 incidents for Alchemy: 199 in the last 12 months and 61 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 30 | 500 of 720 (70%) |
| May 2026 | 29 | 297 of 744 (40%) |
| June 2026 | 20 | 221 of 720 (31%) |
| July 2026 | 33 | 112 of 744 (15%) |
| August 2026 | 26 | 172 of 744 (23%) |
| September 2026 | 15 | 63 of 720 (9%) |
| October 2026 | 13 | 100 of 585 (17%) |
Incidents, newest first
Minor August 5, 2026 Multiple Networks - Increased eth_getUserOperationReceipt Latency 13m Ethereum, Arbitrum, Base, Polygon and 2 more
Started Aug 05, 2026, 05:22 PM UTC· resolved Aug 05, 2026, 05:35 PM UTC
- resolved Aug 05, 2026, 06:13 PM UTC
Between 17:22 and 17:35 UTC on August 5, a subset of eth_getUserOperationReceipt requests across multiple networks experienced increased latencies. This incident has been resolved.
Minor July 31, 2026 Hyperliquid Mainnet - Degraded Performance in Asia Pacific Region 53m HyperEVM
Started Jul 31, 2026, 03:08 PM UTC· resolved Jul 31, 2026, 04:02 PM UTC
- investigating Jul 31, 2026, 03:08 PM UTC
A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet routed through our Asia Pacific region are seeing increased delays and elevated error rates.
- investigating Jul 31, 2026, 03:23 PM UTC
We are continuing to investigate this issue.
- resolved Jul 31, 2026, 04:02 PM UTC
This incident has been resolved.
Minor July 31, 2026 Monad Mainnet - Increased eth_getLogs Latency in EU Central Region 1h 4m Monad
Started Jul 31, 2026, 01:19 PM UTC· resolved Jul 31, 2026, 02:23 PM UTC
- investigating Jul 31, 2026, 01:19 PM UTC
A subset of eth_getLogs requests on Monad Mainnet routed through our EU Central region are seeing increased delays.
- resolved Jul 31, 2026, 02:23 PM UTC
This incident has been resolved.
Minor July 31, 2026 Degraded Performance on Sui Mainnet 1h 41m Sui
Started Jul 31, 2026, 01:07 AM UTC· resolved Jul 31, 2026, 02:49 AM UTC
- investigating Jul 31, 2026, 01:07 AM UTC
We are investigating degraded performance affecting requests on Sui Mainnet.
- investigating Jul 31, 2026, 01:09 AM UTC
We are continuing to investigate this issue.
- resolved Jul 31, 2026, 02:49 AM UTC
This incident has been resolved.
Minor July 30, 2026 Hyperliquid Elevated Latency Europe Region 1h 5m HyperEVM
Started Jul 30, 2026, 04:04 PM UTC· resolved Jul 30, 2026, 05:10 PM UTC
- investigating Jul 30, 2026, 04:04 PM UTC
A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet are seeing increased delays for requests routed through our EU Central region.
- resolved Jul 30, 2026, 05:10 PM UTC
This incident has been resolved.
Minor July 30, 2026 Robinhood Mainnet - Elevated Latency 21h 30m Robinhood
Started Jul 30, 2026, 12:00 AM UTC· resolved Jul 30, 2026, 09:30 PM UTC
- resolved Jul 30, 2026, 11:48 PM UTC
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.
Minor July 28, 2026 Elevated Hyperliquid Latency in US East Region 17h 54m HyperEVM
Started Jul 28, 2026, 02:06 PM UTC· resolved Jul 29, 2026, 08:00 AM UTC
- investigating Jul 28, 2026, 02:06 PM UTC
Some requests to Hyperliquid Mainnet routed through our US East region may be experiencing elevated latency. We are investigating.
- resolved Jul 29, 2026, 11:19 AM UTC
This incident has been resolved.
- postmortem Jul 29, 2026, 12:24 PM UTC
Between 13:30 UTC on July 28 and 08:00 UTC on July 29, HYPERLIQUID\_MAINNET requests served from us-east experienced elevated latency, and `eth_sendRawTransaction` returned a high rate of errors. Read methods remained available throughout, with elevated response times. **Impact** Transaction submission was the primary failure mode. During the peak period, the large majority of `eth_sendRawTransaction` requests either timed out or returned an error, and clients retrying submissions saw sustained failures. Read traffic on the network was slower than normal but continued to be served successfully. Latency was elevated for all HYPERLIQUID\_MAINNET request types for the duration of the event. **Root cause** A majority of our Hyperliquid full nodes in us-east lost peering with the network. The nodes were unable to complete state synchronization handshakes with upstream peers -- connection attempts were rate limited, timed out, or rejected because peer connection slots were full. Affected nodes fell behind and were removed from the healthy serving pool. Recovery required the upstream peer pool to free capacity; feeding new peers into the configuration and pruning node state did not restore peering. Two factors extended the impact: * With that capacity gone, all us-east traffic concentrated on the remaining archive node pool, which pushed latency up further and made `eth_sendRawTransaction` the first method to fail. * On Hyperliquid, transactions are not propagated peer-to-peer. They are relayed to a network-level submission endpoint that can rate limit, which means the transaction submission path is sensitive to network conditions independent of which infrastructure serves the request. **Resolution** We began routing `eth_sendRawTransaction` to secondary infra as soon as the issue was identified, but this did not restore transaction submission. Submissions relayed through secondary infra continued to fail at a comparable rate, since that path depends on the same network-level submission endpoint. A subset of nodes began to recover from around 01:30 UTC on July 29, when the first `hlnode` in us-east returned to a healthy state as upstream peer capacity freed up. Server-side errors from our serving layer dropped off around the same time, though submissions continued to fail through a mix of remaining unhealthy nodes and rejections at the network's submission endpoint. Peering re-established across the rest of the pool over the following hours. Latency returned to normal levels by approximately 08:00 UTC, request volumes and error rates returned to baseline, and all us-east nodes were confirmed healthy shortly afterward. **Follow-up** We are exploring running our own validator and sentry nodes for Hyperliquid so that peering no longer depends on availability in the shared public peer pool.
Minor July 28, 2026 [Network-Wide] Base Mainnet Safe Head Delayed 2h 6m Base
Started Jul 28, 2026, 01:26 PM UTC· resolved Jul 28, 2026, 03:33 PM UTC
- investigating Jul 28, 2026, 01:26 PM UTC
We are investigating a network-wide stall affecting safe and finalized blocks on Base Mainnet.
- identified Jul 28, 2026, 01:32 PM UTC
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
- resolved Jul 28, 2026, 03:33 PM UTC
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
Minor July 27, 2026 Stable Mainnet - Degraded Performance 3h 11m Stable
Started Jul 27, 2026, 03:39 AM UTC· resolved Jul 27, 2026, 06:51 AM UTC
- investigating Jul 27, 2026, 03:39 AM UTC
A subset of requests on Stable Mainnet are experiencing degraded
- identified Jul 27, 2026, 06:32 AM UTC
Nodes were unable to progress, team carried out a restart of the nodes and are seeing recovery and improved performance on requests. Actively monitoring.
- resolved Jul 27, 2026, 06:51 AM UTC
Nodes have recovered and services are healthy again.
Minor July 24, 2026 Cronos Mainnet - Degraded performance 3h 12m Cronos
Started Jul 24, 2026, 09:36 AM UTC· resolved Jul 24, 2026, 12:49 PM UTC
- investigating Jul 24, 2026, 09:36 AM UTC
A subset of requests on Cronos Mainnet are experiencing availability issues.
- investigating Jul 24, 2026, 09:36 AM UTC
We are continuing to investigate this issue.
- identified Jul 24, 2026, 12:48 PM UTC
A part of our Cronos nodes were down due to a binary issue.
- resolved Jul 24, 2026, 12:49 PM UTC
Nodes have been rescyned with stable binary and services are back to healthy.
Minor July 23, 2026 Robinhood Mainnet - Elevated Latency in Asia Pacific 19h 57m Robinhood
Started Jul 23, 2026, 03:12 PM UTC· resolved Jul 24, 2026, 11:09 AM UTC
- investigating Jul 23, 2026, 03:12 PM UTC
A subset of requests on Robinhood Mainnet routed through our Asia Pacific region may be experiencing increased latency.
- resolved Jul 24, 2026, 11:09 AM UTC
This incident has been resolved.
Critical July 22, 2026 [Network-Wide] Multiple Networks Stall 34m BOB, Mode, Ronin, Superseed and 3 more
Started Jul 22, 2026, 06:07 PM UTC· resolved Jul 22, 2026, 06:42 PM UTC
- investigating Jul 22, 2026, 06:07 PM UTC
We are investigating a network-wide stall affecting Zora, Ronin, BOB, Katana, Mode, Metal, and Superseed networks.
- investigating Jul 22, 2026, 06:13 PM UTC
We are investigating a network-wide stall affecting Zora, Ronin, BOB, Codex, Mode, and Superseed networks.
- monitoring Jul 22, 2026, 06:15 PM UTC
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.
- monitoring Jul 22, 2026, 06:17 PM UTC
Update: All impacted networks have recovered except Mode Sepolia (testnet), which is still degraded. We are continuing to monitor Mode Sepolia.
- resolved Jul 22, 2026, 06:42 PM UTC
Resolved: All impacted networks, including Mode Sepolia (testnet), have fully recovered and caught up. This incident is now resolved.
Minor July 22, 2026 WebSocket Connectivity Issue in US West Region 5h 9m US West
Started Jul 22, 2026, 03:51 PM UTC· resolved Jul 22, 2026, 09:00 PM UTC
- investigating Jul 22, 2026, 03:51 PM UTC
We are investigating elevated latency affecting a subset of requests in our US West region.
- identified Jul 22, 2026, 07:18 PM UTC
We identified the root cause and the affected service has been failed over. We are monitoring for full recovery!
- resolved Jul 23, 2026, 06:14 PM UTC
Traffic has been fully restored to the US West region. This incident is now resolved!
Minor July 22, 2026 BNB Smart Chain Mainnet - Degraded Performance 6h 57m BNB Smart Chain
Started Jul 22, 2026, 07:45 AM UTC· resolved Jul 22, 2026, 02:43 PM UTC
- investigating Jul 22, 2026, 08:16 AM UTC
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.
- identified Jul 22, 2026, 11:02 AM UTC
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.
- resolved Jul 22, 2026, 02:43 PM UTC
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!
Minor July 21, 2026 Soneium Mainnet Service Degradation 1h 52m Soneium
Started Jul 21, 2026, 08:49 PM UTC· resolved Jul 21, 2026, 10:42 PM UTC
- investigating Jul 21, 2026, 09:49 PM UTC
We are currently investigating an issue impacting transaction propagation on Soneium Mainnet.
- resolved Jul 21, 2026, 10:42 PM UTC
This incident has been resolved.
Notice July 17, 2026 Resolved: Elevated latency on Polygon Mainnet –
Started Jul 17, 2026, 08:00 PM UTC· resolved Jul 17, 2026, 08:00 PM UTC
- resolved Jul 18, 2026, 09:02 AM UTC
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.
Minor July 16, 2026 Zora Sepolia Degraded Performance 31m Zora
Started Jul 16, 2026, 04:20 AM UTC· resolved Jul 16, 2026, 04:51 AM UTC
- investigating Jul 16, 2026, 04:20 AM UTC
We are currently investigating an issue affecting Zora Sepolia nodes, resulting in failed requests and errors on this network. Our team is actively working to restore service and is coordinating with the Zora team on a resolution. We will provide an update as soon as we have more information.
- resolved Jul 16, 2026, 04:51 AM UTC
This incident has been resolved.
Minor July 15, 2026 [Network-Wide] Abstract Mainnet Safe Head Stall 4h 52m Abstract
Started Jul 15, 2026, 11:09 PM UTC· resolved Jul 16, 2026, 04:02 AM UTC
- investigating Jul 15, 2026, 11:09 PM UTC
We are investigating a network-wide stall affecting safe and finalized blocks on Abstract Mainnet.
- resolved Jul 16, 2026, 04:02 AM UTC
This incident has been resolved.
Minor July 15, 2026 Degraded eth_getLogs across multiple networks 14m Ethereum, Polygon, World Chain
Started Jul 15, 2026, 05:00 PM UTC· resolved Jul 15, 2026, 05:15 PM UTC
- identified Jul 15, 2026, 02:52 PM UTC
We're investigating elevated error rates and latency on eth_getLogs across multiple networks. We've identified the cause and are actively working on mitigation. We'll share an update as recovery progresses.
- identified Jul 15, 2026, 05:16 PM UTC
The fix that we have applied is working well for Ethereum and Polygon mainnets, and we see full recovery there. Our team continues to work on recovering Worldchain.
- monitoring Jul 15, 2026, 05:21 PM UTC
We have applied a fix for all of the impacted chains and are monitoring the results.
- resolved Jul 15, 2026, 05:33 PM UTC
This incident has been resolved.
Minor July 15, 2026 Degraded performance on Solana mainnet – Solana, US West, AP SE
Started Jul 15, 2026, 04:25 PM UTC· resolved Jul 15, 2026, 04:25 PM UTC
- investigating Jul 15, 2026, 04:00 PM UTC
We are currently investigating an issue resulting in increased errors and latency on Solana mainnet.
- identified Jul 15, 2026, 04:25 PM UTC
The issue has been identified and we've rolled out a fix.
- resolved Jul 15, 2026, 04:51 PM UTC
This incident has been resolved.
Minor July 15, 2026 Elevated Latency on Tempo Moderato 3h 33m Tempo
Started Jul 15, 2026, 01:17 PM UTC· resolved Jul 15, 2026, 04:50 PM UTC
- investigating Jul 15, 2026, 01:17 PM UTC
We're seeing increased latency and higher block times on Tempo Testnet. This is caused by a planned stress test run by the Tempo network team, not by Alchemy infrastructure. The test window is expected to last up to 2 hours starting 2PM UTC on July 15. Performance should recover once the test concludes. No action is required on your end.
- investigating Jul 15, 2026, 04:50 PM UTC
We are continuing to investigate this issue.
- resolved Jul 15, 2026, 04:50 PM UTC
This incident has been resolved.
Minor July 14, 2026 Degraded Performance on Cronos Mainnet 1h 3m Cronos
Started Jul 14, 2026, 11:48 PM UTC· resolved Jul 15, 2026, 12:52 AM UTC
- investigating Jul 14, 2026, 11:48 PM UTC
We're currently investigating an issue impacting performance on Cronos Mainnet.
- identified Jul 14, 2026, 11:53 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 15, 2026, 12:52 AM UTC
This incident has been resolved.
Minor July 13, 2026 Robinhood Mainnet - Delayed User Operation Inclusion Times 4m Robinhood
Started Jul 13, 2026, 09:09 PM UTC· resolved Jul 13, 2026, 09:13 PM UTC
- investigating Jul 13, 2026, 09:09 PM UTC
We are actively investigating an issue affecting Robinhood Mainnet where there are delayed user operation inclusion times.
- resolved Jul 13, 2026, 09:13 PM UTC
We are currently seeing recovery.
Minor July 10, 2026 Degraded Performance for Data APIs 44m BNB Smart Chain
Started Jul 10, 2026, 03:16 PM UTC· resolved Jul 10, 2026, 04:01 PM UTC
- investigating Jul 10, 2026, 03:16 PM UTC
We are investigating degraded performance affecting our Data APIs on BNB Smart Chain. A subset of requests may experience errors or increased latency.
- investigating Jul 10, 2026, 03:26 PM UTC
We are continuing to investigate this issue.
- investigating Jul 10, 2026, 03:27 PM UTC
We are continuing to investigate this issue.
- resolved Jul 10, 2026, 04:01 PM UTC
This incident has been resolved.
Notice July 10, 2026 Increased 5xxs in US East Region on Robinhood Mainnet –
Started Jul 10, 2026, 10:00 AM UTC· resolved Jul 10, 2026, 10:00 AM UTC
- resolved Jul 10, 2026, 02:27 PM UTC
This incident has been resolved.