Looking for an update now? Check the current status, or follow Alchemy for future changes.
60%of 55 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
64.3%
28
10
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
August 2026
X Layer Mainnet - Delayed WebSocket Event Delivery in US East
A fix has been implemented, and we are monitoring the results.
investigating
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.
[Network Wide] Zetachain Mainnet Block Production Stalled
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
Legacy Incident Archive
139 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Unichain Mainnet - safe/finalized head stalled in use1
minorSource not attested
Last archived state: resolved
View archived record details
Unichain
investigating
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 eth_getBlockByNumber, eth_getLogs, eth_call) in this region may receive outdated block data. We are actively investigating and will provide updates as we have them!
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.
Elevated Latency for Robinhood Mainnet
minorSource not attested
Last archived state: resolved
View archived record details
Robinhood
investigating
Our team is continuing to investigate elevated latency affecting Robinhood Mainnet requests.
investigating
We are investigating elevated latency affecting Robinhood Mainnet requests. Our team is working to restore normal performance.
Polygon Mainnet - Elevated eth_getLogs Latency
minorSource not attested
Last archived state: resolved
View archived record details
Polygon
investigating
A subset of eth_getLogs requests on Polygon Mainnet are seeing elevated latencies. We are actively investigating.
Elevated latency on BNB Smart Chain
minorSource not attested
Last archived state: resolved
View archived record details
BNB Smart Chain
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
Solana Streaming (WebSocket & gRPC) Unavailable in Multiple Regions
majorSource not attested
Last archived state: resolved
View archived record details
Solana
monitoring
The immediate issue has been mitigated, and we’re working on the final fix.
investigating
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.
Polygon Mainnet - Delays propagating transactions
minorSource not attested
Last archived state: resolved
View archived record details
Polygon
monitoring
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.
Polygon Mainnet: Trace API methods unavailable
minorSource not attested
Last archived state: resolved
View archived record details
Polygon
investigating
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 team to ship an updated binary restoring trace support, and we will roll it out as soon as it is available. We'll post updates here as we learn more.
Elevated Latency on Injective Mainnet
minorSource not attested
Last archived state: resolved
View archived record details
Injective
investigating
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.
Shape Mainnet - Increased Latency
minorSource not attested
Last archived state: resolved
View archived record details
investigating
A subset of requests on Shape Mainnet are experiencing increased latency.
