Your phone, a single point of failure

A single point of failure is a piece that, if it fails, brings everything else down with it. Your phone has become one: it holds your email, your two-step verification, your number and sometimes your bank, all together.

Updated on October 26, 2026 · Reading time: 6 min

What it is

A piece that takes down the whole system

Since

It's a principle, not a date

Does it affect you?

Yes

What it is

A single point of failure is any part of a system whose failure brings down the whole system, because there's no second path to replace it. If a system has a hundred parts and ninety-nine keep working, but that one breaks and everything stops, that one part is the single point of failure.

In your digital life, that point is increasingly your phone. Not because it's fragile, but because today it concentrates functions that used to be spread out: it's your authenticator app, the device that approves your logins, your phone number, and, in many cases, also where you open your bank. You used to need to lose several things at once to get locked out. Today, losing just one is enough.

Think about everything that probably only lives on your phone right now: your banking app, your password manager app, the app that generates your verification codes, your passkeys, the SIM with your number, and often also your signed-in email session. That's six or seven different functions, which used to live in different places — the bank in a passbook, the codes on a coordinate card, email on the home computer — and today share a single case.

Since when

It has no birth date: it's a principle from systems engineering, used for power plants, telecom networks or critical infrastructure, where it's deliberately designed so no single piece is like this. The problem is that same rule hasn't been applied to how we organize our personal accounts.

What does have a date is the concentration: the more things migrate to the phone — payments, passkeys, second factors, messaging — the fewer spare parts are left if that phone disappears. The convenience of having everything in one place is the same reason that, if that one place fails, everything fails.

The phone doesn't have to break for the problem to show up. It's enough for it to run out of battery at a bad moment, get stolen, fall in water, or simply get left in a taxi. The practical result is the same in all four cases: for a while, or for days, that one device is unavailable, and with it, so is everything that depended only on it.

Why it happens

Nobody chooses to have a single point of failure on purpose. It happens out of convenience: it's faster to approve a login with a phone notification than to pull out a physical key, and it's more convenient to have your password manager, your email and your bank on the same device you always carry.

The problem shows up when those conveniences chain together. If your password manager asks for a code that only reaches your phone, and you only ever open your recovery email from that same phone, you've created something even tighter: a circular dependency, where each piece needs the other to open.

There's a difference between having a single point of failure and not knowing you have one. Many people, on hearing this, say they "have a backup" or "could call the bank." But the backup is usually on the phone itself, and calling the bank first requires knowing the number and having another phone on hand. A single point of failure isn't solved by good intentions: it's solved by checking, before you need it, which spare parts you actually have outside that one device.

Does it affect you?

Check this

• Does your email open with the same phone you use for verification codes?
• Do you have another device — laptop, tablet — with an open session in your email that doesn't depend on this phone?
• Would you be able to get into your bank or your password manager if this phone disappeared today?
• Do your backup codes exist somewhere other than the phone itself?