This dashboard combines KeyStone live data covering Jan–Apr 2026 across global Cloud Logistics operations (227,581 load plans) with Navisphere email alerts captured from Apr 23–May 6, 2026 across a focused 14-day C.H. Robinson signal window. Together, the two views show both the structural burden of exception handling in final mile execution and the live downstream manifestations of delay, cancellation, location change, and carrier change pressure.
582,694 exception milestones and 367,214 impacted loads indicate disruption is not episodic — it is embedded in the operating rhythm.
6,239 load plan changes and 3,241 cancellations reveal non-trivial replanning pressure, even before considering downstream alert traffic.
Navisphere alerts accelerate sharply in the back half of the 14-day window, with daily disruption shares repeatedly breaching 70%.
Jan–Apr 2026 global scope. Primary measures: LP creates, changes, cancellations, exception milestones, impacted loads, monthly action rates, carrier/country cancellation patterns, and reroute proxy codes tied to JCAB behavior.
Apr 23–May 6, 2026 email-derived alert stream from C.H. Robinson. Primary measures: daily disruption counts, category mix, delivered overlays, and rapid operational deterioration signals from live notifications.
Use this page to connect upstream planning volatility, midstream exception density, and downstream customer-visible disruptions into one final-mile narrative for Microsoft CSGO stakeholders.
MS requests reroute is the clearest KeyStone-level proxy for JCAB behavior: 1,244 events across 814 loads.
The downstream companion signal adds 631 events across 570 loads, reinforcing that reroute pressure propagates into carrier execution.
Together, C6 + L1 produce 1,875 events across roughly 1,384 loads, forming a targeted reroute evidence cluster tied to final-mile instability.
| Month | Create | Change | Cancel | Cancel % |
|---|
The evidence chain below connects planning actions, exception density, reroute signals, and live disruption alerts into one operating thesis: final-mile volatility is real, measurable, and increasingly visible to customers. MLP is positioned as the mechanism to absorb reroute pressure without forcing binary cancel-and-recreate behavior.
Jan–Apr 2026 planning activity already contains a measurable replanning burden before downstream alert signals are layered on top.
The exception base is too large to be treated as isolated noise; it represents recurring friction across the final-mile operating model.
MS requests reroute is the cleanest direct proxy for the exact behavior this dashboard is trying to evidence.
The source roll-up calls out severe disruption intensity, while the row-level chart still independently validates heavy daily deterioration and sustained pressure.
That concentration points upstream — the system is destabilizing before the shipment fully enters carrier execution, which is exactly where MLP flexibility matters.
The live alert stream demonstrates that pressure is not static; it compounds late in the observed window and becomes increasingly customer-visible.
Instead of cancelling and recreating plans when routes shift, MLP preserves continuity, absorbs reroutes, and reduces unnecessary planning churn.
If reroutes, exception milestones, and live alerts are all rising together, the final-mile design needs structural flexibility — not only faster exception response.
MLP turns disruption handling from a cancel/recreate problem into a path-adjustment problem. That matters because the strongest evidence in this dashboard sits before and between carrier assignment points — exactly where a multi-leg construct can preserve intent while allowing execution to adapt.