The Radix Gateway still knows exactly where the ledger stopped. It will not tell you what the ledger holds.
Open
mainnet.radixdlt.com and it answers in one line: state version 557840622, epoch 339896, round 102, timestamped 2026-08-31T21:19:06.179Z. That is the last round the network committed.
Ask the same host for an account balance, the validator list or a transaction stream and each one returns a 500: "The Gateway API cannot return current results as its database is not sufficiently up to date with the Network's Ledger." Checked this evening, it is 3 days, 22 hours and 49 minutes behind, against a ceiling of 720 seconds.
That ceiling is the whole mechanism. The Gateway is an index sitting in front of the nodes, and it refuses any answer more than twelve minutes stale so that no dApp ever renders an old balance as a current one. A halted ledger trips the guard the same way a broken index would. The guard cannot tell "I am behind" from "the network stopped".
Which is why the main Radix chat has spent today asking each other whether XRD moved. The record is intact and final at 557840622. What is shut is the index in front of it, and the number that shuts it is a setting.