Trucking news · industry · Aug 29, 2026 · 2 min read

Motive and Highway Restore ELD Data Flow After API Fight

Motive and Highway agree to resume ELD data access, ending a week-long outage that stalled 12,000+ trucks across the US and Canada.

Reported by Ekjot Singh, founder of EK Dispatch Academy and an active North American motor carrier (EK Freight Lines, operating since 2014). Primary source: FreightWaves.

Ekjot's take — working-carrier commentaryMotive tried to ransom ELD data, and the industry must fight back with open standards.

The ELD data blackout that hit thousands of carriers this week finally ended. After a heated API showdown, Motive and Highway have signed off on a new data‑sharing agreement, restoring the real‑time logs drivers and dispatchers rely on.

What happened

Motive abruptly throttled the API connection that lets Highway pull electronic logging device (ELD) data from Motive‑hosted fleets. The move cut off over 12,000 trucks from transmitting Hours‑of‑Service (HOS) updates to their dispatch teams. Highway’s customers reported missed load confirmations, delayed driver check‑ins, and a surge in compliance alerts. After a week of back‑and‑forth, the two firms released a joint statement: the API limit will be lifted, and a new rate‑limiting protocol will prevent future “over‑use” claims.

Why it matters for dispatchers/drivers

Dispatchers lost visibility into driver HOS, forcing them to guess compliance windows and risk FMCSA violations. Drivers faced unnecessary roadside inspections because they couldn’t prove they were within legal limits. The outage also highlighted a growing dependency on a single‑vendor data pipeline—if one player pulls the plug, the whole operation stalls. For fleets that run mixed‑vendor stacks, the risk is even higher.

My take

Motive’s heavy‑handed API throttling was a power move, not a technical fix. They tried to force carriers into a pricier, proprietary data package, jeopardizing driver safety and compliance. The settlement is a win for the working trucker, but it proves we need open‑standard data agreements, not corporate gatekeeping. EK Dispatch Academy teaches drivers and dispatchers to audit their tech stack—don’t let a single vendor hold your HOS hostage.

What you should do

  • Audit your ELD integration: verify you have at least two independent data paths (e.g., direct carrier portal + third‑party dispatcher).
  • Negotiate service‑level clauses that guarantee **99.9% uptime** for HOS data feeds.
  • Enroll in EK Dispatch Academy’s compliance module to learn how to manually verify logs when APIs fail.

*— Ekjot Singh, Founder, EK Dispatch Academy*

Primary source: FreightWaves

Train as a dispatcher — C$199 / 30 days →