An Extended Global Node is a full node that keeps more history than a standard full node of the same protocol, but not a complete archive from genesis. Extended does not change request-unit billing.
Which nodes are Extended
Extended applies only to Global Nodes. The protocols and networks that offer Extended Global Nodes show Extended in the Global Node Mainnet Support and Global Node Testnet Support columns on Networks. Each protocol’s history depth is listed in How much history each protocol keeps.
Billing
Extended is not a separate billing class. Requests to an Extended Global Node are billed the same as requests to a Full Global Node of the protocol. See Full vs archive by protocol.
How much history each protocol keeps
History depth depends on the protocol and the network, and it can change over time. Each protocol reports its current range at runtime, so read the range from the node instead of assuming a fixed depth:
- Sui — the gRPC
LedgerService/GetServiceInfo method reports lowestAvailableCheckpoint, the oldest checkpoint the node holds. Plan against the window from that checkpoint to the tip on both gRPC and JSON-RPC. See Checkpoint retention. On Mainnet, GraphQL reports its windows through serviceConfig.availableRange, and its filtered transaction and event queries keep a shorter window — see How far back GraphQL history goes.
- XRP Ledger — keeps more recent ledgers than a default
rippled server. server_info reports the range the node holds in complete_ledgers. See How much ledger history your node holds.
- Stellar —
getHealth reports the retention window, from oldestLedger to latestLedger, which bounds transaction and event queries on both networks. On Mainnet, getLedgers also serves ledgers older than the window, back to ledger 2. On Testnet, getLedgers is limited to the window. See Historical data availability.
Last modified on September 29, 2026
