A whole job at once, from any manufacturer, mixed together. Drop the files and the tool sorts them into fibers on its own.

Your test files are parsed entirely in your browser and never uploaded. We do log anonymous usage, like file counts, instrument type, and whether the job ran clean, tied to your sign-in email, to improve the tool. The short written review is sent to the server only when you ask for it by pressing Run Analysis. We never receive your trace data, and nothing is sold or shared.

Building and running the analysis summaries takes real work and real money, so access is gated to keep the tool from being abused. You sign in with your email (one tap on a link, no password), which ties usage to a real person and keeps the free version going.

Your address is only used to send that sign-in link. It isn't sold or shared, and we only email you for product feedback or about new tools if you tick the optional opt-in box when you sign in.

It reads the identifiers stored inside each file and the file names, then groups everything for one fiber together: both directions of an OTDR trace, the OLTS reading, and the iOLM result all land on one row. It handles reversed site order (A→B vs B→A), span and direction tags, and files that come from different instruments. If a file lands in the wrong group, you can fix its identifiers from the results without leaving the page.

When both directions of a span are present (A→B and B→A), the tool averages the two to report the true bidirectional loss, and it keeps the reflectance from each end (A and Z) so a bad connector isn't hidden by the averaging. Direction is read from the file's own AB / BA / OE / EO tag first, then the leading site name.

Yes. The Thresholds control above the results sets the mid-span loss, span attenuation, maximum link loss, and minimum ORL used to judge each fiber. Change them and the verdicts recompute immediately, no re-drop needed. If a file carries its own pass/fail limits, those win for that file.

The Trace Analyzer is for one file at a time: drop a single trace to see its waveform, event table, and numbers in detail. Fiber Analysis is for the whole job: drop everything, and get one plain-language repair verdict per fiber plus a table across all of them. Click any fiber in the table to open the underlying trace in the analyzer view.

For each fiber you get a pass/fail call and a short read on what to do next: whether the span is clean, which event or connector is the likely culprit, and roughly where along the fiber to look. The table alongside it shows span length, total loss, worst reflectance, and how many events crossed your thresholds, so you can scan the whole job and jump straight to the fibers that need a truck roll.

Yes. The same whole-job pipeline is available as a REST API: POST a job (many files, or a zip) and get back a per-fiber pass/fail verdict as JSON, no browser needed. It's built for reporting pipelines and automated acceptance testing. This interactive tool stays free; the API is the paid path for programmatic and bulk use. See the developer how-to or the API docs.