Monday, November 16, 2026

No, XRP Ledger is producing ledgers

Its newest ledger, number 108,358,095, was made 6 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 4 s.

Read from the chain 58 s ago

Each mark is a minute of ledgers; a shorter mark means fewer than normal. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.

4 snormal time between ledgers
4 saverage over the last hour
Instantfinalityvalidated ledger
650days since the last halt
100%uptime we measured, last 3 days
100%on one client, single implementation

Halts over time

Every halt and finality stall on record for XRP Ledger since 2024: from postmortems, status pages and news reports, plus the ones we measured ourselves. Point at a dot, or focus the rail and use the arrow keys; Enter opens the incident.

We have measured XRP Ledger ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between ledgers for each hour over the last 7 days, or since we started measuring on 12 Nov 2026. The dashed line is the normal pace. Red hours contain a halt; empty hours are gaps in our sampling.

0 ms4 s8.1 s12 Nov 21:00 UTC: 3.9 s per ledger12 Nov 22:00 UTC: 4 s per ledger12 Nov 23:00 UTC: 4 s per ledgerFri 1313 Nov 00:00 UTC: 4 s per ledger13 Nov 01:00 UTC: 4 s per ledger13 Nov 02:00 UTC: 4.1 s per ledger13 Nov 03:00 UTC: 4.1 s per ledger13 Nov 04:00 UTC: 4.1 s per ledger13 Nov 05:00 UTC: 4.1 s per ledger13 Nov 06:00 UTC: 4.1 s per ledger13 Nov 07:00 UTC: 4 s per ledger13 Nov 08:00 UTC: 4.1 s per ledger13 Nov 09:00 UTC: 4 s per ledger13 Nov 10:00 UTC: 4 s per ledger13 Nov 11:00 UTC: 4 s per ledger13 Nov 12:00 UTC: 3.9 s per ledger13 Nov 13:00 UTC: 4.1 s per ledger13 Nov 14:00 UTC: 4.1 s per ledger13 Nov 15:00 UTC: 4.2 s per ledger13 Nov 16:00 UTC: 4 s per ledger13 Nov 17:00 UTC: 4.1 s per ledger13 Nov 18:00 UTC: 4 s per ledger13 Nov 19:00 UTC: 4 s per ledger13 Nov 20:00 UTC: 4 s per ledger13 Nov 21:00 UTC: 4 s per ledger13 Nov 22:00 UTC: 4 s per ledger13 Nov 23:00 UTC: 4 s per ledgerSat 1414 Nov 00:00 UTC: 4.1 s per ledger14 Nov 01:00 UTC: 4.1 s per ledger14 Nov 02:00 UTC: 4.1 s per ledger14 Nov 03:00 UTC: 4.1 s per ledger14 Nov 04:00 UTC: 4 s per ledger14 Nov 05:00 UTC: 3.9 s per ledger14 Nov 06:00 UTC: 4 s per ledger14 Nov 07:00 UTC: 4.1 s per ledger14 Nov 08:00 UTC: 4.1 s per ledger14 Nov 09:00 UTC: 4 s per ledger14 Nov 10:00 UTC: 4 s per ledger14 Nov 11:00 UTC: 4 s per ledger14 Nov 12:00 UTC: 4 s per ledger14 Nov 13:00 UTC: 4.1 s per ledger14 Nov 14:00 UTC: 4.3 s per ledger14 Nov 15:00 UTC: 4.2 s per ledger14 Nov 16:00 UTC: 4.1 s per ledger14 Nov 17:00 UTC: 4.2 s per ledger14 Nov 18:00 UTC: 4.1 s per ledger14 Nov 19:00 UTC: 4 s per ledger14 Nov 20:00 UTC: 4.3 s per ledger14 Nov 21:00 UTC: 4.3 s per ledger14 Nov 22:00 UTC: 4.3 s per ledger14 Nov 23:00 UTC: 4.2 s per ledgerSun 1515 Nov 00:00 UTC: 4.3 s per ledger15 Nov 01:00 UTC: 4.2 s per ledger15 Nov 02:00 UTC: 4.4 s per ledger15 Nov 03:00 UTC: 4.3 s per ledger15 Nov 04:00 UTC: 4.1 s per ledger15 Nov 05:00 UTC: 4 s per ledger15 Nov 06:00 UTC: 4 s per ledger15 Nov 07:00 UTC: 4 s per ledger15 Nov 08:00 UTC: 3.9 s per ledger15 Nov 09:00 UTC: 4.1 s per ledger15 Nov 10:00 UTC: 4 s per ledger15 Nov 11:00 UTC: 3.9 s per ledger15 Nov 12:00 UTC: 4 s per ledger15 Nov 13:00 UTC: 4.1 s per ledger15 Nov 14:00 UTC: 4 s per ledger15 Nov 15:00 UTC: 3.9 s per ledger15 Nov 16:00 UTC: 4 s per ledger15 Nov 17:00 UTC: 4 s per ledger15 Nov 18:00 UTC: 4 s per ledger15 Nov 19:00 UTC: 4 s per ledger15 Nov 20:00 UTC: 4.1 s per ledger15 Nov 21:00 UTC: 4 s per ledger15 Nov 22:00 UTC: 4 s per ledger15 Nov 23:00 UTC: 4 s per ledgerMon 1616 Nov 00:00 UTC: 4 s per ledger16 Nov 01:00 UTC: 4 s per ledger16 Nov 02:00 UTC: 4 s per ledgernormal 4 s

Halts we detected

None so far. We have been measuring since 12 Nov 2026.

The public record since 2024

From postmortems, status pages and news reports.

DateTypeDurationWhat happenedSources
4 Feb 2025Halt≈64 minConsensus kept running but validations were not published, so the network drifted apart and stopped validating ledgers at height 93,927,173 until it re-converged.
Note on timesClock times are uncertain. The Block says 'late Tuesday' with no times. A secondary report says the ledger restarted at 10:58 UTC on Feb 4. The duration is about 64 min.
theblock.co
25 Nov 2024, 13:39 UTCHalt10 minA caching-layer bug in rippled could return an inconsistent result type and crash servers; many nodes crashed and restarted, so no transactions were processed for about 10 minutes (fixed in rippled 2.3.0).dev.to

Client software

rippled Single implementation

Validators run rippled, the only production server.

ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains

Compare

Embed this status

Show the live XRP Ledger status in your docs, dashboard or README.

Is XRP Ledger down? Live status by ChainReport

The badge updates about once a minute and links back to this page. Feed for XRP Ledger incidents: Atom.

Links

We read XRP Ledger from two places: first source XRPL Cluster and second source Ripple public server.

Other chains

Also on the Network Desk for XRP Ledger

How this works and where the data comes from

What we measure. Every minute a server job asks each chain for its newest block and reads the timestamp the chain itself put in that block. "Last block" is now minus that timestamp, so it is accurate even if our own checks run late. "Last hour" is the average spacing between blocks over the past hour, also from block timestamps.

When we call a halt. A chain counts as halted when no new block has appeared for much longer than normal. The limit is set per chain: 2 minutes for most fast chains, 5–7 minutes for Scroll, ZKsync and Cardano, 14 minutes for Dogecoin, 30 minutes for Litecoin and 2 hours for Bitcoin, where long gaps happen by chance. Before declaring a halt we ask a second, independent data provider. If one provider is stale and the other is fresh, the chain is fine and we log the provider as lagging. For Solana, Sui and Cardano we have only one free source, so we wait for three stale checks in a row. Start time is the last block before the stop; end time is the first new block, within about a minute.

Finality. For Ethereum we read the last finalized checkpoint from the beacon chain (normally 2 epochs, about 13–19 minutes behind). For other EVM chains and Polkadot we read the newest "finalized" block from the node. On rollups (Base, Arbitrum, OP, ZKsync, Scroll), "finalized" means settled on Ethereum, which takes longer by design: hours on ZKsync. Free Solana endpoints do not report commitment levels reliably, so we do not show Solana finality.

Limits. We have been measuring since 12 Nov 2026; uptime figures cover only that period and say so. If our job misses minutes, a halt that started and ended entirely inside that gap would show up only as a slow hour in the chart. The historical record before our measurements comes from postmortems and news reports, with approximate times marked "≈". Hyperliquid is measured through HyperEVM, which stops whenever the HyperCore L1 stops.

Sources: XRPL Cluster; Ripple public server; Historical record: project postmortems, status pages, The Block, CoinDesk, Cointelegraph, Decrypt (linked per row)

Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.