410 Gone: a retirement software can recognise
410 Gone is the response one platform in this register states its retired models return. It is the only machine-readable retirement signal here: a caller can branch on it, alert on it, and tell it apart from a transient fault without investigating anything. As of 2026-09-22.
| With a named status | With an unexplained failure |
|---|---|
| Software can alert on the exact cause | Somebody investigates an outage |
| A retirement is distinguishable from a fault | Both look like a failed request |
| The date is confirmed from your own logs | The date is confirmed by reading a page |
| A fallback can be triggered automatically | The fallback starts after a person notices |
Inclusion rule. Read from the lifecycle policy of the one platform in this register that names a status for a retired model. Order. What becomes possible first, then the alternative.
1A status arrives on the day, not before
This signal is confirmation rather than warning. It fires when the retirement happens, which is useful for containment and useless for planning, so it sits alongside a notice period rather than replacing one.
The same platform publishes both, which is why it is the one entry where an automated check and a scheduled migration can be connected to each other.
2The absence of a named status is the norm
Fifteen entries in this register describe no behaviour after a date, mostly because they publish no date. A production on any of them learns about a change when its own output stops or starts looking different.
That is the ordinary state of this market rather than a failing of any particular product. Naming a status requires having a lifecycle process to name it in.
3What it does not tell you
Where to go next. The status confirms that a specific version has gone and carries no successor, no date for the successor, and no statement about migration.
Those are separate disclosures, and the register keeps them in separate columns because almost no entry publishes more than one of them. The successor term sets out the other half.
A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the reading on what happens after the date. Nearby terms: Region availability, Inactivity clause, Active deployment.