The origin tracer is paused

What is paused

The origin tracer itself. You cannot currently submit a TRON address for analysis, and the API behind that analysis returns a 503 Service Unavailable to anything that asks. That covers wallet origin scoring, current-control resolution, the AI explanations, and the feedback form that sat in the site footer.

This is deliberate and it is the whole of what stopped. It is a pause on the part of the service that runs live queries against paid and rate-limited data sources — not a shutdown of TRONORIGIN, and not a retirement of anything published here.

What is open

The written half of TRONORIGIN stays open, and none of it needs the tracer in order to be read:

• The Learn library — the full corpus on TRON origin tracing, wallet control, permissions and attribution.
• The glossary — every term the library and the tracer use, defined.
• The manual — how to read an origin result and what each part of it means.
• How it works and the FAQ — the method, its evidence, and its limits.
• About — what the tool is and is not.

New articles continue to be written and published while the tracer is paused. The pause applies to the tracer, not to the writing.

Five things do change for as long as the pause lasts, and it would be wrong to round them away. The feedback button is gone from the site footer, because the form behind it could only ever have reported a failure. Any article carrying a live on-chain figure shows its last recorded snapshot rather than updating. The status marker in the header and the footer reads paused instead of naming the network it is no longer talking to. The footer no longer lists the data sources the tracer reads, because while it is paused it reads none of them. And the footer’s link to How it works is marked origin tracer paused, because that page describes the tracer in the present tense and it is not running.

When it comes back

The tracer returns when the work on it is finished. We are not naming a date, because an open-ended pause with a date attached is a promise that gets broken rather than kept — and a date is not something we can honestly give you today.

What we can tell you is what a restore looks like: the analyzer comes back at the homepage, this page stops existing, and everything that points at it goes away with it — the notice at the top of every page, the footer’s origin tracer paused mark, and the line on How it works saying the pipeline is not running. Nothing published here moves or changes URL in the meantime, so anything you have linked or cited stays where it is.