XRP Ledger
XRPL Foundation Reports Over 1.7M Daily Ankr Node Requests
The XRPL Foundation reports over 1.7 million daily requests to free Ankr nodes. App builders still need to account for rate limits, limited history and availability.

What XRPL Foundation’s 1.7 million request figure means
The XRP Ledger Foundation says its free Ankr-backed nodes handle more than 1.7 million developer requests daily. That measures use of a network access service, not unique users or completed XRP payments. Developers evaluating the service should examine request limits, retained history and availability alongside the headline traffic figure. [1][2]
The Foundation’s November 12 update concerns the service Ankr launched August 3, 2026. [1][2][3] The development is therefore a usage milestone for existing infrastructure, rather than the opening of a new network or the activation of a new XRP Ledger feature.
A remote procedure call, or RPC, is an instruction an application sends to a server. The server can answer a question about the ledger or relay a transaction. Ankr documents both kinds of operation. That distinction makes the denominator important: a busy information service can receive many requests without an equivalent number of payments being made. [5][6][8]
Uncertainty: the short Foundation update does not provide a breakdown by method, distinct application, mainnet versus testnet, or successful versus failed response. It also does not establish a sustained growth rate. Until those categories are disclosed, the sound interpretation is reported service traffic, with the composition of that traffic unresolved. [1]
Why an XRP balance lookup is different from an XRP payment
The official account_info reference describes a query that returns account information and an XRP balance relative to a particular ledger version. Ankr lists that method among its supported account tools. A request can therefore be useful to a wallet user while doing nothing more than displaying information that already exists. [5][6]
Consider a hypothetical wallet session. A person opens a balance screen, refreshes it, checks an account’s assets and revisits the screen later. Those interactions can produce several server requests even if the person never sends a payment. Conversely, one automated application can request information for many accounts. These examples explain the counting problem; they are not measurements of how Ankr’s reported traffic is distributed.
For an application team, a useful dashboard would separate reads, transaction submissions, responses containing errors and repeated attempts. It should then connect those categories to completed user tasks. A rising request count with unchanged task completion would prompt a different investigation from an increase in successful payments. The former could justify examining inefficient refresh behavior before purchasing more capacity.
For XRP holders, the implication is equally specific. This announcement alone cannot quantify new economic activity or demand for the token. It reports use of the access infrastructure. A stronger adoption claim would require independently described applications, their production status and a measurement connecting usage to a relevant ledger outcome.
Ankr’s history window matters when an XRP app must reconstruct records
Ankr’s XRP documentation, updated November 11, specifies roughly two weeks of retained history; older queries fail. It directs users needing older records to an archive or explorer. Crypto.news reports the same limit. [2][5]
Analysis: that makes recent account access and long-term record reconstruction different service requirements. A wallet may appear satisfactory during a demonstration using fresh transactions, yet need another data source when a customer asks about an older payment. A development team should define the oldest record its product promises to retrieve before deciding that one endpoint covers the whole experience.
A useful acceptance exercise is to select a known recent transaction and a known older transaction, record their ledger references, and attempt the actual history view the product offers. The result should distinguish data unavailable from this provider from a transaction that did not occur. This is a proposed test, not a claim that AllAboutXRP benchmarked Ankr’s historical responses.
The distinction also affects support work. If a history lookup fails, the support screen should retain enough context to route the case to an archive source. Treating a provider’s retention limit as evidence of a missing payment would convert an infrastructure constraint into an incorrect explanation for the customer. The product’s archive plan belongs in its operating design, rather than being discovered during a dispute.
For an accounting export, make the coverage boundary explicit: the requested period, the period actually returned and any unresolved gap. A partial export should not silently look complete. This proposed check helps separate a usable recent-history tool from a record suitable for a longer reporting period.
Free public XRPL access does not define a production service commitment
The XRPL RPC portal offers mainnet and testnet access without an API key, subject to per-IP rate limits and best-effort availability. [2][4] None of those statements supplies a guaranteed capacity allocation for an individual application.
Analysis: a team should map how its users reach the endpoint. If requests pass through a shared backend, the limit relevant to that shared connection may matter more than the number of people using the app. This is an architecture consideration, not a finding about Ankr’s undisclosed rate-limit values. Those values and their treatment of bursts should be confirmed directly before setting product expectations.
XRPL’s directory warns against sustained or business use of Ripple’s public servers, which may become unavailable. [2][7] That warning applies to Ripple’s listed service; it is not an Ankr outage report. It illustrates why moving to another free URL does not by itself establish suitable operating terms.
A procurement decision should start with the consequence of a failed request. A delayed exploratory chart and a stalled customer workflow impose different obligations. Teams can then compare the history required, acceptable interruption, recovery procedure and support contact. Paying for an endpoint is not sufficient evidence either: the contracted coverage must match the actual workflow.
What XRP application teams should verify next
A practical next step is a short workload review: identify the queries each screen needs, record what happens when the endpoint refuses a request, and establish where older records will come from. Keep testnet exercises separate from production reporting so experimental traffic does not become an unexplained component of a business-use claim.
XRPL’s official reference and independent infrastructure provider QuickNode describe submission as sending a transaction for later confirmation and ledger inclusion. [8][9] Analysis: give each application operation its own success criterion. Rendering the requested balance completes a read task. A submission acknowledgement answers a narrower question than a confirmed result. Keep those labels separate in the interface and in usage reports, even when both operations travel through the same endpoint.
Before launch, assign an owner to three failure cases: an unavailable endpoint, an unavailable historical record and an unresolved submission. The owner should know what the interface tells the user, which evidence is retained and where escalation goes. That turns an infrastructure selection into a recoverable service rather than a list of connection URLs.
What would change the assessment? A published request methodology, method-level success data, an explicit history expansion or a documented service commitment would each answer a different open question. Until then, the milestone is useful evidence of demand for access, while the requirements for dependable applications remain workload-specific. It gives builders a reason to evaluate the service, not a substitute for that evaluation.
What to watch next
- • A Foundation methodology separating mainnet and testnet, query types, retries and successful responses. [1]
- • Ankr publishing precise public-tier rate limits and how bursts or shared connections are treated. [4]
- • A dated archive-support release or documentation change extending the current history window. [3][5]
- • Application teams demonstrating old-record retrieval and recovery after endpoint failure, rather than citing aggregate traffic alone.
- • Service commitments that explicitly cover the production methods, history and support a particular application needs. [4][7]
Sources and verification
We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.
- [1]XRPL Foundation: Ankr-backed public-node usage updateprimary
- [2]Crypto.news: Foundation reports daily requests and service limitssupporting
- [3]Ankr: public XRP Ledger RPC launchprimary
- [4]XRPL RPC: public service access and availability termsprimaryUndated reference
- [5]Ankr: XRP methods and retained history (updated November 11)primary
- [6]XRP Ledger documentation: account_infoprimaryUndated reference
- [7]XRP Ledger documentation: public server optionsprimaryUndated reference
- [8]XRP Ledger documentation: transaction submissionprimaryUndated reference
- [9]QuickNode: XRPL submit method (updated June 11)supporting