Business downtime is any period when work stops or falls short of what the firm intended, and the causes of business downtime reach well past the server room into the building, the power supply, suppliers and people. Unplanned downtime is the stoppage nobody scheduled, and business interruption is the effect on the business when a disruption stops work. This article sorts the causes by what stops the work, then shows who in the firm can answer for each one. Our Maintain Business Continuity use case covers the wider help.
Last reviewed 2026-11-02 by Manish Sharma.
Causes of Business Downtime: Planned, Unplanned and What Counts
These are working definitions used in this article, not a standard. Downtime is any period when work stops or falls short of what the firm intended, in full or in part. Planned downtime is a stoppage the firm schedules and announces, such as a maintenance window. Unplanned downtime, in contrast, arrives without notice, and it is the subject here.
Partial and intermittent stoppages also count. A system that answers slowly, or a site that works for some staff and not others, still stops work.
In this article, business interruption means the effect on the business when a disruption stops work. Ready.gov, a US Department of Homeland Security site, says on its Ready.gov business impact analysis page, last updated 25 March 2026, that a business impact analysis predicts the consequences of a disruption to a business. Signisys defines the term business interruption here, not that page.
Planned downtime is outside this article. However, one exception applies: a change that goes wrong inside a planned window becomes unplanned downtime.
Causes of Business Downtime, Sorted by What Stops the Work
There are six groups, and one event can sit in two of them. For example, a power cut that also corrupts open files is a power cause and a data cause. The causes of business downtime on Ready.gov’s list of disruption scenarios are building damage, equipment breakdown, restricted site access, supplier or transport failure, utility outage and damage to IT. Groups 1 to 4 and 6 follow that list. Meanwhile, group 5, people, comes from Signisys’ own description of how firms organise work.
Causes of Business Downtime, Group 1: Place
The place where people work becomes unusable or unreachable. Ready.gov lists physical damage to a building and restricted access to a site or building. For example, a flooded office and a road closure that keeps staff out both belong here. Neither ranks above the other. The decision behind this group is where else the work could happen, and who decides to move.
Causes of Business Downtime, Group 2: Power and Utilities
An electrical or water outage can stop work even when every device is healthy. Ready.gov names utility outage as a scenario. For an office that works through the internet, Signisys treats the internet link as a utility too.
Ready.gov also says the timing and duration of an event can have a significant bearing on the loss. Its own example is a power outage lasting a few minutes, which it calls a minor inconvenience for most businesses, against one lasting hours, which could bring significant losses. Check your own site’s record of unplanned downtime from power and link failures instead of relying on a general figure. Then list what runs on a UPS (a battery that carries equipment through a short outage) or a generator, and for how long.
Causes of Business Downtime, Group 3: Equipment
Ready.gov lists damage to or breakdown of machinery, systems or equipment. For example, an office may have laptops, switches, routers and printers. In a plant or shop, examples also include production lines and point-of-sale machines. One useful lens, in Signisys’ view, is the single item whose failure stops a function.
Causes of Business Downtime, Group 4: Suppliers and Dependencies
Ready.gov lists interruption of the supply chain, including supplier failure and transport disruption. Signisys extends the same idea to cloud, software and internet providers. An outage at a provider sits outside the firm’s control, but it can still stop the firm’s work. For a hypothetical Dubai trading firm, a delayed shipment and a payment gateway outage are the same kind of cause: a function waits on someone else.
Causes of Business Downtime, Group 5: People and Handoffs
This group is Signisys’ description of how firms organise work, not a statistic. For example, the only person who knows how a task runs may be away. Likewise, ownership of a system may be unclear. A handoff between shifts or teams may sit in someone’s head instead of in writing. A change made in a hurry can also stop work, and the team then needs to know who may call a halt and switch to a fallback.
Causes of Business Downtime, Group 6: Systems and Data
Ready.gov lists damage to, loss or corruption of IT, including voice and data communications, servers, computers, operating systems, applications and data. Cyber incidents also belong here. An attack can exhaust capacity so that real users get no service; the DDoS attack entry explains how. Ransomware can lock the files people need and cause unplanned downtime, and what to do in the first hour of an attack has the response steps.
Key Takeaway Work can stop wherever it depends on something, including places far from the server room.
Application-level causes and early warning signs have their own post, on what can take a single application down. This article does not repeat that list, although a few causes, such as changes that go wrong and failing dependencies, appear in both.
Why the Stoppage Lasts Longer Than the Trigger
The trigger starts the stoppage, but the time to find it, decide who acts and bring work back is part of it. In between, someone has to notice, work out what failed and restore the service.
Ready.gov makes a related point about timing: when an event happens and how long it lasts can have a significant bearing on the loss. In Signisys’ working view, unplanned downtime has two parts, the trigger and the delay that follows it. The length of that delay can shape how large a business interruption becomes.
A stoppage can have more than one contributor; the useful question afterwards is which factor added time. A missing contact number, an unclear owner or a spare nobody could find can each add time without causing the original fault.
Key Takeaway The trigger starts a stoppage, and the time to notice, decide and restore keeps it going.
What to write into a plan so that delay is shorter belongs to a separate article on building a plan. This one only names the cause.
Causes of Business Downtime at a Glance: Cause, Who Can Answer, First Question
The table below gives a role and a first question for each cause, so a business interruption can start with the right conversation. A role is a starting point; firms assign these jobs differently. During an unplanned downtime, the first question goes to the person in the middle column.
| Cause of business downtime | Who can answer | First question |
|---|---|---|
| Building damage or no site access | The facilities or office manager answers for the site. | Where else could the work be done, and who may decide to move? |
| Electrical outage | The facilities manager answers, with IT. | Which devices stay up on a UPS or generator, and for how long? |
| Internet link failure | IT answers, or the link provider. | Does the site depend on one link, and what would staff do if it dropped? |
| Equipment breakdown | The owner of the machine or device answers. | Which single item stops a function if it fails, and who can replace it? |
| Supplier or transport failure | Purchasing answers, or the supplier’s account owner. | Which function waits on this supplier, and who holds the contact? |
| Cloud or software provider outage | IT answers, with the contract owner. | Which function runs on this provider, and where does the provider post its status? |
| Key person away or unclear ownership | The function’s manager answers. | Who covers each critical task if the usual person is away? |
| Change that went wrong | The change owner answers. | Who approved the change, and how would the team undo it? |
| Cyber incident | IT answers, or the security lead. | Who may isolate a system, and whom does the firm call first? |
Business Interruption: What a Stoppage Touches
Ready.gov lists possible effects of an interruption to consider, including lost sales and income, delayed sales or income, increased expenses such as overtime, regulatory fines, contractual penalties and customer dissatisfaction or defection. Which of these apply depends on the function that stopped, and a business interruption looks different for each function.
For example, a stopped order desk can delay income, while a stopped production line can also trigger a contractual penalty. Business interruption can reach the customer as well as the ledger, and any of the causes of business downtime above can matter to more than IT.
This article gives no cost figure. Instead, use your own records of lost sales and extra expenses for a stoppage you have had.
Which Causes of Business Downtime Apply to Your Firm
A first pass at which of the six groups apply to your firm needs only a pen and a list of functions.
Write down what the firm depends on, such as taking orders, paying staff or serving customers.
For each function, mark which of the six groups could stop it.
Start the conversation with the owner of the function with the highest number of marks.
Keep the list to one page, with one line for each function.
If two functions tie, the one that tolerates waiting the least goes first, and its owner can say which that is. Ready.gov says a business impact analysis report should put the processes with the greatest operational and financial impact first for restoration. The method for measuring impact belongs to the plan-building article.
What This Article Does Not Cover, and When to Get Help
This article names the causes of business downtime and gives no cost figure. It also leaves out how to build a plan, how to score a plan you already hold, what each of the two disciplines, continuity and disaster recovery, covers, application-level causes, and the loss of business data. Separate articles take each of those.
Bring in outside help as soon as a stoppage hits a regulated business or an attack is under way.
Get outside help when a business interruption hits a regulated business, when an attack is under way, or when a dependency exists that the firm does not see. Signisys provides continuity and managed-cloud services, and the consultation below looks at which functions the firm depends on and where they could stop. It makes no uptime promise and carries no price.
Frequently Asked Questions
What are the main causes of business downtime?
What is the difference between planned and unplanned downtime?
What is business interruption?
Does a power cut count as downtime if the systems stay up?
Who in a firm is responsible for downtime?
Security Insights, Delivered.
Practical, vendor-neutral analysis of threats, tools, and architecture decisions.