LLMSwaps

Which model each app runs today, and when it last changed

The five months between Sora's two closures

OpenAI closed the Sora web and app experiences on 26 April 2026 and states that the interface is discontinued on 24 September 2026. That is roughly five months between the two closures. Nothing in the announcement presents the gap as a commitment, so this column records it as an observation. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhat Sora publishesWhat SorapublishesWhat that leaves openWhat that leavesopenWas a period promised in advan…Was a period promised in advanceWas a period promised in advance — What Sora publishes: Nothing was published before the noticeWas a period promised in advance — What that leaves open: The dates arrived with the announcementWhat interval actually occurredWhat interval actually occurred — What Sora publishes: About five months, April to SeptemberWhat interval actually occurred — What that leaves open: Between the consumer product and the interfaceWhich surface went firstWhich surface went first — What Sora publishes: The web and app experiencesWhich surface went first — What that leaves open: Individuals lost the tool before builders didWas a successor namedWas a successor named — What Sora publishes: No replacement model is namedWas a successor named — What that leaves open: So the runway led nowhere in particular
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the discontinuation notice settles about warning, and what it only illustrates. Recorded 2026-09-22.
What the page is askedWhat Sora publishesWhat that leaves open
Was a period promised in advanceNothing was published before the noticeThe dates arrived with the announcement
What interval actually occurredAbout five months, April to SeptemberBetween the consumer product and the interface
Which surface went firstThe web and app experiencesIndividuals lost the tool before builders did
Was a successor namedNo replacement model is namedSo the runway led nowhere in particular

Inclusion rule. Read from the vendor's own discontinuation article. The interval between the two dates is recorded as an observation and is never presented as a commitment. Order. What was promised first, then what happened.

1One observation is not a norm

Five months reads like a reasonable industry practice until you notice the sample size. It is one retirement by one company, and nothing in the notice suggests the interval came from a policy rather than from a schedule that landed where it landed.

Treating it as typical would set every plan in this field against a number nobody promised. The next retirement will either match it or show that it never meant anything, and until then the honest reading is that no application has committed to any figure.

Five months, and what it did not includeThe consumer surface closed in April and the interface in September, an interval of roughly five months. Nothing in the notice presents that as policy, and no successor is named, so the runway led nowhere in particular.The one retirement in this register with published datesWeb and append26 April 2026People usingthe productlose the toolon this date.Both reachablevia resellersFive monthsSome appsstill name themodel throughthis period.Interface ends24 September2026Teams thatbuilt on itstop here. Nosuccessornamed.An interval that happened, not a commitment that was made
Fig. 2 One retirement by one company: a floor on what is possible, and no evidence at all about what is usual.

2The order of the closures is the informative part

The consumer surface went first and the programmable one second. That is the usual order and it decides who gets a runway: a person using the product lost their tool on the earlier date, while a team calling the interface had until the later one.

It also explains why resellers kept naming the model in between. For five months the weights were reachable through somebody else's product while the maker's own was already gone, which is the gap this register was built to make visible.

3A runway with no destination

The notice ends a service without naming what follows it. Five months of warning is worth much less when the migration target is unstated, because the work of testing a successor cannot begin until somebody decides which successor to test.

The register keeps that absence in the named replacement column rather than folding it into this one. A date and a destination are two commitments, and this notice made only the first.

  • Sora web and app
    26 April 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Sora API
    24 September 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Named replacement model
    No date announced (as of 2026-09-12)none in the announcementOpenAI Help Center / recorded 2026-09-12

4Sources

Read from the discontinuation article on help.openai.com, 2026-09-22. The whole entry is on Sora, and the column it sits in is on Notice period. Same column, other entries: Microsoft Foundry, Amazon Bedrock.