Skip to content
All articles
With cloud AI

When the AI service goes away, the workflow goes with it.

An AI service can go down, or it can disappear. An outage is temporary and a model retirement is permanent. Both interrupt a business process, and only one of them shows up on a status page.

BastionUpdated 4 min read

Cloud AI gives an organisation access to infrastructure it does not own. That is the advantage, and the trade is that the organisation inherits the provider’s availability, lifecycle and decisions. For many workloads that is acceptable. For a critical workflow it has to be planned for.

3 September 2026: ChatGPT, Claude and Grok went down

On Thursday 3 September 2026, OpenAI’s ChatGPT, Anthropic’s Claude and xAI’s Grok all went down in the same morning, Eastern time.

Computerworld reported no confirmed cause. Brian Jackson, a principal research director at Info-Tech Research Group, told it that simultaneous outages at different providers are a curious scenario, and that a shared layer, such as a content delivery network, DNS or shared cloud infrastructure, could be the link.

ServiceDown forSource
ClaudeAbout four hours, from 7:37 a.m. ETComputerworld
GrokAbout three and a half hoursComputerworld
ChatGPTAbout two hours, from around 11 a.m. ETComputerworld
The outage of 3 September 2026, service by service, as recorded by Computerworld

The analyst Carmi Levy told Computerworld that enterprises could find themselves “uncomfortably exposed” when AI hits the brakes, and that “too many organizations are about to learn some hard lessons about not having a backup plan in place.”

An organisation using any one of those services did not control the recovery. The status page, the infrastructure and the incident response all belonged to the vendor. The customer could wait, escalate and start a contingency plan, and could not repair the service.

February 2026: ChatGPT retired GPT-4o and four other models

TechCrunch reported on 13 February 2026 that OpenAI stopped providing access to five legacy ChatGPT models that day. OpenAI’s API deprecations page lists the removals from the API.

DateWhat was retired or removedSource
13 February 2026GPT-4o, GPT-4.1, GPT-4.1 mini, OpenAI o4-mini and GPT-5, retired from ChatGPTTechCrunch
17 February 2026The chatgpt-4o-latest snapshot, removed from the APIOpenAI Developers
1 October 2026The gpt-5.4-cyber model: its API shutdown date, listed under “Past deprecations”OpenAI Developers
Models retired or removed in 2026, as reported by TechCrunch and as listed on OpenAI’s deprecations page

A provider that ships better models must retire the old ones, and the consequence falls on the customer. Software vendors have always changed APIs. AI adds a second layer, which is behavioural dependency: two models can accept the same prompt and return materially different results. The API still responds and the workflow still completes, but the output has moved.

In a company that spent six months putting a model into a workflow, employees learned it, the prompts were tuned, the outputs were tested, compliance reviewed the process and the documentation was written. When the model is retired, the replacement may give better answers. It is not guaranteed to give the same answers, so the validation runs again. For a casual user that is a minor inconvenience. For a bank processing documents, a hospital preparing clinical drafts or a legal team extracting facts from case files, it is a revalidation on the vendor’s timetable.

What DORA requires: a tested exit plan

For a regulated financial entity, DORA requires an exit strategy for each ICT service supporting a critical or important function, and Article 28(8) says the exit plans “shall be sufficiently tested and reviewed periodically”.

Article 30(2)(f) also requires the contract to provide assistance at no additional cost, or at a cost determined in advance, when an ICT incident occurs. A per-token API contract rarely says that.

A second cloud provider supplies redundancy on paper. If both depend on the same connectivity, the same identity infrastructure or the same cloud architecture, the redundancy is thinner than it looks.

A local system can fail too

A server can lose power, a disk or a network switch can fail, a software update can introduce a fault, and a building can become inaccessible. The organisation can plan around these risks directly: a spare component on the shelf, backup power, and a recovery procedure tested without waiting for someone else’s status page.

Five questions to answer in writing before a model goes into production

  • What happens if the model is unavailable for four hours?
  • What happens if it is retired, and what happens if the replacement behaves differently?
  • How quickly can the workflow move elsewhere?
  • Can the data and the configuration be exported?
  • Has the exit plan been tested?

If the answers depend entirely on another provider’s infrastructure, the dependency already exists, whether or not the business has written it down.

With Bastion

What Bastion changes

Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.

Bastion runs the model on a unit at your site or in a partner data centre. It answers without any AI provider’s service, and the model changes only when the organisation accepts a refresh. The exit plan ships with the appliance. Documents, index and logs leave in open formats, and the model weights are open weights.

An appliance can fail as well. It is one machine, and a machine has a power supply and a disk. Bastion keeps one spare power supply for the whole fleet and stays the owner of the unit, so a failure is a whole-unit swap under the contract.

Questions this article answers

What does DORA require in an exit plan?
An exit strategy for each ICT service that supports a critical or important function, and the plan must be “sufficiently tested”. Article 30(2)(f) also requires incident assistance at no extra cost or at a cost set in advance.
When did OpenAI retire GPT-4o?
ChatGPT retired GPT-4o, GPT-4.1, GPT-4.1 mini, o4-mini and GPT-5 on 13 February 2026. The chatgpt-4o-latest API snapshot was removed on 17 February 2026.
What happens to a workflow when the model is retired?
The replacement may give different answers to the same prompt. So the validation runs again, on the vendor’s timetable.

On the record

  1. 1
  2. 2
  3. 3

    OpenAI Developers

    Deprecations

    read 2026-11-17

  4. 4