Alchemy

Affected: EU Central

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 22:30 UTC

   Some requests to Base Mainnet routed through our EU Central region may be experiencing increased latency.

2. resolved 2026-10-16 06:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Superseed

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 12:14 UTC

   We are investigating a network-wide stall on Superseed Mainnet.

2. resolved 2026-10-14 14:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Base

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 17:30 UTC

   A subset of Bundler requests on Base Mainnet are seeing increased errors.

2. monitoring 2026-10-13 21:20 UTC

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

3. resolved 2026-10-13 23:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: US West

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-13 00:45 UTC

   Some requests routed through our US West region may be experiencing degraded performance. Affected requests have been rerouted to healthy regions.

2. resolved 2026-10-13 04:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 21:50 UTC

   A subset of eth_sendRawTransaction requests on Robinhood Mainnet are showing degraded performance.

2. investigating 2026-10-12 21:51 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-12 22:10 UTC

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

4. monitoring 2026-10-12 22:12 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-10-12 22:13 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-10-12 22:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Abstract

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 11:07 UTC

   A subset of requests on Abstract Mainnet are experiencing elevated error rates.

2. resolved 2026-10-09 11:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Ronin

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 16:38 UTC

   We’re investigating issues affecting our Ronin Mainnet nodes following the hardfork.

2. resolved 2026-10-07 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Starknet

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 08:52 UTC

   Starknet Mainnet is currently not producing new blocks following a recent network-wide upgrade. This is a chain-level condition affecting the Starknet network as a whole and is not isolated to Alchemy infrastructure. We are actively coordinating with the Starknet team on...

2. resolved 2026-10-06 09:13 UTC

   Starknet Mainnet block production has resumed and Alchemy Starknet endpoints are serving current chain data as expected. Applications that cached stale state during the stall should recover on their next refresh. Thank you for your patience while the network recovered.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: US East

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-30 13:12 UTC

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

2. resolved 2026-09-30 13:30 UTC

   We observed chain stalls across our networks affecting requests in the USE region. This occurred between the 13:12:00 UTC to 13:30:15 UTC, and has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-22 17:15 UTC

   We are seeing increased error rates and higher latency in our US West region. We are currently investigating.

2. resolved 2026-09-22 18:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Unichain

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 10:27 UTC

   We’re currently investigating a finalized block stall on Unichain Mainnet that is impacting requests using the finalized tag in our USE region.

2. identified 2026-09-22 13:45 UTC

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

3. resolved 2026-09-23 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: ARC

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-21 17:35 UTC

   A subset of requests on Arc Testnet experienced increased latency starting ~17:35 UTC. This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Solana

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 08:43 UTC

   We are investigating elevated latency affecting getSignaturesForAddress requests on Solana Mainnet in the US East region.

2. monitoring 2026-09-11 09:02 UTC

   A routing change has been implemented, and we are observing latency returning to normal levels.

3. resolved 2026-09-11 10:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 22:14 UTC

   A subset of requests on Robinhood Mainnet are experiencing increased latency in the APAC region.

2. resolved 2026-09-09 01:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 16:22 UTC

   We are investigating elevated latency and block lag affecting a subset of requests. Our team is actively working to restore normal performance and will provide an update soon.

2. investigating 2026-09-04 16:23 UTC

   We are investigating elevated latency and block lag affecting a subset of requests due to upstream feed relay instabilities. Our team is actively working to restore normal performance and will provide an update soon.

3. monitoring 2026-09-04 16:54 UTC

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

4. resolved 2026-09-04 17:28 UTC

   The upstream feed relay instabilities have been resolved, and latency and block lag have returned to normal.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 12:50 UTC

   We are currently investigating this issue.

2. investigating 2026-09-04 12:56 UTC

   We are continuing to investigate this issue. Team noticed that this is driven by an upstream issue on Robinhood Mainnet - a sharp increase in on-chain activity and block size, combined with brief instability on Robinhood's sequencer feed. This caused some of our nodes to briefly...

3. resolved 2026-09-04 13:32 UTC

   Service is now fully recovered, nodes are caught up with the chain and error rates are back to baseline! Instability upstream on Robinhood chain was concluded as a root cause.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 15:41 UTC

   We're investigating elevated 403s affecting multiple teams across multiple regions. Team is actively working on resolution.

2. identified 2026-09-03 16:11 UTC

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

3. monitoring 2026-09-03 16:21 UTC

   We are no longer seeing elevated errors in local testing and are monitoring the situation closely.

4. monitoring 2026-09-03 16:21 UTC

   We are observing an increase in successful responses and are monitoring the situation closely.

5. resolved 2026-09-03 16:54 UTC

   The incident has been resolved. We are continuing to monitor the situation.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 02:58 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-03 03:20 UTC

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

3. resolved 2026-09-03 03:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 14:39 UTC

   We’re investigating elevated error rates and latency affecting some API requests across multiple regions. Our team is actively working to restore normal performance.

2. identified 2026-08-31 14:57 UTC

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

3. identified 2026-08-31 15:00 UTC

   Robinhood Mainnet is seeing recovery. We're continuing to monitor.

4. identified 2026-08-31 15:00 UTC

   Arbitrum Mainnet is seeing recovery. We're continuing to monitor.

5. identified 2026-08-31 15:03 UTC

   All networks are seeing recovery. We're continuing to monitor. You might still see elevated latencies on Arbitrum, BSC and Robinhood. We expect them to come back to baseline shortly.

6. identified 2026-08-31 15:18 UTC

   Arbitrum, BSC and Robinhood continue to exhibit slightly higher latencies than baseline. All other networks are back to baseline.

7. resolved 2026-08-31 15:34 UTC

   All networks latencies are back to baseline.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Cronos

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-31 12:15 UTC

   Network wide incident is affecting Cronos Mainnet and block production has been halted: https://x.com/CronosNetwork/status/2094072333434769703

2. resolved 2026-08-31 13:38 UTC

   Incident is resolved and blocks are being produced again - confirmed by Cronost team: https://x.com/CronosNetwork/status/2094417832394301499

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Ethereum

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-29 18:13 UTC

   A subset of requests on Ethereum Mainnet are experiencing elevated latency.

2. identified 2026-08-29 18:20 UTC

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

3. resolved 2026-08-29 19:45 UTC

   The elevated latencies affecting Ethereum Mainnet Data APIs have been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-27 20:05 UTC

   A subset of Data API requests on Robinhood Mainnet are experiencing increased latency and error rates.

2. resolved 2026-08-27 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: X-Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 16:18 UTC

   WebSocket connections to X Layer Mainnet in our US East region are being established normally, but subscription events may be delayed or missing. HTTP requests are not affected.

2. monitoring 2026-08-27 18:38 UTC

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

3. resolved 2026-08-27 23:40 UTC

   This incident has been resolved! WebSocket subscription delivery for X Layer Mainnet in our US East region has returned to normal. HTTP requests were not affected at any point during this incident

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 21:58 UTC

   We are currently investigating reports of elevated latency affecting Token API balance lookups and related endpoints across multiple networks. We will provide an update as more information becomes available!

2. resolved 2026-08-26 22:12 UTC

   This incident has been resolved. Between approximately 21:58 UTC and 22:12 UTC, some API requests across multiple networks experienced elevated latency, primarily affecting Token API and Portfolio API balance lookups. All services are currently operating normally. We will...

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 12:30 UTC

   We're observing a network wide chain stalled on Xdc Testnet - stopped at block: 85974607 See Xdc Testnet block explorer here: https://testnet.xdcscan.com/block/85974607

2. resolved 2026-08-26 21:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Zetachain

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 13:31 UTC

   We're observing a network wide chain stalled on Zetachain mainnet - stopped at block: 18349554 See Zetachain block explorer here: https://zetascan.com/block/18349554

2. resolved 2026-08-25 18:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Unichain

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 12:23 UTC

   We are investigating reports of delayed safe and finalized block tag data on Unichain Mainnet for requests routed through our US East (use1) region. The latest block head and overall API serving are healthy and unaffected. Applications relying on safe/finalized tags (e.g. via...

2. resolved 2026-08-24 18:37 UTC

   A subset of nodes serving Unichain Mainnet in our US East (use1) region experienced stalled safe/finalized block tracking, causing delayed safe/finalized block data for requests routed through that region. The latest block head and overall API serving were unaffected throughout...

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: BNB Smart Chain

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-23 14:20 UTC

   A subset of eth_getLogs and debug_traceTransaction requests on BNB Smart Chain Mainnet are experiencing high latencies. We are actively investigating these issues and pursuing mitigation.

2. resolved 2026-08-25 14:25 UTC

   Resolved - Elevated latency on BNB Smart Chain Mainnet JSON-RPC requests has been fully mitigated. All methods are performing within normal latency ranges!

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-22 21:33 UTC

   We are investigating elevated latency affecting Robinhood Mainnet requests. Our team is working to restore normal performance.

2. investigating 2026-08-22 22:05 UTC

   Our team is continuing to investigate elevated latency affecting Robinhood Mainnet requests.

3. resolved 2026-08-22 22:43 UTC

   Latency has returned to normal for Robinhood Mainnet. We will continue to monitor the service.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Polygon

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-20 00:36 UTC

   A subset of eth_getLogs requests on Polygon Mainnet are seeing elevated latencies. We are actively investigating.

2. resolved 2026-08-20 01:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: BNB Smart Chain

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-19 17:42 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-19 19:01 UTC

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

3. resolved 2026-08-20 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Solana

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 06:00 UTC

   We are investigating an issue causing Solana Streaming (WebSocket and gRPC) to be unavailable in Tokyo, Frankfurt, New York, and Salt Lake City. We will provide an update as more information becomes available.

2. monitoring 2026-08-19 06:21 UTC

   The immediate issue has been mitigated, and we’re working on the final fix.

3. resolved 2026-08-19 06:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Polygon

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-17 14:18 UTC

   Some transactions submitted on Polygon Mainnet were taking longer than expected to propagate and land onchain. A fix has been applied and we are monitoring the results.

2. resolved 2026-08-17 14:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Polygon

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-13 14:52 UTC

   Following today's Polygon network hard fork, some trace methods on Polygon Mainnet are currently failing. This is a network-wide issue affecting all providers, as the Polygon team has not yet released a client binary with trace API support for the new fork. We expect the Polygon...

2. resolved 2026-08-13 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Injective

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 11:36 UTC

   We are investigating elevated latency affecting requests to Injective Mainnet in the US East region. Error rates remain within normal levels. We will provide an update as more information becomes available.

2. resolved 2026-08-14 18:00 UTC

   This incident has been resolved. Injective Mainnet performance has returned to normal.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: AP SE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-12 04:45 UTC

   We have identified a network connectivity issue with an upstream infrastructure provider affecting our Asia Pacific region. Dedicated node deployments in this region may be unreachable. We are working with the provider to restore connectivity and will post updates here.

2. monitoring 2026-08-12 04:51 UTC

   Connectivity to our apne1 region has been restored. All nodes are back in sync. API error rates have returned to normal and dedicated node deployments in the region are recovering.

3. resolved 2026-08-12 08:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Solana

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 04:38 UTC

   We are investigating global network instability affecting Solana Mainnet. Some requests may experience elevated errors or degraded performance. We will provide an update as more information becomes available.

2. identified 2026-08-12 04:39 UTC

   We have isolated the impact to the Asia Pacific region, affecting Singapore and Tokyo. Other regions are operating normally. We are continuing to investigate and will provide an update as more information becomes available.

3. resolved 2026-08-12 04:44 UTC

   The issue has been resolved. Solana Mainnet service has recovered in Singapore and Tokyo, and we are monitoring the situation closely.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-12 01:19 UTC

   We’re currently investigating an issue causing elevated latency and increased 5xx errors on Robinhood Mainnet. We’ll share additional updates as soon as we have more information.

2. identified 2026-08-12 02:00 UTC

   The issue has been identified and we're working on a fix.

3. resolved 2026-08-12 02:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Story

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-10 12:29 UTC

   We are investigating a network-wide stall on Story Mainnet. Block production has halted at block 20818220 and requests for the latest block may return stale data until the chain resumes. We are coordinating with the Story team and working to resolve this ASAP.

2. resolved 2026-08-10 17:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Base

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 06:09 UTC

   We are investigating a network-wide stall on Base Sepolia.

2. resolved 2026-08-06 06:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Ethereum, Arbitrum, Base, Polygon, Robinhood, World Chain

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-05 17:45 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.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: HyperEVM

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 15:08 UTC

   A subset of requests on Hyperliquid Mainnet routed through our Asia Pacific region are seeing increased delays and elevated error rates.

2. investigating 2026-07-31 15:23 UTC

   We are continuing to investigate this issue.

3. resolved 2026-07-31 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Monad

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 13:19 UTC

   A subset of eth_getLogs requests on Monad Mainnet routed through our EU Central region are seeing increased delays.

2. resolved 2026-07-31 14:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Sui

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-31 01:07 UTC

   We are investigating degraded performance affecting requests on Sui Mainnet.

2. investigating 2026-07-31 01:09 UTC

   We are continuing to investigate this issue.

3. resolved 2026-07-31 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: HyperEVM

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 16:04 UTC

   A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet are seeing increased delays for requests routed through our EU Central region.

2. resolved 2026-07-30 17:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Robinhood

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-30 21:30 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.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: HyperEVM

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-28 14:06 UTC

   Some requests to Hyperliquid Mainnet routed through our US East region may be experiencing elevated latency. We are investigating.

2. resolved 2026-07-29 08:00 UTC

   This incident has been resolved.

3. postmortem 2026-07-29 12:24 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....

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Base

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-28 13:26 UTC

   We are investigating a network-wide stall affecting safe and finalized blocks on Base Mainnet.

2. identified 2026-07-28 13:32 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...

3. resolved 2026-07-28 15:33 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

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Stable

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 03:39 UTC

   A subset of requests on Stable Mainnet are experiencing degraded

2. identified 2026-07-27 06:32 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.

3. resolved 2026-07-27 06:51 UTC

   Nodes have recovered and services are healthy again.

Excerpts are shortened. Read the full incident on Alchemy's status page.

Affected: Cronos

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 09:36 UTC

   A subset of requests on Cronos Mainnet are experiencing availability issues.

2. investigating 2026-07-24 09:36 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-24 12:48 UTC

   A part of our Cronos nodes were down due to a binary issue.

4. resolved 2026-07-24 12:49 UTC

   Nodes have been rescyned with stable binary and services are back to healthy.

Excerpts are shortened. Read the full incident on Alchemy's status page.