What an endpoint does once the date passes
Two platforms describe it. One states that every inference request returns a specific status code. The other states that the model is removed from all regions and requests to it fail. One closure also deleted stored material after an export window. Everybody else describes nothing, mostly because nothing is scheduled. As of 2026-09-12.
| Entry | What is published | Detail |
|---|---|---|
| Microsoft Foundry | All inference requests return a named status | Software can tell this from a fault |
| Amazon Bedrock | Removed from all regions, and requests fail | No regional fallback remains |
| Sora | Material deleted after a final export window | The files, as well as the service |
| Wan-AI | Nothing changes for a copy already held | A listing coming down reaches no copy |
| Every application tracked | Nothing published | No date, so no aftermath described |
Inclusion rule. Filled from a published sentence about behaviour after a stated date. A reader's expectation of what a failing service looks like does not fill a cell. Order. Entries describing an aftermath first, then the rest.
1A named status is the single automated warning here
Naming the exact response lets a caller branch on it, alert on it, and distinguish a retirement from a transient fault. That turns the event into something software handles rather than something a person investigates.
It fires on the day rather than before it, so it is containment and not planning. The same platform publishes a notice period, which is why it is the one entry where the two connect.
2Global removal closes the route people reach for
Multi-region platforms teach their customers to solve availability problems by moving. Stating that removal happens everywhere removes that option explicitly, which saves a week of investigation at the worst possible moment.
It also means the migration is to another model rather than to another place, and no interim arrangement exists to buy time with.
3Capability and material end on different days
Where output is returned per call, a retirement removes the ability to make more and reaches no existing file. Where a product kept a library, the same event can reach the library too.
The one documented case did exactly that, with deletion after an export window. That is why stored work is a separate column from the calendar.
- What the endpoint does after the retirement dateAll inference requests return 410 Gone
- What happens at end-of-lifeAfter the end-of-life date the model is removed from all AWS Regions and requests made to it fail
- What happens to the workData associated with Sora is deleted after any final export window passes
- Licence stated on the weightsApache 2.0
4Sources
Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: Can a date move, Cut off early, Who moves you.