Fax outage: your 24-hour business continuity plan

Short answer: a fax outage is never merely a technical problem — it is first and foremost a problem of proof and deadlines. Three reflexes, in order: (1) document the outage to the minute (screenshots, failure reports, timestamped carrier ticket), because that trail is what will let you invoke a legitimate impediment; (2) switch to a backup channel identified in advance — online fax through another provider, a registered electronic letter compliant with the eIDAS Regulation, submission via a dedicated portal; (3) regularise as soon as service is restored, resending the document with an explicit reference to the first, failed attempt. A document continuity plan fits on a single sheet of A4 and should be tested twice a year. Without one, you'll discover the outage on the day it costs you the most.

Why a fax outage does more damage than an email outage

When the mail server goes down, everyone notices within fifteen minutes and complains loudly. When the fax goes down, nobody says a word — until a correspondent calls three days later to ask why they never received anything.

The difference lies in the nature of the traffic. In organisations that still use it, fax carries the critical residue: prescriptions and discharge summaries sent to healthcare facilities, mandatory reports to a regulator, purchase orders in logistics, filings to a court registry or a bailiff, payment instructions in certain banking workflows. These are low-volume, high-consequence flows. One document in a thousand failing to go out is statistically nothing; legally, it can mean a missed limitation period.

Second peculiarity: fax is asymmetric. You only control half the chain. The machine at the other end may be out of paper, unplugged, misconfigured, or connected to an analogue line that has already been migrated without anyone being told. Your transmission report says "OK" and the document sits in a buffer nobody ever checks.

Third peculiarity, and the most structural one in 2026: the shutdown of the public switched telephone network. Orange has been phasing out the PSTN for several years now, switching off analogue lines geographic batch by geographic batch. Many organisations discover the changeover on the morning the fax machine displays "no dial tone". That isn't a fault, it's a scheduled shutdown — and it cannot be repaired.

The five real causes of unavailability, and what each one implies

Not every outage is handled the same way. Identifying the cause determines both the backup channel and the legal argument.

The "useful remedy" column is the only one that matters on the day. For carrier incidents, remember one practical point: providers' public status pages only keep history for a few days. If you think you may need to prove the incident later, take a dated screenshot the same day. A screenshot taken three weeks later simply won't exist.

On power cuts, the single most cost-effective piece of kit in a continuity plan is probably a properly sized UPS for network equipment: it keeps the router, modem and fax gateway alive through the micro-outages that account for most electrical incidents in urban areas. Thirty minutes of runtime is enough to push an urgent transmission through.

Documenting the outage: the reflex nobody has

This is the heart of the matter, and the part that gets neglected. Under French law, the force majeure principle set out in Article 1218 of the Civil Code requires an event beyond the debtor's control, unforeseeable, and whose effects cannot be avoided by appropriate measures. An isolated fax outage is almost never qualified as force majeure — precisely because appropriate measures exist: another channel. What does carry real weight before a judge, a public health fund or an administrative body assessing a delay is a demonstration of genuine unavailability and of the diligence shown in remedying it.

In practice, your outage file must contain, for each failed transmission:

• The exact time of the first attempt, with the failure report from the fax machine or online fax service (error code, number of attempts, number dialled).
• Proof of the incident: screenshot of the carrier's status page, ticket number, confirmation email from support with its timestamp.
• The record of alternative attempts: phone call to the recipient (with the time and the name of the person you spoke to), fallback email, postal despatch.
• The regularisation: date and time of the successful transmission, with the corresponding confirmation.

These four elements fit into a spreadsheet or into a bound transmission logbook with numbered pages, kept the old-fashioned way at the front desk. Paper has one underrated advantage here: it doesn't depend on the system that has failed. Emergency services, pharmacies and practices that handle incidents well almost all keep a register of this kind.

A word on wording. Never write "fax outage" on its own in official correspondence. Write "unavailability of the fax service on [date] from [time] to [time], carrier incident referenced no. X, transmission attempts logged at [times]". The first phrasing sounds like an excuse; the second sounds like evidence.

Building the backup channel before you need it

A continuity plan that starts with "we'll see on the day" is not a plan. Here is the minimum architecture, valid for a three-person practice as much as for a fifty-strong department.

Level 1 — Online fax as backup for the physical fax

This is the simplest fallback: keep the fax machine for day-to-day use if you're attached to it, but maintain a ready-to-use online fax account, tested, with your correspondents' numbers already stored. Transmissions then travel over infrastructure entirely separate from your local line. A router failure doesn't prevent you from sending via a mobile hotspot. Our complete guide to sending faxes online explains how it works end to end, and the available countries page lets you check coverage for your international recipients in advance — a check to run calmly, never in a crisis.

Level 2 — The legally equivalent channel

For transmissions where proof matters more than speed, the qualified registered electronic letter, governed by the eIDAS Regulation and Article L.100 of the French Postal and Electronic Communications Code, offers a higher evidentiary standard than a fax transmission report. It does require the recipient to accept it, which is far from universal. Our comparison proof of receipt: fax, registered e-letter or email sets out the equivalences.

Level 3 — The deliberately degraded channel

An advance phone call, then hand delivery against signed receipt, or physical filing. It sounds archaic; within a ten-kilometre radius it is often the fastest option, and a signed receipt is worth more than a disputed transmission report.

Level 4 — Hardware independence

A 4G backup connection via a 4G router with SIM card slot lets you run a workstation and an online fax service when the fibre is cut. For organisations with continuous document production, a backup duplex desktop scanner avoids depending on the single multifunction device that, curiously, always breaks down on the day the fax isn't working either.

The first 24 hours: the operational sequence

T+0 to T+15 min — Qualify. Is one recipient failing, or all of them? Test a control number known to work. If it goes through, the problem is at the recipient's end, not yours: call them, and it's usually sorted in two minutes. If it doesn't, the problem is yours or the carrier's.

T+15 to T+45 min — Open a ticket and capture evidence. Call support, note the reference, screenshot the status page. Don't hang up without a ticket number: without it, you have nothing to produce later.

T+45 min to T+2 h — Switch over. Activate the backup channel for urgent transmissions only. Triage: what must go out today, what can wait until tomorrow. A continuity plan isn't meant to sustain 100% of throughput, only the critical flow.

T+2 h to T+8 h — Notify your correspondents. A short message to your regular partners: "our fax line has been unavailable since this morning, please send your documents to [alternative channel] until further notice." This information has legal value: it demonstrates your diligence and prevents a third party from later claiming a transmission was "sent but never received".

T+8 to T+24 h — Decide. If the incident drags on, it's time to consider that this isn't a fault but a signal. Our six-step migration plan will stop you replaying the same scenario in three months' time.

The special case of regulated flows

Some transmissions tolerate no improvisation. Health data transfers fall under the framework set by the French Public Health Code and the guidelines of the Agence du Numérique en Santé: switching in a panic to an unsecured personal email account constitutes a data breach within the meaning of Article 33 of the GDPR, potentially notifiable to the CNIL within 72 hours. The outage excuses nothing here; it actually aggravates the breach, since it reveals the absence of a compliant backup channel. The topic is developed in our article on medical faxing and health data.

The same logic applies to mandatory reports to authorities: a regional health agency, a prefecture or a public prosecutor will not accept a delay justified by a broken fax machine if an online form or a dedicated address was available. The principle is simple: the backup channel for a regulated flow must be as compliant as the primary channel, otherwise it isn't a backup, it's a deferred breach.

For practices bound by professional secrecy, going into degraded mode multiplies exposure risks: printed documents left lying around awaiting manual despatch, transmission from a personal device, poorly controlled bulk sending. A cross-cut document shredder at the workstation and a discipline of immediate filing limit the damage during incident periods.

Testing your plan: two exercises a year, one hour each

An untested continuity plan is an administrative fiction. The exercise takes an hour and is best run on a Tuesday morning in September and a Tuesday morning in March.

1. Unplug the fax line deliberately, or cut the internet connection, without warning the team in advance (but with management's knowledge).
2. Time how long it takes until the first successful transmission via the backup channel. A reasonable target: under thirty minutes.
3. Check that whoever is on duty that day knows where to find the credentials for the backup service. This is where 80% of exercises fail: the account exists, but only one employee knows the password and they're on holiday. A password manager shared at team level solves this better than any written procedure.
4. Review the incident log filled in during the exercise: does it contain the four elements listed above? If not, fix the form, not the people.
5. Archive the exercise report. Should a dispute arise later, proving that you tested your continuity twice a year changes how your diligence is perceived.

Frequently asked questions

Can a fax outage justify a delay in court?

Rarely on its own. The judge will look at whether an alternative channel existed and whether it was used. A documented outage, backed by attempts to transmit by another means within a reasonable time, is on the other hand a serious argument for setting aside a forfeiture or obtaining relief from a missed deadline. Without a record of those attempts, the argument collapses.

My transmission report says "OK" but the recipient received nothing. Who's right?

Both, technically. The report certifies that the negotiation between the two terminals completed normally, not that the document reached anyone's desk. That is precisely the evidentiary limit of fax, detailed in our article on the evidential value of fax. When the stakes are high, always follow up with a confirmation call.

How long should failure reports be kept?

Align them with the retention period of the document transmitted. An isolated failure report is useless; combined with the document and proof of regularisation, it forms a coherent set. The rules on archiving with evidential value are set out in our dedicated guide to archiving faxes for ten years.

Should you keep a physical fax machine as a backup for online fax?

No, in the vast majority of cases. The logic has flipped: today the point of fragility is the analogue line, not the internet connection. A relevant backup in 2026 is a second network access route (4G) and a second service account, not a machine plugged into a network that is being switched off.

What if the outage is at the recipient's end and lasts several days?

Document your attempts, notify them through another channel, and ask them in writing for a substitute address. If the transmission is regulated, check whether the receiving authority offers a submission portal: this is increasingly common and settles the problem for good.

In summary

• A fax outage is first of all a deadline and evidence risk, not an IT incident.
• Document it to the minute: failure report, timestamped carrier ticket, screenshot of the status page, alternative attempts, regularisation.
• Force majeure is almost never a winning plea for a fax: what saves you is demonstrated diligence.
• Prepare three levels of backup — online fax on separate infrastructure, a channel of equivalent evidential value, and a deliberately degraded channel — and test them twice a year.
• For regulated flows (healthcare, mandatory reporting), the backup channel must be as compliant as the primary one: improvising exposes you to a data breach.
• A PSTN shutdown is not a fault: it's the signal to migrate, not to repair.
• The most common point of failure in a continuity plan isn't technical: it's the backup service credentials nobody can find on the day.

For practical questions about sending faxes and number coverage, the FAQ covers the essentials in a few minutes.