The internet was supposed to be decentralized.
No central authority.
No single point of control.
A network of independent systems.
And for a while, it was.
But that’s not what we have today.
Decentralization was the design — not the outcome
The original internet was built as a distributed system.
Anyone could:
- run a server
- connect a network
- participate independently
No one owned it.
That structure still exists at a protocol level.
But structure and reality are not the same thing.
Efficiency slowly replaced independence
Running infrastructure is expensive.
Scaling systems is complex.
Maintaining reliability is hard.
So over time, a shift happened:
instead of running their own systems,
companies started relying on shared infrastructure.
Cloud providers made things:
- cheaper
- faster
- easier to deploy
And that convenience had a side effect.
Concentration.
The more traffic, the more centralization
As usage grew, traffic patterns changed.
Data started flowing through fewer, larger systems.
Today, a significant portion of global traffic moves through a small number of companies.
Not because it was designed that way.
Because that’s where efficiency led.
Infrastructure follows demand.
And demand concentrates.
Network effects reinforce the center
Once systems become large, they become more valuable.
More users → more data → better optimization → more users.
This creates a feedback loop.
The “network effect” makes larger platforms more attractive,
which pulls even more activity into them.
At that point, decentralization becomes less competitive.
Not technically.
Economically.
Optimization drives consolidation
Every system optimizes for something:
- cost
- latency
- reliability
- scale
And optimization favors centralization.
Fewer systems:
- are easier to maintain
- cheaper to operate
- more efficient to scale
This is the same pattern described in
Optimization Systems and Unintended Consequences.
No one optimizes for decentralization.
They optimize for performance.
And centralization is often the result.
Dependencies make centralization irreversible
Once systems depend on shared infrastructure,
moving away becomes difficult.
As described in
When Daily Life Depends on Software Infrastructure:
systems stop being optional.
They become essential.
Which means:
the infrastructure they rely on
becomes critical.
Fragility increases with concentration
Centralization creates efficiency.
But it also creates risk.
When more systems depend on fewer providers:
- failures affect more users
- outages spread faster
- recovery becomes harder
This is exactly the fragility described in
The Fragile Infrastructure Behind “Always Online” Services.
Failures scale with the system
In a decentralized system, failure is local.
In a centralized one, failure is systemic.
A small issue can propagate globally —
as shown in
How Small Infrastructure Failures Become Global Outages.
And when systems are tightly connected,
everything can fail at once, as described in
Why Modern Systems Fail All at Once.
No one planned this
There was no single decision.
No central authority redesigning the internet.
Just thousands of local decisions:
- choose the cheaper provider
- use the faster service
- rely on the more reliable platform
Each decision made sense.
Together, they reshaped the system.
What this actually means
The internet didn’t become centralized by design.
It became centralized through optimization.
Through convenience.
Through economics.
Through scale.
The architecture is still decentralized.
But the way we use it is not.
And once efficiency starts shaping systems,
the result is rarely distributed —
it converges.