What disruption looks like right now in global freight.
Lane-level disruption themes caught by the FlowSync pipeline in the trailing weeks — what the engine is rerouting, which carriers it's pivoting off, and where the weather is asking the network to absorb a re-plan. No per-shipment data, no customer names — the same view a freight ops lead would get when scoping the engine for their own lanes, with the live numbers below to back it up.
What the pipeline is rerouting right now.
Four lane-level patterns the FlowSync pipeline surfaced this month — each one is the result of a real classification decision, tied back to the method that catches it and the outcome one of our fleets already saw.
Rerouting
When transit-time drift crosses the 15% threshold, the engine ships a scored primary route plus a small set of alternatives, so the ops lead picks a real call rather than a placeholder.
Carrier diversification
Reroutes lean on multi-carrier spot pricing rather than defaulting to the incumbent — the lane gets cheaper and the network less brittle when the original carrier pulls capacity.
Port rotation
When a weather cell parks over a hub, the negotiation step rotates the discharge port rather than waiting the storm out — at the cost of a longer inland leg the engine has already priced.
Weather reroute timing
Active weather alerts no longer trigger a full reroute on contact — the engine scores lead time and only re-plans when the savings beat the operational cost of swapping the booking.
Four signals, one window.
Total disruptions, reroutes generated, average resolution hours, and the most recent anonymized reroutes — all pulled from the production DisruptionEventtable for the 30 days ending now. A zero in any cell is a real zero — the page shows example numbers only when the pipeline has been live but quiet.
Loading…
Loading…
Loading…
Loading…
Every public number here is an aggregate of records in the production DisruptionEventtable — no identifying data is included by design. For how the pipeline scores those events and turns them into reroutes, read the method. When you’re ready to run the engine on your own lanes, start a Pilot with 14 days free, then $350/month; for an outcome closer to what these numbers describe, read the proof from a real fleet.
Same engine, your data.
The aggregates above come from FlowSync’s production routing engine. A Pilot with 14 days free, then $350/month wires the same engine to your real fleet's GPS, carrier, and weather feeds so you can see your own numbers populating this same view.