Single-mode fiber does not have one Ethernet distance limit. The link's reach belongs to a specific transmitter, receiver, signaling standard, and channel specification. The same installed OS2 pair may support a ten-kilometer LR link today and a different reach after the optics change. Buying fiber that says single-mode does not buy every speed at every distance.

For Atlanta and Southeast campuses, the useful question is whether a particular route supports the selected optic with measurable margin. Start with the actual cable length, not straight-line distance between buildings. The OS2 versus OM4 backbone article covers the media choice; this discussion starts after single-mode has been selected.

Use the full transceiver name

LR, ER, DR, and vendor reach labels are not interchangeable. Record the complete part number, Ethernet interface, connector, wavelength arrangement, host compatibility, and required forward error correction. A module that physically fits a QSFP cage can still be unsupported by the switch or incompatible with the remote end.

The following table summarizes common nominal interfaces, not a purchase specification. Verify the selected product's channel budget and platform requirements. Cisco's 40G QSFP data sheet and 100G QSFP data sheet illustrate why similarly named products can have different reach conditions.

InterfaceCommon nominal single-mode reachCheck before specifying
10GBASE-LR10 kmChannel loss and receiver input range
10GBASE-ER40 kmShort-link attenuation and dispersion limits
40GBASE-LR410 kmFour wavelength lanes over a duplex pair
40GBASE-ER440 kmSelected product's channel and receiver requirements
100GBASE-LR410 kmHost support and lane-level optical specifications
100G ER-family productsProduct-dependent; commonly 25–40 kmER-Lite versus full ER4, host FEC, and remote compatibility

The table deliberately avoids treating every 100G module sold with ER in its name as the same forty-kilometer interface. Build the bill of materials from the approved hardware matrix and exact data sheets. Where a manufacturer permits an extended reach only with matching modules or a particular FEC setting, document that condition beside the distance.

Distance and loss are different limits

Attenuation consumes optical power. Connectors, splices, bends, splitters where applicable, and fiber length all contribute. The allowed channel insertion loss is a requirement of the chosen interface. It is not simply the advertised transmitter power minus whichever receiver number happens to be easiest to find.

For an illustrative twenty-kilometer route, suppose the design uses 0.35 dB/km fiber attenuation at the chosen wavelength, four mated connections at 0.4 dB each, and eight splices at 0.1 dB each. The estimated passive loss is 7 + 1.6 + 0.8 = 9.4 dB. Add a separately stated design reserve before comparing against the selected optic's allowed channel loss. These are example inputs, not standard acceptance values.

Two gates: A link must satisfy both the maximum channel specifications and the optical-loss budget. A low-loss cable beyond the optic's rated reach is not automatically an acceptable link.

Use the route schedule to count every cross-connect and enclosure. A clean spreadsheet can hide two uncounted patch panels in a building entrance room. The splice-versus-connector loss article explains why connection architecture belongs in the design calculation. Preserve enough reserve for repair work rather than assuming the initial measurement lasts unchanged forever.

Chromatic dispersion can close the window

Different wavelengths travel through fiber at slightly different speeds. A transmitter has a finite spectral width, so the optical pulse can spread as it travels. At the receiver, enough spreading reduces the ability to distinguish adjacent symbols. Amplifying the received light does not restore the original pulse shape.

The effect depends on fiber characteristics, wavelength, modulation, transmitter design, and receiver processing. Around 1310 nm, conventional G.652 fiber has relatively low chromatic dispersion; at longer wavelengths the accumulated dispersion can become more consequential over extended routes. That does not make one wavelength universally better, because attenuation and the optical interface design also matter.

Moving from 10G to 100G is not a simple tenfold reduction in distance. Some interfaces distribute traffic across multiple wavelengths; others use different modulation or signal processing. Read the interface's dispersion tolerance and reach requirements instead of inferring them from aggregate line rate. On long leased or legacy routes, obtain the fiber characterization required by the selected system.

A short link can overload a long-reach receiver

An ER optic installed across a short campus segment may deliver more power than its receiver permits. Check maximum receive power using maximum launch power and minimum expected channel loss. This is the opposite end of the budget from sensitivity. A successful startup is not evidence that the receiver is operating inside its specified range.

If an attenuator is required, follow the manufacturer's guidance for the model and route. Document its value and location, then measure the resulting receive level. Avoid stacking random attenuators until a warning disappears. Their insertion loss affects the other end of the budget, and the operational record must explain why they are installed.

Also verify connector polish and inspection practice. UPC and APC interfaces should not be casually mixed. A contaminated connector can introduce loss and reflection that make an otherwise adequate route intermittent. Inspection and cleaning are part of the measurement process, not a remedy saved for after the optic is blamed.

Commission the route and the live link

Measure the installed channel with appropriate optical-loss equipment at the specified wavelengths and reference method. Use OTDR traces to locate events and document the route where required. An OTDR event table alone does not replace the channel insertion-loss acceptance test. Save results under the same identifiers used on the panels and drawings.

Then verify both host ports, compatible optics, negotiated speed, FEC configuration where applicable, receive levels, and traffic performance. Monitor errors during a meaningful load test. A link that stays up while accumulating uncorrectable errors has not met the operational objective. Keep corrected-error trends as context rather than judging health from link-up status alone.

For fiber-optic installations across Atlanta and the Southeast, the deliverable should include route measurements and equipment settings. Coordinate structured-cabling pathways so future patching does not quietly change the accepted channel. The final distance limit is the shortest constraint among the rated interface, measured channel, dispersion tolerance, and supported host configuration.

Project documentation and system scope

Review the Atlanta and Southeast service scope alongside the project requirements and acceptance records.