All Systems Operational

About This Site

Welcome to the Quicknode status page. We use this page to communicate any issues with our products including planned and unplanned outages.

Uptime over the past 90 days. View historical uptime.
0g Operational
0g - Galileo Testnet Operational
0g - Mainnet Operational
Abstract Operational
Abstract - Mainnet Operational
Abstract - Testnet Operational
Aleo Operational
Aleo - Mainnet Operational
Aleo - Testnet Operational
Aptos Operational
Aptos - Mainnet Operational
Aptos - Testnet Operational
Arbitrum Operational
Arbitrum - Mainnet Nitro Operational
Arbitrum - Mainnet Classic Operational
Arbitrum - Sepolia Operational
Arbitrum Nova Operational
Arbitrum Nova - Mainnet Operational
Arc Operational
Arc - Testnet Operational
Arc - Mainnet Operational
Ault Operational
Ault - Testnet Operational
Ault - Mainnet Operational
Avalanche Operational
Avalanche - Mainnet Operational
Avalanche - Fuji Testnet Operational
B3 Operational
B3 - Mainnet Operational
B3 - Sepolia Operational
Base Operational
Base - Mainnet Operational
Base - Sepolia Operational
Berachain Operational
Berachain - Mainnet Operational
Berachain - Bepolia Operational
Bitcoin Operational
Bitcoin - Mainnet Operational
Bitcoin - Testnet Operational
Bitcoin Cash Operational
Bitcoin Cash - Mainnet Operational
Bitcoin Cash - Testnet Operational
Blast Operational
Blast - Mainnet Operational
Blast - Sepolia Operational
BNB Smart Chain (BSC) Operational
BNB - Mainnet Operational
BNB - Testnet Operational
Celestia Operational
Celestia - Mainnet Operational
Celestia - Mocha Testnet Operational
Celo Operational
Celo - Mainnet Operational
Cosmos Operational
Cosmos - Mainnet Operational
Cyber Operational
Cyber - Mainnet Operational
Cyber - Sepolia Operational
DOGE Operational
DOGE - Mainnet Operational
Ethereum Operational
Ethereum - Mainnet Operational
Ethereum - Sepolia Operational
Ethereum - Hoodi Operational
Flare Operational
Flare - Coston2 Testnet Operational
Flare - Mainnet Operational
Flow Operational
Flow - Mainnet Operational
Flow - Testnet Operational
Fluent Operational
Fluent - Testnet Operational
Fluent - Mainnet Operational
Fraxtal (Select Access) Operational
Fraxtal - Mainnet Operational
Fuel Operational
Fuel - Mainnet Operational
Fuel - Sepolia Operational
Gnosis Operational
Gnosis - Mainnet Operational
Gravity Operational
Gravity - Alpham Operational
Gravity - Mainnet Operational
Hedera Operational
Hedera - Mainnet Operational
Hedera - Testnet Operational
Hemi Operational
Hemi - Mainnet Operational
Hemi - Testnet Operational
HyperLiquid Operational
HyperEVM - Mainnet Operational
HyperEVM - Testnet Operational
Hypercore - Mainnet Operational
Injective Operational
Injective - Mainnet Operational
Injective - Testnet Operational
Ink Operational
Ink - Mainnet Operational
Ink - Sepolia Operational
JOC Operational
JOC - Mainnet Operational
Kaia Operational
Kaia - Mainnet Operational
Kaia - Testnet Operational
Katana Operational
Katana - Mainnet Operational
Lens Operational
Lens - Mainnet Operational
Lens - Testnet Operational
Linea Operational
Linea - Mainnet Operational
Lisk (Select Access) Operational
Lisk - Mainnet Operational
Litecoin Operational
Litecoin - Mainnet Operational
Litecoin - Testnet Operational
Mantle Operational
Mantle - Mainnet Operational
Mantle - Sepolia Operational
MegaETH Operational
MegaETH - Mainnet Operational
Moca Operational
Moca - Testnet Operational
Mode (Select Access) Operational
Mode - Mainnet Operational
Monad Operational
Monad - Testnet Operational
Monad - Mainnet Operational
Morph Operational
Morph - Mainnet Operational
Morph - Hoodi Testnet Operational
NEAR Operational
NEAR - Mainnet Operational
NEAR - Testnet Operational
Optimism Operational
Optimism - Mainnet Operational
Optimism - Sepolia Operational
Osmosis (Select Access) Operational
Osmosis - Mainnet Operational
Osmosis - Mainnet Operational
Peaq Operational
Peaq - Mainnet Operational
Plasma Operational
Plasma - Mainnet Operational
Plasma - Testnet Operational
Polkadot Operational
Polkadot - Mainnet Operational
Polygon Operational
Polygon - Mainnet Operational
Polygon - Amoy Testnet Operational
RobinHood Operational
Robinhood - Testnet Operational
Robinhood - Mainnet Operational
Scroll Operational
Scroll - Mainnet Operational
SEI Operational
Sei - Pacific-1 Mainnet Operational
Sei - Atlantic-2 Testnet Operational
Solana Operational
Solana - Mainnet Operational
Solana - Devnet Operational
Solana - Testnet Operational
Soneium Operational
Soneium - Mainnet Operational
Sonic Operational
Sonic - Mainnet Operational
Stacks Operational
Stacks - Mainnet Operational
Stacks - Testnet Operational
Starknet Operational
Starknet - Mainnet Operational
Starknet - Sepolia Operational
Stellar Operational
Stellar - Mainnet Operational
Stellar - Testnet Operational
Sui Operational
Sui - Mainnet Operational
Sui - Testnet Operational
Tempo Operational
Tempo - Testnet Operational
Tempo - Mainnet Operational
TON Operational
TON - Mainnet Operational
Tron Operational
Tron - Mainnet Operational
Tron - Nile Testnet Operational
Unichain Operational
Unichain - Mainnet Operational
Unichain - Sepolia Testnet Operational
Vana Operational
Vana - Mainnet Operational
Vana - Moksha Testnet Operational
World Chain Operational
World Chain - Mainnet Operational
World Chain - Sepolia Operational
X Layer Operational
X Layer - Mainnet Operational
X Layer - Testnet Operational
XRP Ledger Operational
XRP Ledger - Mainnet Operational
XRP Ledger - Testnet Operational
XRPL EVM Operational
XRPL EVM - Mainnet Operational
XRPL EVM - Testnet Operational
Zcash Operational
Zcash - Mainnet Operational
Zcash - Testnet Operational
ZkSync Operational
ZKsync - Mainnet Operational
ZKsync - Testnet Operational
Zora (Select Access) Operational
Zora - Mainnet Operational
Quicknode Products Operational
Quicknode Faucet Operational
Multi-region Transaction Broadcast Operational
Single Flight RPC Operational
Quicknode NFT API Operational
Quicknode Token API Operational
IPFS Rest API Operational
Quicknode Solana DAS API Operational
Jupiter Swap API Operational
Quicknode Streams Operational
JITO Bundles & Transactions Operational
RPC Logs Operational
Quicknode Webhooks Operational
SQL API Operational
QuickNode Dashboard Operational
QuickNode Website Operational
Customer Support Operational
GIWA Operational
GIWA - Sepolia Operational
Elysium Operational
Elysium Mainnet Operational
Elysium Testnet Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[Standard] Stacks - Mainnet & Testnet - Upgrade API to v9.9.0 Nov 11, 2026 00:00-23:59 UTC

We are upgrading our Stacks Mainnet infrastructure to stacks-blockchain-api v9.8.0 on 2026-11-11. This feature release adds transaction type filtering and fee-based sorting to transaction endpoints, and resolves performance issues causing timeouts on supply endpoints. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- GET /extended/v3/transactions — New type filter parameter allows filtering transactions by type.
- GET /extended/v3/mempool/transactions — New type filter parameter allows filtering mempool transactions by type; new sort_by=fee option enables sorting by transaction fee.
- GET /extended/v1/stx_supply — Performance improvements resolve timeout issues on this endpoint.

https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.8.0
Posted on Nov 03, 2026 - 19:07 UTC

Urgent Sui - Testnet - Upgrade to testnet-v1.84.0 Nov 11, 2026 00:00-23:59 UTC

We are upgrading our Sui Testnet infrastructure to testnet-v1.84.0 on 2026-11-11. This release advances the protocol to version 142, introducing transaction effects-size accounting improvements, stricter cryptographic verification, new Clock and derived object APIs, and extensive breaking changes to gRPC and GraphQL cursor formats and filtering semantics. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- ListTransactions / ListEvents / ListCheckpoints — Requests with cursors past the requested checkpoint range now close with CheckpointBound instead of CursorBound; their closing cursor resumes where the request's cursor does.
- Checkpoint subscriptions — Checkpoints on full nodes with embedded rpc-store now deliver approximately 180 ms sooner on average.
- Signature verification (gRPC) — Now accepts both supported zkLogin circuits independently of network activation rules.
- VerifySignatureRequest — Accepts optional `check_address_aliases` parameter to verify against the address's current address aliases; response includes `address_aliases_checked` field when applied.
- ListTransactions / ListEvents — Now accept `start_transaction_index`, `end_transaction_index`, `start_event_index`, and `end_event_index` to start and end queries at positions inside first and last checkpoints.
- ListCheckpoints / ListTransactions / ListEvents / SubscribeTransactions / SubscribeEvents — All frames now carry `Watermark.cursor_position`, the frame's resume point as a public ledger position; use this to order frames and drop duplicates instead of comparing cursor bytes. kv-rpc List* requests with invalid filters fail with INVALID_ARGUMENT even when nothing is left to scan. On a fullnode, a descending request whose start_checkpoint is below the pruning floor fails with BELOW_EARLIEST_AVAILABLE even when its before cursor is past the tip.
- AffectedAddress transaction filters — Now also match transactions sent by the address, including sponsored transactions that touch only shared objects. Filters whose AffectedAddress literals would expand to more than 64 terms are rejected with INVALID_ARGUMENT. Sender(X) AND NOT AffectedAddress(X) now matches nothing.
- ListTransactions / ListEvents — Reject cursors minted by servers older than 1.83 and cursors in the original format with INVALID_ARGUMENT; restart scans from a ledger position instead.
- /health endpoint — Accepts optional `max_history_lag` query parameter; when set, a full node reports unhealthy while its ledger-history indexes lag live-object indexes beyond that checkpoint count, or if it has no RPC indexes.
- gRPC verifySignature — Accepts both supported zkLogin circuits and ML- multisig members independently of network activation rules.

https://github.com/MystenLabs/sui/releases/tag/testnet-v1.84.0
Posted on Nov 10, 2026 - 19:31 UTC

[Critical] Injective Mainnet - Upgrade to v1.20.4-safeharbor.5 Nov 11, 2026 12:00-14:00 UTC

Injective Mainnet is undergoing a network upgrade to v1.20.4-safeharbor.5 on 2026-11-11. This is a coordinated network halt and upgrade as part of Injective's Institutional Readiness Program, introducing targeted improvements to network infrastructure, validator coordination, and operational efficiency.
If the proposal passes, Mainnet will halt at block 191,270,000, estimated for November 11, 2026 at 12:30 UTC / 07:30 EST
Posted on Nov 10, 2026 - 15:01 UTC

[Standard] Hedera Mainnet - Upgrade JSON-RPC Relay to v0.81.0 Nov 16, 2026 00:00-23:59 UTC

[Standard] Hedera - Mainnet - Upgrade to Mirror Node v0.166.1 and JSON-RPC Relay v0.81.0

We are upgrading our Hedera Mainnet infrastructure to Mirror Node v0.166.1 and JSON-RPC Relay v0.81.0 on 2026-11-16. These releases introduce WebSocket subscriptions for pending transactions, more accurate gas estimation, clearer error handling for transaction receipts and submissions, faster and more precise transaction tracing, and enhanced REST and Web3 API responses. Some error responses and trace outputs change format, so please review the RPC changes below. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- newPendingTransactions: New WebSocket subscription method for monitoring pending transactions in real time.
- eth_getTransactionReceipt: Transactions rejected before consensus now return a JSON-RPC error (-32003) instead of null. Clients that check for a null receipt should handle this error code.
- eth_getTransactionCount: A race condition fix ensures the correct nonce is returned when called immediately after eth_sendRawTransaction or under concurrent requests.
- eth_sendRawTransaction: Aborted transaction submissions now return HTTP 499 instead of HTTP 500.
- debug_traceTransaction: The prestateTracer now returns only the storage slots a transaction actually touched instead of the full contract state, improving performance and accuracy.
- Historical gas prices: Gas prices now resolve correctly for blocks older than the first EVM fee schedule.
- /api/v1/contracts/call: Gas estimation accuracy has improved from roughly 2.5% variance to less than 1% variance compared to consensus nodes.
- Contract result REST APIs: A new child field on all contract result endpoints indicates whether the underlying transaction has a parent transaction.

https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.166.1
https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.166.0
https://github.com/hiero-ledger/hiero-json-rpc-relay/releases/tag/v0.81.0
Posted on Nov 06, 2026 - 15:42 UTC

[Standard] Cosmos Mainnet - Upgrade to Gaia v29.1.0 Nov 16, 2026 05:00-07:00 UTC

Cosmos is undergoing a network upgrade to Gaia v29.1.0 on 2026-11-16 @ ~6:00 UTC. This is a state-breaking release that restores decoding of historical ParameterChangeProposal content, fixing governance proposal list, status-filtered, single-proposal and tally queries and state export.

Brief interruptions to RPC availability may occur on that date.

https://github.com/cosmos/gaia/releases/tag/v29.1.0
Posted on Nov 10, 2026 - 16:43 UTC

[Standard] Aleo - Testnet - Upgrade to testnet-v4.13.0 Nov 17, 2026 00:00-23:59 UTC

We are upgrading our Aleo Testnet infrastructure to snarkOS testnet-v4.13.0 on 2026-11-17. This is a non-consensus-breaking release built against snarkVM v4.13.0-rc.1, introducing validator upgrade safety checks, improved block sync efficiency, REST API v2 migration, and enhanced metrics granularity. There is no activation height; validators and nodes on v4.12.x and v4.13.0 remain interoperable and may upgrade at their convenience. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- REST API v1 — The v1 REST API and unversioned routes are now deprecated. They continue to work but responses carry Deprecation and Link headers directing users to /v2. See node/rest/MIGRATING_TO_V2.md for migration guidance.
- REST API responses — Responses are now compact JSON (not pretty-printed) and are gzip-compressed when the client sends Accept-Encoding: gzip.
- Endpoint versioning (snarkos developer) — The snarkos developer CLI commands now use /v2. An --endpoint without a version gets /v2/ appended automatically; endpoints with query strings are rejected.

https://github.com/aleo-labs-protocol/snarkOS/releases/tag/testnet-v4.13.0
Posted on Nov 10, 2026 - 18:15 UTC

[Urgent] Injective - Mainnet - Upgrade to v1.21.0 Nov 17, 2026 13:00-17:00 UTC

Injective Mainnet is undergoing a network upgrade to v1.21.0 on Tuesday, November 17, 2026, during the 14:00-17:00 UTC window. This is a planned network upgrade coordinated with on-chain governance. Brief interruptions to RPC availability may occur on that date.
Posted on Nov 06, 2026 - 23:17 UTC

Nov 10, 2026

Urgent Sei - Atlantic (Testnet) - Upgrade to v6.8
Completed - The scheduled maintenance has been completed.
Nov 10, 17:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 10, 15:30 UTC
Scheduled - Sei Atlantic (testnet) will be undergoing a netowrk upgrade to v6.8 on 2026-11-10 ~16 UTC. This release removes the Cosmos gRPC and gRPC-Web servers, Rosetta, and the tokenfactory module; state proofs are now off by default. Per-IP RPC rate limiting is enabled by default on EVM JSON-RPC and CometBFT RPC endpoints. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- batch_request_limit — EVM JSON-RPC batch_request_limit default has been reduced from 1000 to 100; requests exceeding this limit will be rejected.
- Cosmos gRPC and gRPC-Web — These servers have been removed from seid and are no longer available.
- Rosetta API — The Rosetta API has been removed and is no longer available.
- per-IP rate limiting — EVM JSON-RPC and CometBFT RPC now enforce per-IP rate limiting by default; users behind reverse proxies or load balancers may experience rate-limit errors if proxy IP configuration is not set.
Nov 9, 14:32 UTC
Base Mainnet and Sepolia upgrade to version base v1.5.4
Completed - The scheduled maintenance has been completed.
Nov 10, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 10, 14:00 UTC
Scheduled - Release notes: https://github.com/base/base/releases/tag/v1.5.4
Nov 10, 13:37 UTC
Injective Mainnet – Scheduled Network Upgrade Test
Resolved - This incident has been resolved.
Nov 10, 02:53 UTC
Investigating - Injective is conducting a scheduled mainnet upgrade test in coordination with its validators, as part of preparations for an upcoming network upgrade. During this window, block production on Injective mainnet may be paused or delayed, and requests to Injective endpoints may return stale data or errors.

This is a chain-wide event and is not related to Quicknode infrastructure. We are in contact with the Injective team and will post an update once normal network operations resume.
Nov 9, 13:52 UTC
[Standard] Celestia Mocha - Upgrade to v10.6.0-mocha
Completed - The scheduled maintenance has been completed.
Nov 10, 00:00 UTC
Scheduled - We are upgrading our Celestia Mocha infrastructure to v10.6.0-mocha on 2026-11-09. This release bundles celestia-core v0.42.5 through v0.42.8 with fixes in consensus block propagation, peer identity validation, mempool handling, and the JSON-RPC server, along with improvements to data-availability proof verification, Fibre escrow validation, and IBC concurrency safety. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
tx_search — max_search_results now applies to the whole query, not only its first condition.
block_search — max_search_results now applies to the whole query, not only its first condition.

https://github.com/celestiaorg/celestia-app/releases/tag/v10.6.0-mocha
Nov 5, 14:13 UTC

Nov 9, 2026

[Standard] Ethereum TN&MN - Reth v2.9.0
Completed - The scheduled maintenance has been completed.
Nov 9, 23:59 UTC
Scheduled - We are upgrading our Ethereum Reth infrastructure from v2.5.2 to v2.9.0. This upgrade combines four releases of improvements. It includes a new EVM implementation (evm2) that makes block execution about 10% faster, faster historical-state and trace queries, and several RPC correctness fixes. No hard fork is involved, and users do not need to take any action. During the maintenance window, brief interruptions to RPC availability may occur.

RPC Changes:
- eth_getProof — fixed. Proof responses now match the Ethereum execution-apis specification.
- eth_call / eth_estimateGas — fixed. When the node works out how much gas a caller can afford, it now reserves blob fees from the account balance.
- eth_estimateGas — changed. Estimates are now capped at the node's RPC gas cap.
- eth_maxPriorityFeePerGas — changed. The fee oracle now ignores transactions with a tip below 2 wei, so the suggested priority fee no longer drops to 0. This matches Geth.
- trace_* (Parity-style) — changed. Output now matches other clients:
- Deleted accounts report empty stateDiff storage.
- vmTrace ops and subs include only operations that actually executed.
- Reverted CREATE calls return {gasUsed, output} without an address.
- trace_callMany / trace_filter — changed. trace_callMany without a block parameter and trace_filter without block bounds now default to latest. If you need pending state or a historical range, specify the block or range explicitly.
- trace_get — fixed. Results are now selected by trace tree path. Replaying a missing transaction returns null.

https://github.com/paradigmxyz/reth/releases/tag/v2.9.0
Intermediate releases (v2.6.0 – v2.8.1): https://github.com/paradigmxyz/reth/releases
Oct 29, 20:07 UTC
Elysium Mainnet – Elevated Errors on eth_sendRawTransaction
Resolved - This incident has been resolved.
Nov 9, 23:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 9, 23:40 UTC
Identified - The issue has been identified and a fix is being implemented.
Nov 9, 23:23 UTC
Investigating - We are investigating an issue affecting Elysium Mainnet where users are experiencing 429 and 403 errors on eth_sendRawTransaction requests. We will provide updates as we learn more.
Nov 9, 23:20 UTC
RPC Logs - Service Disruption
Resolved - The issue affecting RPC Logs has been resolved. Transaction and error logs are now operating normally. Please note that log data may show inaccuracies roughly between 15:10 UTC - 16:25 UTC. We apologize for any inconvenience caused.
Nov 9, 16:43 UTC
Investigating - We are investigating an issue affecting transaction and error log serving. Our engineers are actively working on a fix and will provide updates as more information becomes available.
Nov 9, 15:54 UTC
[Urgent] Injective - Testnet - Upgrade to v1.21.0-beta
Completed - The scheduled maintenance has been completed.
Nov 9, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 9, 15:00 UTC
Scheduled - Injective Testnet is undergoing a network upgrade to v1.21.0-beta on Monday, November 9, estimated around 15:30 UTC, at block height https://www.mintscan.io/injective-testnet/block/147786000. This is a planned network upgrade coordinated with on-chain governance. Brief interruptions to RPC availability may occur on that date.

https://github.com/InjectiveFoundation/injective-core/releases/tag/v1.21.0-beta-1793995527
Nov 6, 23:16 UTC
Elysium Mainnet – Transaction Submission Errors
Resolved - Transaction submission on Elysium mainnet is working normally again. The issue was caused by rate limiting at the upstream sequencer.
Nov 9, 15:46 UTC
Monitoring - A fix has been implemented and we are monitoring.
Nov 9, 15:05 UTC
Identified - Some customers may see 429 errors when sending transactions (eth_sendRawTransaction) on Elysium mainnet. These errors are coming from rate limiting at the upstream sequencer level. Read requests are not affected. We've identified the cause and the team is working on it as a top priority. We'll post an update as soon as it's resolved.
Nov 9, 14:59 UTC

Nov 8, 2026

Degraded Performance - HypeEVM Testnet
Resolved - This incident has been resolved.
Nov 8, 15:26 UTC
Monitoring - An upstream stall on Hyperliquid's HyperEVM testnet caused transaction submissions to fail from about 03:00 UTC. The upstream recovered at about 12:00 UTC, and transaction submission through Quicknode HyperEVM testnet endpoints has been operating normally since then. We are monitoring to make sure it stays stable.
Nov 8, 14:36 UTC
Investigating - The Quicknode team is investigating the degraded performance of HypeEVM testnet nodes. Customers may experience a high TX drop rate. We will provide an update as more information becomes available.
Nov 8, 05:42 UTC

Nov 7, 2026

Elevated Response Times and Timeouts - FRA Region
Resolved - This incident has been resolved.
Nov 7, 23:36 UTC
Update - We are continuing to monitor for any further issues.
Nov 7, 22:40 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 7, 22:37 UTC
Investigating - We are investigating elevated response times and timeouts affecting endpoints in the FRA region. Our team is actively investigating and will provide updates as more information becomes available.
Nov 7, 20:31 UTC

Nov 6, 2026

Solana Mainnet: Agave 4.4.0 and Yellowstone gRPC v17
Completed - The scheduled maintenance has been completed.
Nov 6, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 2, 00:00 UTC
Scheduled - As part of our preparation for Agave 4.4 on Solana Mainnet, we are upgrading our Solana Mainnet endpoints to the latest releases: Agave 4.4.0, Yellowstone gRPC v17, and our matching RPC and WebSocket serving layers. Nodes restart one at a time, so requests continue to be served throughout. Devnet is the place to test your integration against these changes before they reach Mainnet.

**Expected changes**

JSON-RPC

- getTransaction accepts an optional minContextSlot. If the node has not yet reached that slot, it returns error -32016 (minimum context slot not reached) instead of null.

- getSignatureStatuses accepts optional commitment and minContextSlot. The default commitment is still processed. When you set one, statuses below it are not returned, and minContextSlot behaves as in getTransaction.

- getLeaderSchedule:
accepts an optional keyByVoteAccount to key the result by vote account instead of identity; returns error -32022 when you ask for an identity that is not in the schedule. It used to return an empty result {}. If your code treats {} as “not a leader this epoch”, handle this error instead.

- getInflationGovernor now returns the cluster’s current inflation parameters instead of fixed default values.

- getBlocks over wide ranges is faster. Results are unchanged.

- Error messages for invalid base64 input keep the invalid base64 encoding: prefix, but the text after it may differ. Match on the prefix or the error code, not the full message.


WebSocket

- accountSubscribe and programSubscribe now apply dataSlice for binary encodings (base58, base64, base64+zstd). Notifications contain only the requested slice; a zero-length slice returns empty data. Before, dataSlice was ignored and the full account data was sent. If you send dataSlice but need full data, remove it.

Yellowstone gRPC

- The protobuf schema is unchanged, so existing clients need no update.
- Subscribing with from_slot now replays without gaps or duplicates when the stream joins live data.
from_slot is honored only on the first request of a stream; a later request’s from_slot is ignored.
- On confirmed and finalized subscriptions, the CreatedBank slot event now arrives together with its block’s data, so its position in the stream can differ from before.
- Alpenglow block-footer certificates are passed through exactly as the validator produces them, so none are dropped.
Oct 30, 22:59 UTC

Nov 5, 2026

Urgent Sui - mainnet - Upgrade to mainnet-v1.83.1
Completed - The scheduled maintenance has been completed.
Nov 5, 23:59 UTC
Scheduled - We are upgrading our Sui mainnet infrastructure to mainnet-v1.83.1 on 2026-11-05. This release advances the protocol to version 141, introducing refined transaction effects size estimation, a 1024 accumulator event limit per transaction, new bulk vector operations (replace_range, keep_range, copy_range, remove_range, truncate), and significant gRPC and GraphQL improvements. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- SubscribeTransactions — Now fills effects object types, clever errors, and event json when the read mask requests them, matching GetTransaction behavior.
- SubscribeCheckpoints — Now fills effects object types, clever errors, and event json when the read mask requests them, matching GetTransaction behavior.
- ListTransactions — Returns OUT_OF_RANGE instead of INTERNAL for requests below the node's retention. Cursors can now be sent back in either ordering without skipping items. Returns OUT_OF_RANGE for a descending request whose end_checkpoint is above the latest indexed checkpoint + 1, or whose start_checkpoint is above the latest indexed checkpoint with no end_checkpoint. On a pruning fullnode, every request needing data below the pruning floor returns OUT_OF_RANGE. Faster performance with improved scan logic (progress frames sent after every 256 buckets of scan work).
- ListEvents — Returns OUT_OF_RANGE instead of INTERNAL for requests below the node's retention. Cursors can now be sent back in either ordering without skipping items. Returns OUT_OF_RANGE when applicable. Faster performance with improved scan logic.
- ListCheckpoints — Returns OUT_OF_RANGE for a starting cursor past the server's indexed tip instead of an empty page. Cursors at or below filter.afterCheckpoint or at or above filter.beforeCheckpoint now return checkpoints within the bound instead of an empty page. Faster performance with improved scan logic.
- GetEpoch — Now lists mldsa65_auth among protocol feature flags.
- GraphQL multi-get operations — Nullable, fallible multi-gets now return successful entries alongside indexed errors for failed keys instead of failing the entire batch. No schema changes required.
- GraphQL NameRecord — contents.json decoding fixed; contents.bcs now returns only the NameRecord value, matching contents.type.
- GraphQL object and package resolution — Objects and packages resolved inside subscription, executeTransaction, and simulateTransaction results no longer resolve to unrelated objects. Live subscription events now report the correct transactionModule.package.address.
- GraphQL subscriptions — Subscriptions resumed with after or afterCheckpoint no longer skip a checkpoint at the backfill-to-live handoff. A backfill waiting on a stopped ledger disconnects with a reconnect error after 3 minutes.
- GraphQL checkpoints subscription — With an after cursor at or below filter.afterCheckpoint or before cursor at or above filter.beforeCheckpoint, now returns checkpoints within the bound instead of an empty page.
- GraphQL transaction and event connections — No longer report hasNextPage: true (or hasPreviousPage: true) when a page exactly fits remaining data. Pages derive hasNextPage/hasPreviousPage from the end reason. A page resuming at its window's edge reports no further page where it reported one before.
- GraphQL filtered transactions and events subscriptions — Take a new progress: Boolean = false argument. When enabled, the subscription interleaves progress payloads (node: null, carrying only a cursor) to let clients advance resume points without a match. Subscription fields now return TransactionSubscriptionEdge / EventSubscriptionEdge (nullable node) rather than paginated TransactionEdge / EventEdge; existing { cursor node {... } } selections remain valid. Clients leaving progress off see no behavior change.
- GraphQL protocolConfigs.featureFlags and featureFlag — Now report the mldsa65_auth flag.

https://github.com/MystenLabs/sui/releases/tag/mainnet-v1.83.1
Nov 4, 21:27 UTC

Nov 4, 2026

Polygon Amoy Testnet - Degraded Performance During Network Stress Test
Resolved - This incident has been resolved.
Nov 4, 21:09 UTC
Investigating - A network stress test is scheduled by the foundation at 19:00 UTC. Customers may experience degraded performance and elevated API errors on Polygon Amoy Testnet during this time. We will update this page as we acquire new information.
Nov 4, 18:53 UTC

Nov 3, 2026

Degraded Performance - Aptos Testnet
Resolved - This incident has been resolved.
Nov 3, 05:07 UTC
Investigating - The Quicknode team is investigating the degraded performance of Aptos Testnet nodes.
Customers may experience higher error rates, including 503 responses and failed or timed-out requests.
We will provide an update as more information becomes available.
Nov 3, 04:47 UTC

Nov 2, 2026

[Urgent] Stacks Mainnet - Upgrade to v9.7.0
Completed - The scheduled maintenance has been completed.
Nov 2, 23:59 UTC
Scheduled - We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date.

RPC Changes:
- GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference.
- GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost.
- GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts.
- GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts.
- GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block.
- event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search).
- /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available.

https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0
Oct 26, 15:45 UTC
[Standard] Morph - Hoodi Mainnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)
Completed - The scheduled maintenance has been completed.
Nov 2, 23:59 UTC
Scheduled - We are upgrading our Morph Mainnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC.

Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported.

During the maintenance window, brief interruptions to RPC availability may occur.

RPC changes:
- eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected.
- Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used.
- eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions.
- MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702).
- Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding.

https://github.com/morph-l2/morph/releases/tag/v0.6.4
https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7
Oct 21, 15:32 UTC
Stacks Mainnet Stuck at Block 9,395,980
Resolved - This incident has been resolved.
Nov 2, 19:10 UTC
Update - We have identified the root cause and are actively working on remediation across affected regions. Service restoration is underway and block height is progressing. We will continue to monitor and provide updates as the situation develops.
Nov 2, 18:53 UTC
Monitoring - Stacks Mainnet blocks are catching up. We are monitoring the network to confirm full recovery and stability.
Nov 2, 18:04 UTC
Identified - We have identified the root cause of the Stacks Mainnet stal Our engineers are actively working on restoring the connection and resuming block production. We will provide further updates as the situation progresses.
Nov 2, 16:44 UTC
Investigating - The Quicknode team is investigating an issue where Stacks Mainnet endpoints have stalled at block 9,395,980 since approximately 13:48 UTC. Users may be experiencing stale responses from Stacks Mainnet RPC endpoints. We will provide updates as more information becomes available.
Nov 2, 15:18 UTC
Base Mainnet – Delayed transaction inclusion (upstream)
Resolved - This incident has been resolved.
Nov 2, 15:55 UTC
Monitoring - Base has implemented a fix for the delayed transaction inclusion and is monitoring the results. Inclusion times should be returning to normal. We'll keep monitoring and update this incident once Base confirms it's fully resolved.
Nov 2, 15:44 UTC
Investigating - We're aware of delayed transaction inclusion on Base Mainnet caused by an issue on the Base sequencer side. Transactions sent through Quicknode endpoints are being accepted and forwarded normally, but may take longer than usual to be included in a block.

Base is actively investigating: https://status.base.org/incidents/9jdt5jc1ylry

We'll update this incident as Base shares more information.
Nov 2, 14:13 UTC

Nov 1, 2026

No incidents reported.

Oct 31, 2026

Solana Devnet: Agave 4.4.0 and Yellowstone gRPC v17 ahead of the Mainnet upgrade
Completed - The scheduled maintenance has been completed.
Oct 31, 20:44 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 30, 20:44 UTC
Scheduled - As part of our preparation for Agave 4.4 on Solana Mainnet, we are upgrading our Solana Devnet endpoints to the latest releases: Agave 4.4.0, Yellowstone gRPC v17, and our matching RPC and WebSocket serving layers. Nodes restart one at a time, so requests continue to be served throughout. Devnet is the place to test your integration against these changes before they reach Mainnet.

**Expected changes**

JSON-RPC

- getTransaction accepts an optional minContextSlot. If the node has not yet reached that slot, it returns error -32016 (minimum context slot not reached) instead of null.

- getSignatureStatuses accepts optional commitment and minContextSlot. The default commitment is still processed. When you set one, statuses below it are not returned, and minContextSlot behaves as in getTransaction.

- getLeaderSchedule:
accepts an optional keyByVoteAccount to key the result by vote account instead of identity; returns error -32022 when you ask for an identity that is not in the schedule. It used to return an empty result {}. If your code treats {} as “not a leader this epoch”, handle this error instead.

- getInflationGovernor now returns the cluster’s current inflation parameters instead of fixed default values.

- getBlocks over wide ranges is faster. Results are unchanged.

- Error messages for invalid base64 input keep the invalid base64 encoding: prefix, but the text after it may differ. Match on the prefix or the error code, not the full message.


WebSocket

- accountSubscribe and programSubscribe now apply dataSlice for binary encodings (base58, base64, base64+zstd). Notifications contain only the requested slice; a zero-length slice returns empty data. Before, dataSlice was ignored and the full account data was sent. If you send dataSlice but need full data, remove it.

Yellowstone gRPC

- The protobuf schema is unchanged, so existing clients need no update.
- Subscribing with from_slot now replays without gaps or duplicates when the stream joins live data.
from_slot is honored only on the first request of a stream; a later request’s from_slot is ignored.
- On confirmed and finalized subscriptions, the CreatedBank slot event now arrives together with its block’s data, so its position in the stream can differ from before.
- Alpenglow block-footer certificates are passed through exactly as the validator produces them, so none are dropped.
Oct 30, 20:42 UTC

Oct 30, 2026

[Urgent] NEAR - Mainnet - Upgrade to 2.14.0
Completed - The scheduled maintenance has been completed.
Oct 30, 23:59 UTC
Scheduled - We are upgrading our NEAR Mainnet infrastructure to nearcore 2.14.0 on 2026-10-30. This is a mandatory protocol upgrade (protocol version 86 to 88) introducing consensus-breaking changes, new action validation rules, and improved cryptographic support. Validators must upgrade before protocol version 87 voting begins on November 4th. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- view_access_key_list now supports pagination with after_key and limit parameters, returning a last_key field. Accounts with more than 100 access keys must use pagination; unpaginated requests for these accounts will fail.
- tx, send_tx, and broadcast_tx_commit responses now include an optional cause field on TIMEOUT_ERROR, describing transaction progress (NOT_OBSERVED, PENDING, DOES_NOT_TRACK_SHARD, or ERROR).
- tx_status is now the stable method name for what was EXPERIMENTAL_tx_status. Both names work identically; Quicknode documentation for tx_status is in progress.

https://github.com/near/nearcore/releases/tag/2.14.0
Oct 26, 20:12 UTC

Oct 29, 2026

[Urgent] Ault - Mainnet - Network Upgrade to v2.1.1
Completed - The scheduled maintenance has been completed.
Oct 29, 23:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 22:30 UTC
Scheduled - Ault Mainnet is undergoing a Network Upgrade on 2026-10-29 at 23 UTC (Target Height: 32,492,100)
This release adds telemetry metrics for aultvisor and aultd versions, upgrade progress tracking, aultd running status, and failed upgrade diagnostics. Brief interruptions to RPC availability may occur on that date.
Oct 28, 16:26 UTC
XRPL EVM Mainnet Network Upgrade - Service Disruption
Resolved - This incident has been resolved.
Oct 29, 16:39 UTC
Monitoring - A fix has been deployed and XRPL EVM Mainnet endpoints are returning current blocks again as of 16:16 UTC. Between 13:59 and 16:16 UTC, requests may have returned stale block data following today's network upgrade.
Oct 29, 16:21 UTC
Investigating - We are investigating service disruptions affecting XRPL EVM Mainnet following a scheduled network upgrade. Users may experience intermittent errors and degraded performance. Our team is actively working to restore full service and will provide updates as more information becomes available.
Oct 29, 16:03 UTC
XRPL EVM Mainnet Network Upgrade
Completed - The scheduled maintenance has been completed.
Oct 29, 16:35 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 15:35 UTC
Scheduled - XRPLEVM Mainnet is undergoing a Network Upgrade to 11.3.0. During this maintenance period you may experience interruption in service on XRPLEVM Mainnet.
Oct 29, 15:31 UTC
Multiple Chain Degradation - IAD Region
Resolved - This incident has been resolved.
Oct 29, 00:46 UTC
Monitoring - We have identified the issue in the IAD region and services are now stable. We are monitoring for any further impact.
Oct 29, 00:12 UTC
Investigating - The Quicknode team is currently investigating degradation in the IAD region. Customers may experience intermittent 503s and latency on our services.
Oct 28, 23:54 UTC
[Standard] Hedera Mainnet - Upgrade to Mirror Node v0.165.0 & RPC Relay v0.80.2
Completed - The scheduled maintenance has been completed.
Oct 29, 00:02 UTC
Scheduled - We are upgrading our Hedera Mainnet infrastructure to Mirror Node v0.165.0 and RPC Relay v0.80.2 on 2026-10-28. This release prepares the mirror node for the Nova/TSS 3.22.0 consensus-layer transition, introduces cryptographic improvements to block proof handling, and adds new REST and gRPC endpoints with enhanced security hardening. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
Block proof hashing — Block proof hashing is transitioning to a new format. Dual support for both block proof formats is maintained during the rollout period to enable gradual operator deployment.

https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.165.0
Oct 21, 16:59 UTC
[Urgent] Sui - Testnet - Upgrade to v1.83.0
Completed - The scheduled maintenance has been completed.
Oct 29, 00:01 UTC
Scheduled - We are upgrading our Sui Testnet infrastructure to v1.83.0 on 2026-10-28. This release advances the protocol to version 140 with consensus-breaking changes, including refined object funds withdrawal checks, transaction effects optimization, and substantial improvements to gRPC and error handling. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- SimulateTransaction — When gas selection cannot find enough SUI to cover the gas budget, the error now carries structured metadata (owner, requiredBudget, coinBalance, addressBalance) via a google.rpc.ErrorInfo with reason INSUFFICIENT_GAS_BALANCE (domain sui.io), allowing clients to read the required budget without message parsing. If budget estimation fails, the error reports the execution failure with reason TRANSACTION_EXECUTION_FAILED and includes ExecutionError details.
- SubscribeTransactions, SubscribeCheckpoints — Now populates effects object types, clever errors, and event json when the read mask requests them, matching GetTransaction behavior.
- ListTransactions, ListEvents — Requests below the node's retention now return OUT_OF_RANGE instead of INTERNAL. Cursors can be sent back in either ordering without skipping items. Descending requests with end_checkpoint above the latest indexed checkpoint + 1 now return OUT_OF_RANGE. On pruning fullnodes, all requests needing data below the pruning floor return OUT_OF_RANGE. Pages now correctly report hasNextPage/hasPreviousPage based on end reason rather than arbitrary boundaries.
- ListCheckpoints — Requests with a starting cursor past the server's indexed tip now return OUT_OF_RANGE instead of an empty page. Pages now correctly report hasNextPage/hasPreviousPage based on end reason. Checkpoints with an after cursor at or below filter.afterCheckpoint, or a before cursor at or above filter.beforeCheckpoint, now returns the checkpoints within the bound instead of an empty page.
- GetEpoch — Now lists mldsa65_auth among protocol feature flags.

https://github.com/MystenLabs/sui/releases/tag/testnet-v1.83.0
Oct 27, 17:59 UTC
Standard Fluent - Mainnet & Testnet - Upgrade to v1.5.1
Completed - The scheduled maintenance has been completed.
Oct 29, 00:00 UTC
Scheduled - We are upgrading our Fluent infrastructure to v1.5.1 on 2026-10-28. This release introduces native Ethereum precompiles (0x01–0x11 and P256VERIFY) via revm for significantly faster cryptographic operations, upgrades the rWasm runtime to 0.7.2 for improved consensus safety, and enforces a protocol-level transaction gas cap. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
eth_sendTransaction / eth_sendRawTransaction — Transactions exceeding 100 Mgas will be rejected by the network (EIP-7825 with Fluent-specific limit); clients sending such transactions will receive rejection errors.
Precompile execution (ecrecover, keccak256, sha256, ripemd160, bigModExp, bn256Add, bn256ScalarMul, bn256Pairing, blake2f, KZG, BLS12-381) — All Ethereum precompiles now execute via native revm implementations at the same addresses with identical gas costs and results, but with several times faster performance.

https://github.com/fluentlabs-xyz/fluentbase/releases/tag/v1.5.1
Oct 22, 16:36 UTC

Oct 28, 2026

[Standard] Bitcoin Mainnet - Upgrade ord to 0.29.1
Completed - The scheduled maintenance has been completed.
Oct 28, 23:59 UTC
Scheduled - We are upgrading our Bitcoin Mainnet Ordinals infrastructure from ord 0.23.2 to 0.29.1. This release rolls up several versions of indexer improvements, including richer inscription metadata in API responses, new gallery and bulk lookup endpoints, a new recursive endpoint for raw block data, and a fix for indexing transactions that include pay-to-anchor outputs. During the maintenance window, brief interruptions to Ordinals API availability may occur.

RPC Changes:
- Inscription JSON responses — added. Inscription responses now include a properties object (attributes, traits, title, and gallery items) along with the metaprotocol field.
- Inscription parents — fixed. Invalid parents are now filtered out and no longer returned for inscriptions.
- /children routes — added. Child inscription routes now support JSON responses.
- /gallery — added. New JSON endpoint for retrieving gallery inscriptions, with paginated gallery items.
- /galleries and /collections — changed. /collections now returns results in reverse order, and hidden inscriptions are excluded from both /collections and /galleries.
- /missing — added. New endpoint to check whether a batch of inscriptions exists in a single request.
- /r/block/ — added. New recursive endpoint that returns the raw block hex for a given block hash or height.
- Block inscriptions pagination — changed. Requests for an out-of-range page now return an empty page instead of an error.
- Outpoint and TXID lookups — fixed. Outpoints and TXIDs made up entirely of decimal digits now resolve correctly instead of being misrouted.
- Sat lookups — fixed. "Not found" sat index responses are no longer cached, so subsequent lookups return current data.
- Rune amounts — fixed. Decimal amounts with excessive precision or values that would overflow now return a proper error.
- Pay-to-anchor outputs — fixed. Transactions containing pay-to-anchor (P2A) outputs are now indexed correctly. Prior versions could return incorrect inscription and output data for these transactions.

https://github.com/ordinals/ord/releases/tag/0.29.1
Oct 20, 17:24 UTC
Cosmos Mainnet Outage - 503 Errors
Resolved - This incident has been resolved.
Oct 28, 15:35 UTC
Monitoring - Traffic has been restored and 503 errors are no longer observed. We will continue to monitor.
Oct 28, 15:24 UTC
Investigating - We are investigating an issue affecting Cosmos Mainnet endpoints. Users may be experiencing 503 errors when attempting to connect. Our team is actively working to restore service and will provide updates as more information becomes available.
Oct 28, 14:55 UTC
Aptos Testnet - Chain Stall at Block 16,617,441
Resolved - This incident has been resolved.
Oct 28, 05:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 28, 02:43 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 28, 00:20 UTC
Update - We are continuing to investigate this issue.
Oct 27, 23:59 UTC
Investigating - The Quicknode team is currently investigating a network-wide stall at block height 16,617,441.
Oct 27, 23:59 UTC
[Critical] Zcash - Mainnet & Testnet - Upgrade to Zebra 7.0.0
Completed - The scheduled maintenance has been completed.
Oct 28, 00:01 UTC
Scheduled - We are upgrading our Zcash Mainnet and Testnet infrastructure to Zebra 7.0.0 on 2026-10-27. This is a mandatory upgrade to support the NU7 network upgrade activation which is a consensus-level protocol change. Nodes must upgrade before the activation height to remain on the consensus chain. This release includes critical security fixes, RPC improvements, and peer synchronization enhancements. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
getinfo — Build field now includes full git commit metadata; updated peer discovery handling improves sync reliability.
getnetworkinfo, getpeerinfo — No longer blocks while processing large batches of gossiped peer addresses, improving responsiveness.
getaddresstxids, getaddressutxos — Now returns an error for queries matching more than 100,000 results; use startHeight and maxEntries pagination to narrow results.
getaddress* methods — Now accept at most 10,000 addresses per request instead of unlimited.

https://github.com/ZcashFoundation/zebra/releases/tag/v7.0.0
Oct 22, 15:56 UTC
[Standard] Gravity Mainnet - Upgrade to v1.10.1
Completed - The scheduled maintenance has been completed.
Oct 28, 00:00 UTC
Scheduled - We are upgrading our Gravity Mainnet infrastructure to v1.10.1 on 2026-10-27. This release contains bugfixes and optimizations, including improvements to RPC block-replay endpoints, consensus recovery at epoch boundaries, and startup stability. There is no hardfork and no new activation time. Brief interruptions to RPC availability may occur on that date.

RPC Changes:
- debug_trace*, trace_*, eth_callMany — Block replay now follows Gravity's execution rules, including system/user precompile sets, Alpha gas exemption, activation-block state changes, EIP-2935 handling, and onBlockStart logic. Requests targeting pending blocks will now fail; only committed blocks can be replayed.
debug_executionWitness* — This endpoint is now refused for all blocks.

https://github.com/Galxe/gravity-sdk/releases/tag/v1.10.1
Oct 19, 17:19 UTC

Oct 27, 2026

[Standard] Morph - Hoodi Testnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)
Completed - The scheduled maintenance has been completed.
Oct 27, 23:59 UTC
Scheduled - We are upgrading our Morph Hoodi Testnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC.

Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported.

During the maintenance window, brief interruptions to RPC availability may occur.

RPC changes:
- eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected.
- Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used.
- eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions.
- MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702).
- Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding.

https://github.com/morph-l2/morph/releases/tag/v0.6.4
https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7
Oct 21, 15:31 UTC
Injective Testnet - Degraded Performance
Resolved - This incident has been resolved.
Oct 27, 21:48 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 27, 21:36 UTC
Identified - Injective Testnet indexer APIs are degraded after a network-wide chain halt; standard RPC is working normally, and we are monitoring as the indexers catch up to the chain. We have escalated this to the Injective Foundation.
Oct 27, 21:25 UTC
Solana Testnet: Planned network halt
Resolved - This incident has been resolved.
Oct 27, 02:29 UTC
Investigating - Solana testnet has been halted by Anza as part of their planned stabilization process. Block production is paused network-wide until the cluster restarts. We're following Anza's restart process and will bring our nodes back online as soon as the network resumes. Solana mainnet and devnet are not affected.
Oct 26, 14:07 UTC
Incident History Powered by Atlassian Statuspage