layman/terms
Going live

Uptime / downtime / outage

up · tyme · down · tyme · owt · ij

In shortUptime is how much of the time a service is working. Downtime or an outage is when it isn't.

A shop with a sign saying “Closed unexpectedly” loses a day of trade. Websites have days like that too.

A good shop is open when its sign says it will be. Then one morning: blinds down, a note on the door, “Closed unexpectedly.” Customers who came for something go elsewhere.

That’s the difference. Uptime is how much of the time a service is working. Downtime is when it isn’t. An outage is a stretch of unexpected downtime.

The famous nines

Uptime is usually given as a percentage. The nines add up fast:

Why outages happen

A bad deploy, a hardware failure, a sudden rush of visitors, a problem at a cloud provider. Big outages often start with one small mistake that spreads.

What it isn’t

Not all downtime is bad. Planned downtime, announced in advance at a quiet hour, is often needed for maintenance.

Where the comparison breaks down

A shop is either open or shut. A website can be half up: working for some people, slow for others or with one feature broken.

How the words fit together

A quick rollback shortens an outage. Scaling prevents some. A 503 status code often means the site is down.

Good to know

When a big app is down, check a site like downdetector.com or the company's status page before restarting everything you own.

When you'll hear it

“We have 99.9 per cent uptime.” The service works all but about nine hours a year.

“There's an outage.” The service is down right now for many people.

“Planned downtime tonight.” The service will be switched off on purpose for maintenance, at a quiet time.

Say it in a meeting

“How much downtime could we live with in a year? What's the plan when it happens?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Check a website's status code ↗