Concern 173 · Working draft · editorial review in progress

Cloud-provider risk

Cloud-provider risk is the exposure created when an AI service depends on another company's computing infrastructure.

Understanding the concern

An outage, account problem, security incident, or service change at the provider can interrupt applications built on top of it. Several apparently separate AI tools may share the same underlying infrastructure, so switching between them may not remove the dependency.

The concern should not be reduced to an unsupported claim that exactly two or three firms run everything. What matters for a particular service is its actual dependency chain and recovery options. Backups help only if the team can use them when the main provider is unavailable.

An example

Several shops use different delivery brands, but all rely on the same warehouse. A warehouse failure reaches them all.

Illustrative unless identified as a documented case.

Words in plain English

AI
Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.

Evidence and its limits

The sources support dependency and concentration mechanisms. They do not provide a current count or market-share estimate for cloud providers.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

Which shared provider failures would stop us, and have we tested a workable recovery path?

Keep track of different views, what needs checking, and any next step in your own discussion notes.

Open discussion notes →
Principles for the conversation

Before you finish · reflect together

Virtues and principles to consider

Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.

Stewardship

Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.

Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.

Ask together: What are we responsible for caring for over time?

Prudence

Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.

Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.

Ask together: What is a careful next step, and when should we stop or change course?

Accountability

Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.

Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.

Ask together: Who will answer for the outcome and help put things right?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Major · 4/5
Likelihood
Widely observed · 4/5
Time horizon
Now
Register risk score
16
About the register and scoring →
More ways to explore

Search for more writing

For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.

Explore a proposed use of AI →