A force majeure clause is a contract term that may excuse or suspend a party’s obligations when a defined event beyond its reasonable control, such as a natural disaster, war, government action or widespread utility failure, prevents it from performing. In IT and telecom contracts it usually sits in the master agreement and mostly protects the provider: if an event the clause covers takes service down, the provider may not be in breach and may not owe the remedies it otherwise would. What counts as force majeure, and what relief follows, depends on the exact wording and on the governing law.
At a glance
- It may excuse or suspend performance during defined events beyond a party’s reasonable control.
- The list of covered events, and any exclusions, is set by the clause and is negotiable.
- It can interact with SLA credits, termination rights and payment obligations, so read them together.
- Many clauses require notice and reasonable efforts to resume, and some allow termination after a long event.
- Interpretation depends on the wording and governing law. This is general information, not legal advice.
What problem it solves
Some events no party can reasonably prevent or plan around. A provider that commits to uptime on a circuit or a cloud service doesn’t want to be in breach, or owe damages, because a hurricane cut a fiber route or a government ordered a shutdown. A force majeure clause allocates that risk in advance so the parties don’t have to argue about it after the event.
For the buyer, the problem is the reverse: an overly broad clause can let a provider escape responsibility for outages that better engineering or diversity would have avoided. The buyer’s job is to keep the clause to genuinely uncontrollable events and make sure there is a way out if a disruption drags on.
How it works
Covered events. Clauses usually list examples, such as natural disasters, fire, flood, war, terrorism, epidemics, government orders, labor disputes and failures of utilities or third-party networks, followed by a general phrase about events beyond reasonable control. The list matters: courts in many jurisdictions read these clauses narrowly, so an event not covered by the words may not qualify.
Exclusions. Buyers often negotiate exclusions, such as events the provider could have avoided with reasonable precautions, failures of the provider’s own subcontractors or suppliers, labor disputes involving the provider’s own staff, and cyberattacks where agreed security measures weren’t followed.
Notice and mitigation. The affected party is often required to notify the other promptly, describe the event and expected duration, and use reasonable efforts to resume performance, for example by invoking its disaster recovery plan.
Effect on obligations. The clause may suspend the affected obligations for the duration, extend deadlines, or excuse them entirely. Payment obligations are often excluded. Whether SLA credits still accrue during the event depends on how the clause and the service level agreement (SLA) are written.
Extended events. Many clauses let one or both parties terminate the affected service if the event continues past a set period, sometimes without a termination charge.
Enforceability and interpretation depend on the governing law, the jurisdiction and the exact wording. Some legal systems also offer separate relief when performance becomes impossible, but that varies and is not a substitute for a clear clause. This is general information, not legal advice; have counsel review the contract.
Tracking outages, credits and contract remedies across carriers is part of telecom expense management; our managed network services page covers how resilient network designs reduce reliance on force majeure in the first place.
When it matters for buyers
- Negotiating the master agreement. The clause is boilerplate in most forms but still negotiable before signing.
- Critical services. For connectivity, hosting or contact-center platforms that the business depends on, a broad clause shifts real risk onto you.
- Third-party dependencies. Many providers rely on upstream carriers, data centers or cloud platforms. Check whether their failures are treated as force majeure.
- After a major outage. When a provider invokes the clause, compare its notice with the clause’s requirements before accepting it.
- Business continuity planning. Your own business continuity and disaster recovery (BCDR) plan should assume the provider may claim relief during regional disasters.
Questions to ask vendors
- Which events does your force majeure clause cover, and is the list exhaustive or illustrative?
- Are failures of your subcontractors, upstream carriers or cloud providers treated as force majeure?
- How are cyberattacks handled, and does relief depend on your meeting agreed security obligations?
- Do SLA credits and fees continue during a force majeure event?
- What notice will you give, and what disaster recovery or diversity measures do you commit to?
- Can we terminate the affected service without charge if the event lasts beyond a set period?
- Is the clause mutual, so it also protects us?
How it differs from a chronic outage clause
A force majeure clause excuses a party when events beyond its control stop it from performing. A chronic outage clause does nearly the opposite for the buyer: it gives the customer an exit when service fails repeatedly and the contract’s defined outage thresholds are met, subject to its exclusions. The two can collide, because outages excused as force majeure may not count toward a chronic outage threshold. Buyers often ask whether excused outages count, and for a separate termination right if a force majeure event goes on too long.