Fade Margin Calculator

ByAlex Mercer, MSCS ✓ Verified 📚 201 Calculators Authored

Principal Systems Architect & Network Performance Engineer · M.S. in Computer Science, Certified Kubernetes Administrator (CKA)

📅 Published: Sep 28, 2026

The formula

Margin = RSL − noise − SNRreq − rain; reliability mapped from margin size

What the radio fade margin tells you

How much atmosphere a microwave link can lose before the radios drop to a lower modulation — the availability number ITU-R gives you in dB.

Calculation: Margin = RSL − noise − SNRreq − rain; reliability mapped from margin size. Enter your inputs and every substitution is shown below the result.

Reading the result

Every 4–6 dB of margin buys another “nine” of availability against rain; below 10 dB the link is a fair-weather contract.

Rules of thumb: Backhaul design targets: 20–30 dB in temperate zones, 35+ dB tropical.

Limitations and best practice

Multipath fades in hot climates can exceed rain for sub-6 GHz links — size margins to the ITU climate zone, not the storm you remember.

This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.

Frequently asked questions

Does adaptive modulation replace margin?

It softens fades instead of surviving them, but the SLA is usually written on the MODCAP you hit at the rain peak.

Can more TX power fix a thin margin?

Only a few dB before linearity and regulations bite — antenna gain or a shorter path is the durable answer.

Source & methodology

ITU-R P.530 propagation availability method.

Fade Margin: the number, the method and the caveats

Capital decisions deserve better than a gut feeling — this page gives you the arithmetic to defend one. There are plenty of pages about Fade Margin; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.

Like most useful measures, Fade Margin is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.

In plain terms, Fade Margin answers the question "Fade margin?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Technology & Computing, Networks & Storage is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.

What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here fade margin = 5.0 dB, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Noise floor first, at ≈190.0 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.

Inside the Fade Margin calculation: formula and every input

One formula, published in full: Margin = RSL − noise − SNRreq − rain; reliability mapped from margin size. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.

Received signal level (dBm) (example value -58) is a plain measured quantity — the unit shown in the label is the unit the formula expects. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.

Required SNR at MODCAP (dB) (example value 20) is a quantity rather than a category — precision here is cheap and worth having. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.

Noise floor (dBm) (example value -95) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.

Rain fade depth expected (dB) (example value 12) is a quantity rather than a category — precision here is cheap and worth having. Measure twice and use the unit the label asks for — length terms often scale the result geometrically.

Fade Margin on the example inputs: the complete substitution

The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Received signal level (dBm), Required SNR at MODCAP (dB), Noise floor (dBm), Rain fade depth expected (dB). Run to the end, the fade margin resolves to 5.0 dB — Thin — a storm will drop it on the bands this tool uses.

SNR = RSL − noise = -58 − (-95) = 37.0 dB
Less required 20 dB → 17.0 dB dry margin
Less the 12 dB rain budget = 5.0 dB
Availability class ≈ 98.00 %

Current SNR — 37.0 dB. This is the number experienced users quote when the headline alone would mislead.

Margin before rain — 17.0 dB. Compare it against the main result of 5.0 dB before drawing conclusions.

Projected availability — 98.00 %. This is the number experienced users quote when the headline alone would mislead.

Rain budget that survives (max fade) — 17.0 dB. Compare it against the main result of 5.0 dB before drawing conclusions.

Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.

How far Fade Margin can reasonably move

Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?

Noise floor setting	Fade margin
80 % of the example value	-14.0 dB
90 % of the example value	-4.5 dB
example inputs	5.0 dB
110 % of the example value	14.5 dB
120 % of the example value	24.0 dB

The corridor runs from -14.0 dB to 24.0 dB across that band — which is the range worth planning inside rather than the single 5.0 dB point estimate. Reproduce it in the form above by editing Noise floor alone; the substitution steps will follow your figures exactly.

Sensitivity: which inputs change Fade Margin the most

Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the fade margin. It is the fastest honest answer to “what matters most in Fade Margin?” — and it is specific to these defaults, because sensitivity moves with the starting point.

Noise floor +10 % → Fade Margin = 14.5 dB · −10 % → -4.5 dB (the fade margin shifts ≈190.0 %)
Nudge Received signal level by ±10 % and Fade Margin lands between -0.8 dB and 10.8 dB (sensitivity ≈116.0 %)
Nudge Required SNR at MODCAP by ±10 % and Fade Margin lands between 3.0 dB and 7.0 dB (sensitivity ≈40.0 %)
Nudge Rain fade depth expected by ±10 % and Fade Margin lands between 3.8 dB and 6.2 dB (sensitivity ≈24.0 %)

Noise floor is the dominant lever here: ten percent either way moves the result by about 190.0 %, from -4.5 dB to 14.5 dB. Measure that input from a document rather than from memory, and treat Received signal level as the second priority (≈116.0 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.

Reading the result: bands, zones and thresholds

Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “Thin — a storm will drop it” band, and bands are deliberately wide because real situations overlap. How much of that band is luck? On Noise floor alone ten percent either way covers -4.5 dB to 14.5 dB. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.

The comparison worth making is not with somebody else’s Fade Margin but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.

Common mistakes with Fade Margin (and the fix)

Multipath fades in hot climates can exceed rain for sub-6 GHz links — size margins to the ITU climate zone, not the storm you remember. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.

Confusing a large number with an important one. Fade Margin can be dominated by one input whose absolute value looks unimpressive, which is why this page ranks influence separately from magnitude.

Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Noise floor first, everything else second.

Another is comparing across contexts: a Fade Margin computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.

Before you trust your Fade Margin: a short checklist

Check that every field the formula needs actually arrived from a document, not from recollection.
Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
Check Noise floor before anything else: it is the measured dominant input, ≈190.0 % of Fade Margin per ten percent.
State, in one sentence, which convention each rate, unit or period in the form is using.
Compare the output against one published benchmark or a colleague’s independent estimate.
Run the ±10 % stress on the top two levers and check that your conclusion survives both.

A routine for decision-grade Fade Margin

The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.

Step 1 — gather before you type. Fade Margin depends on received signal level (dbm), required snr at modcap (db), noise floor (dbm), rain fade depth expected (db). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Most surprises in numbers are surprises about inputs, not about formulas.

Step 2 — baseline before exploration. Get one defensible Fade margin on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. If the answer changes your behaviour, it deserves a second run with different assumptions.

Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.

Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. The test of a good estimate is not that it feels right but that it changes what you do.

Step 5 — schedule the next run. In Technology & Computing the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. Estimates improve most when the worst case is written down in ink.

Who actually uses Fade Margin — and when

In Networks & Storage the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. The input you reach for first is usually the one you measured longest ago.

The audience for this page is investors and founders comparing opportunities on equal terms. In professional Networks & Storage practice the pattern is always the same — screen with Fade Margin, then invest slow analysis only in whatever survives the screen. A calculation you cannot explain to somebody else is a calculation you cannot defend.

Treat Fade Margin like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Most surprises in numbers are surprises about inputs, not about formulas.

What the labels on this page mean

Current SNR: 37.0 dB for the Fade Margin worked case; it sits next to the main result because it carries context the headline leaves out.
Margin before rain: 17.0 dB in the default Fade Margin calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
Projected availability: 98.00 % in the default Fade Margin calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
Fade margin: The primary output of this tool: 5.0 dB for the default inputs, computed exactly from Margin = RSL − noise − SNRreq − rain; reliability mapped from margin size.
Worked example: The calculation written out in full so that nothing on this page has to be taken on trust.
Verdict band: The plain-language label — here “Thin — a storm will drop it” — mapping the computed figure onto experience-based ranges for Technology & Computing.
Sensitivity (±10 %): How far the Fade Margin moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.

Where the Fade Margin model comes from

Everything above runs on one stated formula, applied without hidden coefficients: Margin = RSL − noise − SNRreq − rain; reliability mapped from margin size. Source of record: ITU-R P.530 propagation availability method. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.

Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.

After the number: what to do with it

Run the pessimistic case before the optimistic one; an opportunity that survives the pessimistic inputs is the only kind worth pursuing.

Whoever you are (investors and founders comparing opportunities on equal terms), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Technology & Computing, a dated figure is a trend, and an undated one is a rumour.