The bottom line: OM3 MPO cable reach depends on the named Ethernet PHY and the complete transmitter-to-receiver fiber path, not the cable label alone. Published OM3 ranges span 300 m for 10GBASE-SR to 60 m for 800GBASE-SR8. Compare the exact interface and full path, then record Distance Pass, Distance Fail, or Blocked when evidence is incomplete. See the IEEE/TIA multimode interface table and the IEEE 100GBASE-SR4 specification.
Use this guide when an existing OM3 plant is being considered for a named Ethernet interface. The result is a distance decision: Distance Pass, Distance Fail, or Blocked. It is not a cable selection, loss-budget approval, polarity design, BOM release, or supplier approval.
Engineering disclaimer: Published interface reaches are planning references, not a guarantee for an undocumented link. Final design and acceptance depend on the exact optics, complete channel, applicable standards, and project requirements.
Procurement summary: Do not request cable pricing from a speed label such as "100G" or from one trunk length. First record both optic part numbers, the named PHY, the complete path, and evidence for every OM3 segment. If length exceeds the published range, stop and redesign the media or optics. If an input is missing or conflicting, hold the RFQ and assign an evidence owner. A distance pass only opens the next reviews: passive-channel budget, MPO polarity and mapping, cable role and BOM, site requirements, acceptance method, and project-specific commercial terms. Suppliers should receive the same controlled inputs.
Four decisions to retain
- Match the exact PHY, not only the data rate.
- Screen the complete channel, not one trunk segment.
- Treat
Distance Passas a distance result, not a purchase approval. - Hold the RFQ when the optic, route, or installed-grade evidence is unresolved.
Already have both optic part numbers and the complete route length? Run the three-step reach screen and record its status before asking any supplier for a quotation.
On this page
- What OM3 MPO cable identifies
- OM3 reach by Ethernet interface
- Why complete-channel length matters
- Run the three-state reach screen
- Act on the result
- Confirm international project inputs
- Record the reach decision
- Avoid common reach mistakes
- Read the reach FAQs
- Request a BWNFiber review
- Technical references
What OM3 MPO cable identifies
"OM3 MPO cable" combines two separate specifications.
OM3 identifies laser-optimized 50/125 µm multimode fiber with an effective modal bandwidth of 2,000 MHz·km at 850 nm, as shown in this current OM3 fiber specification.
MPO identifies a multi-fiber connector interface. The standalone IEC 61754-7:2008 publication has been replaced by interface-specific parts, so controlled documents should cite the applicable part of the IEC 61754-7 series.
Neither label identifies the Ethernet PHY or proves the channel length, optics, loss budget, polarity, pinning, cassette mapping, or acceptance status.
Aqua is not conclusive grade evidence. OM4 is also commonly supplied in aqua, so use the jacket legend and controlled plant records rather than color alone. See the technical background in this OM3 and OM4 overview.
No single standard answers every design question. Use each reference for its own layer:
| Decision layer | Reference | What it establishes |
|---|---|---|
| Multimode fiber category | IEC 60793-2-10:2019 with Amendment 1:2022 | Defines A1-OM3, A1-OM4, and A1-OM5 fiber categories. It is not an Ethernet reach table. |
| Premises and component cabling | ISO/IEC 11801-1:2017 with Amendment 1:2025 and ANSI/TIA-568.3-E | Supplies the generic cabling or optical component framework when named by the project. It does not approve a transceiver. |
| Ethernet interface | The applicable IEEE 802.3 PHY clause, such as the 100GBASE-SR4 specification or IEEE 802.3df-2024 | Defines the media, lane arrangement, and operating range for the named PHY. |
| Installed MPO inspection and testing | IEC TR 61282-15:2017, IEC 61280-4-5:2020, and ISO/IEC 14763-3:2024 | Covers applicable attenuation, polarity, length, inspection, and test procedures. It does not replace the optic data sheet or project acceptance limits. |
Project documents may name the ANSI/TIA framework, the ISO/IEC 11801 series, or both. Record the exact edition and acceptance method in the design basis. Neither framework changes the operating range of the selected IEEE PHY.
OM3 MPO cable reach by Ethernet interface
Use the exact interface name, not the line rate alone. "100G" can refer to more than one PHY. Those PHYs may use different media, connectors, lane counts, and reaches.
| Ethernet interface | Active fibers | OM3 planning reach | Distance-screen note |
|---|---|---|---|
| 10GBASE-SR | 2 | 300 m | Duplex interface; an MPO structured-cabling plant may aggregate duplex paths, but the end-to-end implementation still needs review. Source |
| 25GBASE-SR | 2 | 70 m | Use the 25GBASE-SR limit rather than carrying over the longer 10GBASE-SR reach. Source |
| 40GBASE-SR4 | 8 | 100 m | Parallel interface using four transmit and four receive fibers. Source |
| 50GBASE-SR | 2 | 70 m | Duplex interface defined with the 50 Gb/s PAM4 generation; confirm that this is the actual endpoint PHY. Source |
| 100GBASE-SR4 | 8 | 70 m | The 100 m value belongs to OM4 for this interface, not OM3. Source |
| 200GBASE-SR4 | 8 | 70 m | Four-lane parallel interface using eight active fibers; do not infer this row from the line rate alone. Source |
| 400GBASE-SR8 | 16 | 70 m | Confirm the exact module interface and complete 16-fiber path. Source |
| 800GBASE-SR8 | 16 | 60 m | IEEE 802.3df is active; the exact module and full channel remain controlling. Source |
IEEE lists 802.3df-2024 as an active standard covering 800 Gb/s Ethernet additions. Each row applies only to the named interface. Other 100G, 400G, or 800G optics may use different media, connectors, or reaches.
Why the reach screen uses complete-channel length
A trunk label shows the length of one component. The optical channel can also include equipment cords, cassettes, adapters, breakouts, and other cable segments. For a distance screen, compare the interface limit with the planned transmitter-to-receiver fiber path, not with one trunk length.
A distance fit leaves the channel budget open. Connector count, component attenuation, cassette paths, optic limits, end-face condition, and project margin still require separate engineering evidence. IEC TR 61282-15 discusses attenuation, polarity, length, and optical return loss considerations for installed MPO cabling; see the IEC report summary.
The acceptance plan should name both the method and the limit. IEC 61280-4-5:2020 addresses attenuation, polarity, and length measurements for installed MPO-terminated cabling using MPO-interface test equipment. ISO/IEC 14763-3:2024 includes MPO cabling, end-to-end light-source and power-meter (LSPM) testing, cleanliness inspection, and measurement uncertainty. An OTDR trace and an end-to-end insertion-loss result answer different questions, so use the method required by the project rather than treating one record as complete acceptance.
If the path fits the distance limit, move to the MPO trunk design and loss-budget guide. Verify its design inputs against the exact optic and controlled component data.
How to run the three-state OM3 MPO reach screen
The screen has three possible results: Distance Pass, Distance Fail, or Blocked.
Step 1: Name the exact interface
Record the PHY from the approved optic data sheet. Use 100GBASE-SR4, for example, rather than 100G. If the part number or PHY is unknown, the screen is Blocked.
Step 2: Compare complete-channel length with the OM3 range
Use the planned transmitter-to-receiver fiber length. If it exceeds the OM3 maximum for the named interface, the result is Distance Fail. A connector marketed as "low loss" cannot turn that result into a pass.
Step 3: Check whether the media and optic evidence exist
Distance is only the first gate. Uncertainty about the installed grade, exact optic, hidden route, or channel evidence keeps the result Blocked even when the planned length fits.
Use the evidence for the question it can answer. One record rarely closes every reach-screen input.
| Evidence item | What it can establish | What it cannot establish by itself | Reach-screen action |
|---|---|---|---|
| Endpoint part numbers and current data sheets | The actual module, named PHY, supported media, and vendor operating conditions | Installed fiber grade, complete route length, or passive-channel acceptance | If either endpoint or PHY is unresolved, record Blocked. |
| Controlled as-built route or complete-path length record | The transmitter-to-receiver path length when the record is current and covers every segment | OM3 grade, insertion loss, polarity, or connector condition | If records conflict or the possible range crosses the PHY limit, record Blocked. |
| Jacket legend plus controlled plant record | The marked grade of identified cable segments | The grade of hidden, replaced, or unlabelled segments | Use the OM3 row only when the complete installed path is accounted for. |
| End-to-end LSPM result | Insertion loss under the documented reference and test setup | Fiber category, route completeness, or transceiver compatibility | Keep loss acceptance separate from the distance result. |
| OTDR trace | Optical length and event information along the tested path | A required end-to-end insertion-loss result, fiber category, or optic approval | Use it to resolve route evidence only as required by the acceptance plan. |
| Aqua color | A visual clue for laser-optimized multimode cabling | A unique OM3 identification, because OM4 may also be aqua | Color alone leaves the media grade Blocked. |
| Scenario | Distance result | Reason |
|---|---|---|
| 100GBASE-SR4 over a planned 80 m OM3 channel | Distance Fail | 80 m exceeds the IEEE 70 m OM3 range for this interface. Source |
| 40GBASE-SR4 over a planned 80 m OM3 channel | Distance Pass | 80 m is within the published 100 m OM3 range; loss, polarity, component, and optic checks remain open. Source |
| 800GBASE-SR8 over a planned 65 m OM3 channel | Distance Fail | 65 m exceeds the published 60 m OM3 range. Source |
| 25GBASE-SR over a planned 60 m OM3 channel | Distance Pass | 60 m is within the published 70 m OM3 range; the exact optic and complete channel still require approval. Source |
| 100GBASE-SR4 with records showing a possible 60 to 75 m OM3 path | Blocked | The route uncertainty crosses the 70 m limit. Confirm the complete path before using either a pass or fail result. Source |
These are standards-based screening examples, not customer deployments or BWNFiber performance claims.
What to do with the result
| Reach result | Procurement action | Supplier-facing next step | Next review |
|---|---|---|---|
Distance Fail | Stop cable selection and pricing for the rejected path. Reassess the optic or media architecture. | Do not request a quotation or sample for the rejected path; redesign first. | Engineering redesign |
Blocked | Assign the missing optic, route, or fiber-grade evidence to a named owner. Hold pricing until the evidence closes. | Request only the missing data sheet or controlled record. Do not compare incomplete quotations. | Evidence closure |
Distance Pass | Continue to channel, polarity, BOM, deployment, and commercial review. Purchase release waits for those approvals. | After downstream approvals, issue the same controlled requirement to each supplier. | Detailed design |
Use the MPO cable-types guide to choose the assembly role. If the approved design terminates in LC or another duplex equipment interface, review the fiber optic patch cord range. The MPO trunk design guide covers fiber-count architecture and channel budget, while the MPO polarity checklist covers lane mapping, pinning, and the controlled BOM.
Installation teams can use the pre-terminated MPO deployment guide for route measurement, pulling, labeling, and receipt acceptance. Use the MPO polarity and loss testing guide when the acceptance plan calls for detailed testing. Move to the MPO cabling hub only after the technical inputs are controlled.
When the controlled BOM is ready, compare like with like. Ask each supplier to identify the configuration-specific drawing or data sheet, any deviation from the request, quotation validity, project-specific lead time, and the sample or test-document scope if applicable. Do not assume that a sample, report, configuration, or schedule is available until the supplier confirms it for the exact product and order. The MPO polarity checklist is the appropriate downstream record for normalizing those responses rather than rebuilding a supplier scorecard on this reach page.
A lower price or shorter proposed lead time cannot make a failed reach valid. Commercial comparison begins only after the technical requirement is the same for every supplier.
What international projects must confirm after the reach screen
The named IEEE PHY reach is not a regional value. Cross-border projects can differ in their governing cabling and fire requirements, environmental exposure, submittal language, acceptance plan, import documents, and packaging instructions. Record the actual tender, site, and authority requirements instead of applying one regional assumption.
ANSI/TIA-568.3-E is an optical fiber cabling component standard, while ISO/IEC 11801-1 supplies generic premises cabling requirements for multi-vendor systems. European projects may also need construction-product documentation under the applicable EU Construction Products Regulation. None of these references authorizes a specific jacket, fire classification, declaration, or certification for an unverified product.
| Project location | Confirm with the project owner | Do not infer from the region alone |
|---|---|---|
| North America | Authority having jurisdiction, project-named TIA and electrical/fire requirements, pathway classification, acceptance method, and submittal language | OFNR, OFNP, listing, or approval status |
| Europe | Project-named ISO/IEC or EN documents, applicable construction-product declarations, pathway/fire requirement, acceptance method, and destination language | That LSZH wording alone satisfies every market requirement |
| Middle East | Client/EPC specification, local fire or civil-defense requirement where applicable, conditioned versus unconditioned routing, storage/install exposure, and document language | One universal Middle East specification or a blanket claim that every applicable IEC requirement is met |
| Southeast Asia | Country and project standard, humidity or condensation exposure, storage/transport conditions, import documentation, and acceptance language | One regional jacket, test, or certification requirement |
| Latin America | Country/tender requirement, Spanish or Portuguese submittals where required, pathway/fire rules, import documents, and local acceptance plan | One Latin America-wide standard or delivery assumption |
| Africa | Country/operator/EPC specification, indoor-outdoor transitions, heat/dust/storage exposure, packaging instructions, inspection documents, and acceptance language | One Africa-wide cable construction, certification, or logistics rule |
Do not estimate delivery from the region name. Record the required-on-site date, destination, Incoterm if applicable, configuration-freeze date, quantity, packaging and label instructions, import documents, inspection hold points, and any partial-shipment or storage constraints. The supplier must confirm a project-specific schedule. If an RFQ includes OEM/ODM or bulk procurement, define the controlled drawing, labeling, quantity, packaging, inspection, and document scope before comparing responses; do not infer that any option is available.
These prompts do not change the reach table. Any outdoor, unconditioned, or harsh-environment segment needs a separate cable-construction and installation review before a supplier request is released.
Record the reach decision
Use a short reach record before opening detailed design or supplier work.
| Reach-screen field | Record |
|---|---|
| Exact optic part number and PHY | Name both endpoints and the approved interface |
| Planned complete-channel length | Transmitter-to-receiver fiber path, not one cable segment |
| Published OM3 range | Value and source for the exact PHY |
| Distance result | Distance Pass, Distance Fail, or Blocked |
| Installed-grade evidence | Jacket legend plus controlled plant record, or unresolved |
| Exact optic/channel evidence | Available, missing, or conflicting |
| Project location and design basis | Country/site, named cabling/fire/acceptance documents, and required submittal language |
| Environmental handoff | Indoor controlled route or any outdoor, unconditioned, storage, transport, heat, humidity, condensation, or dust exposure requiring downstream review |
| Evidence owner and due date | Name who must close each missing optic, route, grade, or channel record |
| Next decision owner | Media/optic redesign, channel-budget review, polarity/BOM review, or commercial inquiry |
Example: a planned 65 m 100GBASE-SR4 OM3 path is inside the IEEE 70 m distance range, so the record can say Distance Pass; it must not say Link Approved until the exact optic and complete channel have passed their separate checks. Source
Common OM3 reach mistakes
| Assumption | Why it fails |
|---|---|
| OM3 always supports 100 m at 40G and 100G | OM3 supports 40GBASE-SR4 to 100 m, but 100GBASE-SR4 to 70 m. Source |
| The trunk label is the channel length | The distance screen needs the full transmitter-to-receiver fiber path. |
| An OM4 patch cord upgrades an OM3 plant | The OM3 segment remains in the channel and still limits the media classification. |
| A low-loss connector extends the standards reach | Lower passive loss may help the channel budget; the published media range stays unchanged. |
| Aqua proves the cable is OM3 | OM4 may also be aqua. Use the jacket legend and controlled records. |
100G is enough to choose a reach row | The data rate alone leaves the PHY unknown. |
| A manufacturable cable length is a supported link reach | Supplier build range is a product fact. Ethernet reach is an interface and channel fact. |
| A distance pass authorizes a purchase | Polarity, pinning, component mapping, loss, jacket requirements, and acceptance remain open. |
OM3 MPO cable reach FAQs
How far can 10GBASE-SR run on OM3?
The published 10GBASE-SR reach is 300 m on OM3. That row applies to the named duplex interface; an MPO structured-cabling path still needs an approved end-to-end architecture and complete-channel review. Source
How far can 25GBASE-SR run on OM3?
The published 25GBASE-SR reach is 70 m on OM3. Use the complete transmitter-to-receiver fiber length and the exact optic rather than carrying forward a 10G distance assumption. Source
How far can 50GBASE-SR run on OM3?
The published 50GBASE-SR reach is 70 m on OM3 and the interface uses two active fibers. Confirm that the endpoints name 50GBASE-SR rather than another 50G PHY. Source
How far can 100GBASE-SR4 run on OM3?
The IEEE operating range is up to 70 m on OM3 for 100GBASE-SR4. The complete channel and exact optic must also meet their requirements. Source
How far can 200GBASE-SR4 run on OM3?
The published 200GBASE-SR4 reach is 70 m on OM3 over eight active fibers. The endpoint interface, MPO path, polarity, and passive-channel evidence remain separate checks. Source
Is 100 m ever a valid OM3 number for an MPO parallel link?
Yes. For 40GBASE-SR4, the published OM3 range is up to 100 m. It is not the OM3 value for 100GBASE-SR4. Source
Does every 100G optic have a 70 m OM3 reach?
No. The 70 m value here belongs to 100GBASE-SR4. A "100G" label alone leaves the PHY, fiber arrangement, connector, and media range unspecified. Confirm the approved optic part number and interface before using a reach row. Source
Can OM3 support 800G?
For the named 800GBASE-SR8 interface, the published OM3 planning reach is 60 m and the active path uses 16 fibers. Other 800G optics may use different interfaces, media, or connectors. Source
Can a low-loss MPO connector extend OM3 beyond the table value?
No. Component loss and media reach are different constraints. Lower connector loss may help the passive-channel budget; the published OM3 operating range stays the same.
Can an OM4 patch cord make an existing OM3 channel reach farther?
No. The OM3 segment remains in the channel, so the path cannot be treated as an all-OM4 channel. Record the mixed media and design to the limiting component.
Is a channel safe if its planned length is just below the maximum?
The distance screen may pass, but that alone is not a link approval. Check the exact optic, every passive component, the full loss budget, and project margin. If those records are missing, mark the result Blocked.
What if the complete OM3 channel is longer than the published reach?
Record Distance Fail for that interface. Reassess the approved optics and media architecture instead of trying to recover the difference with a "low-loss" connector or a shorter patch cord elsewhere in the path.
Does MPO fiber count change the OM3 reach?
The named Ethernet interface defines both its active-fiber arrangement and media range. Extra installed fibers cannot increase that reach, and the physical interface and lane mapping must still match the optic.
Is an aqua cable enough evidence to use the OM3 row?
No. Read the jacket legend and compare it with controlled plant records. If the grade remains uncertain, the reach screen is Blocked.
Request a BWNFiber OM3 reach review
Before asking for a price or assembly drawing, prepare five inputs:
- Exact optic part numbers and the named PHY at both ends.
- Planned complete transmitter-to-receiver fiber length.
- Evidence that the installed segments are OM3.
- Available channel-budget or test records, including any known gaps.
- Project country/site, governing design or acceptance document if known, and any outdoor, unconditioned, storage, or transport exposure that affects downstream cable and packaging review.
Contact us through the MPO cabling hub to request a BWNFiber OM3 MPO cable reach review with those inputs. The requested output should be limited to a reach status, a list of missing evidence, and the appropriate next review. It is not a quotation, sample offer, delivery schedule, compatibility promise, test-report commitment, compliance approval, or order approval.
Technical references
- TIA FOTC: IEEE multimode Ethernet interface table
- IEEE: 100GBASE-SR4 operating range
- IEEE: 50GBASE-SR and 200GBASE-SR4 OM3 reach summary
- TIA FOTC: 200GBASE-SR4 application overview and IEEE clause reference
- IEEE: 400GBASE-SR8 OM3 reach reference
- IEEE: 802.3df-2024 status and scope
- IEEE 802.3: 800GBASE-SR8 OM3 reach reference
- IEC: A1-OM3, A1-OM4, and A1-OM5 fiber categories
- IEC: status of IEC 61754-7:2008 and replacement parts
- IEC: TR 61282-15 installed-MPO testing considerations
- IEC: 61280-4-5 installed MPO attenuation, polarity, and length testing
- ISO/IEC: 14763-3:2024 inspection and testing of installed optical fiber cabling
- ISO/IEC: 11801-1 generic cabling requirements
- TIA: ANSI/TIA-568.3-E optical fiber cabling component standard
- European Commission: Construction Products Regulation overview
