Fiber Propagation Delay Calculator

July 2, 2026

Fiber Propagation Delay Calculator

Estimate one-way fiber latency, round-trip delay, effective optical path length, and delay per kilometer from refractive index, velocity factor, slack, and route factors.

📌Named fiber link presets
🔧Fiber route inputs
Use mapped cable length where possible, not straight-line distance.
Profiles load typical group index values for quick estimates.
Velocity factor equals signal speed divided by vacuum light speed.
Used for the report label and fiber type comparison.
Typical silica fiber is around 1.468 at telecom wavelengths.
Use 0.67 to 0.69 for many fiber planning checks.
Patch loops, service coils, and tray slack still add propagation time.
Percent added for non-straight routing, risers, trays, and duct path.
Each splice can include a small allowance for closure loops.
Keep this at zero when your route length already includes closure loops.
Optional one-way transceiver, PHY, retimer, or mux latency in microseconds.
Optional RTT budget in milliseconds for margin checking.
One-way propagation
0.162
microseconds through fiber
Round-trip time
0.324
microseconds fiber RTT
Effective optical path
32.9
meters after route factors
Velocity factor
0.681
203,000 km/s signal speed
Fiber propagation delay is usually the floor; switches, optics, queues, and protocol processing add more.
📊Fiber delay spec grid
4.90
us per km OS2 estimate
204k
km/s at VF 0.681
0.98
ms RTT for 100 km
2x
one-way delay for RTT
📘Fiber type and wavelength reference
Fiber profile Wavelength Typical group index Approx delay
OS2 singlemode1310 nm1.46774.90 us/km
OS2 singlemode1550 nm1.46824.90 us/km
OM3 multimode850 nm1.48204.94 us/km
OM4 multimode850 nm1.48154.94 us/km
Bend-insensitive SMF1550 nm1.46804.90 us/km
Plastic optical fiber650 nm1.49004.97 us/km
🗺Common fiber link presets
Scenario Nominal length Fiber type Planning note
Rack patch OS230 mOS2 1310 nmPatch slack dominates the small delay.
Room OM4 trunk75 mOM4 850 nmGood for short multimode switch uplinks.
House backbone120 mOS2 1310 nmSmall RTT, but include tray and wall slack.
Campus OS22.5 kmOS2 1550 nmRouting factor matters more than patch cords.
Regional WAN85 kmOS2 1550 nmFiber path sets a visible latency floor.
⏱Delay budget examples
Effective length One-way OS2 Fiber RTT Typical use
10 m0.049 us0.098 usSame rack or adjacent rack
100 m0.49 us0.98 usHome, lab, or small building
1 km4.90 us9.79 usCampus or neighborhood run
10 km49.0 us98.0 usMetro access path
100 km0.49 ms0.98 msRegional fiber span
🧮Standards and conversion table
Reference Value Meaning Calculator use
Speed of light299,792,458 m/sVacuum reference speedMultiplied by velocity factor
Velocity factor1 / group indexFraction of vacuum speedSets propagation speed
Route factor0 to 80 percentExtra path for ducts and risersAdded to base cable length
Patch slackPer endService loops and patch coilsAdded twice by default
RTT2 x one-wayFiber-only round tripCompared with budget
💡Fiber delay planning tips
Measure the cable path: fiber delay follows the glass route through risers, trays, closures, and patch panels. A map distance can understate latency on campus and metro paths.
Separate propagation from equipment: this calculator can include a one-way optics allowance, but switch buffering, serialization, forward error correction, and queuing should be budgeted separately.

The spreadsheet reads like a dream. The ping from Chicago to New York is low; the database in one city speak fluently to the server in the other. Throughput is high, so you deploy application with confidence. But as number of users scales up, you realize there’s a problem. Not with bandwidth. With light speed. Or should I say the lack of it?

Fiber propagation delay slow down every photon that gets trapped in silica glass. This delay is hard floor on network latency and no amount of protocol optimization or buffering can erase it. When you understand this physics constraint, you’re able to design for performance with precision, not guesswork.

Understanding Fiber Delay

The calculator above will do the math for you. But knowing how numbers work is more valuable then the number itself. Most planners model fiber as a straight line between two points where distance equals travel time. In the real world, it’s never a straight shot. Route factors include tray meander, duct bend and riser climb. And there is patch slack in coils at each termination point. It’s not just an inventory thing; it makes the delay much worse. On a floor plan, that thirty-meter patch cord may appear to be short in a rack, but once you add in connector panels and service loop, the optical path can get much longer. All of that additional glass add microseconds that compound over large networks.

And that brings us to the invisible governor: refractive index. This tell us how much light slows down compared to vacuum speed. At normal telecom wavelengths, single mode fiber (e.g., OS2) tend to be somewhere around 1.468. Some multimodes may be higher, thus pushing delay up slightly. The tool will make this conversion for you from refractive index to velocity factor or vice versa, whichever you prefer.

Velocity factor is just a number representing how many times faster than the speed of light your signal is traveling, if only it were. See a 0.68? Well then your signal are moving along at approximately six-eighty percent of theoretical top speed. Not a flaw. Not a problem. Just material science. Light interacts with structure and mass. And silica glass does have some structure and mass. This is spelled out on the page with a handy table of reference material for common fiber types and their wavelength ranges.

For common single-mode (OS2) fiber at two popular bands, 1310 nanometers and 1550 nanometers, the delay are nearly identical. Latency budget-wise this difference is negligible although loss of power differs between bands. That’s not so much the case for plastic optical fiber. Its higher refractive index (around 1.49) cause slightly increased delay per kilometer. At short range (say audio link or home automation) that fraction of a microsecond won’t make any difference. Every nanosecond makes a difference when you’re doing something like distributed database consistency checks or high frequency trading.

Fiber latency and network lag gets confused all of the time. They’re different things. Fiber latency is purely a function off physics. It’s the time it takes for that first photon to go from point A to point B. That’s called propagation delay. Other factors like queueing delay, packet serialization, protocol overhead, switch processing… All of those adds up to what we call network lag. The fiber portion of the calculator removes all of that so you can actualy see the baseline.

If you find that the actual round-trip time you measure is much larger than this number, you have a pretty good idea where the issue lies. It isn’t on the glass; it’s either an issue with the software stack or the electronics. Always allow for the unknown when building a metro loop or campus backbone. Closures bulge with extra fiber needed for maintenance. Ducts move around. That service loop is just dragging down your latency budget. You can enter number of splices in the tool as well as how much slack allowance per splice. Do so. Designing for a marginally longer path beats finding out at commissioning that your route factor was too optimistic. Go conservative now, save some headaches later.

You should of gone conservative from the start. Finally, remember that while light travels quickly, it doesn’t travel instantly. The difference between amateur installs and professional engineering is understanding the physics of fiber optics in a microsecond-driven world where competitive advantage hinges on microseconds. There’s no cheating the speed of light; however, there are ways to plan for it. When you understand exactly what your cable plant adds by way of delay, you’re able to make educated hardware-placement and layout decisions. This transforms an abstract constraint into a manageable variable. That kind of clarity is worth its weight in gold come go-livig day.

Fiber Propagation Delay Calculator

Related posts

Leave a Comment