Practical guide · November 17, 2026
Cyber business interruption: your systems or a supplier’s outage?
First identify whose system stops the work: yours or a supplier's. Then identify the event that caused the disruption and the wording that would need to respond. A dependency outage and a breach of your own network are different situations; neither the word “cyber” nor an interruption lasting several hours establishes coverage.
Locate the system that stops the work
A useful loss description names the business activity, the system it depends on and who operates that system. “We cannot invoice because our office server is unavailable” is more specific than “our IT is down.” So is “we cannot schedule work because a hosted application is unavailable.”
The Travelers CyberRisk coverage specimen, CYB-16001 Rev. 06-20 distinguishes own-system interruption from dependent interruption tied to a defined IT Provider Breach. That definition matters: do not substitute any supplier outage for the defined trigger, or assume this specimen governs your policy.
For your agent discussion, draw a short dependency chain: business activity → application → operator → any other essential service you know about. Mark unknown links. This is a preparation aid, not a technical investigation or an assertion that every dependency is insured.
Separate the cause from the duration
There are two distinct questions: did the event meet the applicable trigger, and what time and loss provisions apply? A long interruption cannot answer the first question by itself. Ask the agent to locate how malicious events, nonmalicious failures and provider disruptions are treated in the offered wording rather than assuming they are interchangeable.
Time provisions also deserve a separate reading. CFC's historical explanation of cyber time retentions, published in 2018, distinguishes a time threshold from how the loss is then measured. Use that distinction as a reading question, not as evidence of a standard number of hours or of CFC's current offered terms.
Ask when the relevant clock starts, what happens before the threshold is reached, and when the measurement period ends. Do not infer a payment by multiplying outage hours by ordinary sales. This article does not calculate insured loss or interpret your accounting provisions.
Walk through a hypothetical supplier outage
Suppose a small service company cannot access its hosted dispatch application. Its staff can still answer calls, but they cannot see the normal job schedule. The supplier says it is investigating; the cause is not yet known.
| Known or proposed fact | Useful next step | Conclusion to avoid |
|---|---|---|
| Hosted application unavailable | Identify the operator and relevant policy definitions | Every hosted service is an eligible provider |
| Cause not yet confirmed | Preserve supplier updates and distinguish facts from speculation | The outage must be a covered attack |
| Some work continues by phone | Record the operational effects and workarounds | All revenue during the period was necessarily lost |
| Access eventually returns | Record timestamps and remaining disruption | Restored access alone settles the entire loss calculation |
These are records to help the conversation and any appropriate investigation. They do not establish that a claim exists or that particular costs are recoverable.
Prepare evidence before and after an interruption
Before an event, keep the important dependencies, response contacts and policy reporting instructions accessible to the people who need them. Ask the agent to explain notification and service-provider arrangements while you are comparing terms, rather than leaving those questions for the first disrupted morning.
If an event occurs, follow the actual reporting instructions and obtain appropriate incident-response help. Keep factual timestamps and cost records without altering evidence or treating speculation as a confirmed cause. This is not a substitute for the policy's requirements or professional incident advice.
Return to the quote-comparison guide to place the relevant trigger, limit and time provisions side by side. Use the coverage overview if the distinction between your loss and someone else's claim is still unclear.
Research basis: a named carrier specimen and historical insurer explanation inspected November 17, 2026. No issued policy, outage investigation or claim determination was reviewed; the supplier situation is hypothetical.