Tool
OTDR event table analyser
An OTDR event table lists each connector, splice and anomaly along a fibre with its distance and loss. This analyser checks each event against editable thresholds, flags bends and reflectance failures, and produces a pass/fail handover table with a distance strip.
Paste your event table below. Everything is analysed in your browser from what you type.
Your event table
Event table
Event types: connector, splice, bend, end, reflective, non-reflective.
OTDR analysis
0 fails
3 events, total 1.10 dB. Worst: 0.5 dB at 100 m.
Distance strip
connector at 100 m: 0.5 dB
Connector loss within limits.
splice at 500 m: 0.2 dB
Splice loss within limits.
non-reflective at 750 m: 0.4 dB
Possible bend or macrobend. Non-reflective event above threshold with no expected splice.
Test bidirectionally and average the results. A single-direction splice loss can show as a gain or exaggerated loss.
How this is worked out
Every threshold is on this page and every input is yours to change. An analyser with hidden limits is not a tool.
Connector loss above 0.75 dB and splice loss above 0.3 dB fail. Reflectance above minus 35 dB for UPC or minus 55 dB for APC fails. A non-reflective event above 0.3 dB with no expected splice warns as a possible bend.
Test bidirectionally and average the results. A single-direction splice loss can show as a gain or exaggerated loss.
Questions about OTDR analysis
What is an OTDR event?
An OTDR event is a connector, splice, bend or break along a fibre, shown with its distance and loss. The analyser checks each event against thresholds and flags failures.
What thresholds are used?
Connector loss above 0.75 dB and splice loss above 0.3 dB fail. Reflectance above minus 35 dB for UPC or minus 55 dB for APC fails. All thresholds are editable.
What is a possible bend?
A non-reflective event above 0.3 dB with no expected splice warns as a possible bend or macrobend. Check cable routing and minimum bend radius.
Why test bidirectionally?
A single-direction splice loss can show as a gain or exaggerated loss. Testing both directions and averaging gives the true loss. Always test bidirectionally.
Related tools and services
Do this kind of work? Join the DataOptix engineer network.
Vetted independent engineers. Scoped jobs, no bidding.
Need OTDR testing done?
Tell us the site, the task and the urgency. A coordinator replies within 2 business hours.