A freight-verification data connection that degraded during the week is flowing at its previous frequency again. Motive and Highway said August 28 that they reached an agreement to restore how often Highway can access Motive customers' electronic-logging-device data when a carrier authorizes that access. The companies said no action is required from carriers or brokers.
The restoration closes the immediate service gap without closing the commercial question behind it. The joint statement says the companies are discussing an update to their existing agreement so it better reflects current uses. It does not disclose pricing, service levels, data volumes, the number of affected users or final contract terms.
Highway's official status history supplies the operating timeline. It identified a load-tracking issue affecting carriers connected through Motive on August 26 and described an ongoing service degradation the next day while monitoring the incident. The companies' later statement addresses access frequency and continuity; it does not turn the episode into a general outage of every Motive or Highway function.
The distinction matters for compliance. Motive's documented ELD-output workflow lets a driver or fleet send the federally required record to enforcement through web services or email. The company-to-company connection in the joint statement concerns authorized data moving into Highway. FreightNews infers that a degraded third-party integration should not be described as proof that a driver's underlying log or official roadside-transfer path failed unless separate evidence shows that.
For carriers, the event makes data authorization an operating control rather than a one-time setup screen. Keep a current list of which platforms may receive vehicle, location and hours data; who approved each connection; how access can be revoked; and which business process depends on it. A carrier should also know whether changing an ELD, telematics provider or broker-verification tool alters tracking, tender eligibility or exception handling before a live load exposes the dependency.
Brokers and shippers need the other half of the map. Identify which carrier-vetting, load-tracking, fraud-control and service-guarantee steps rely on one external feed, then document the timestamp, freshness threshold, fallback method and owner for a degraded connection. A green integration badge is not a continuity plan if no one knows how old the underlying data can become before a load decision changes.
No immediate user action is the companies' stated message, and the restored frequency is the verified current event. The durable test comes next: whether the revised vendor agreement preserves carrier choice, defines acceptable latency, makes data use visible and gives affected operations a clear failure path. Those terms have not been announced, so continuity should be measured in observed data and written controls rather than assumed from the reconciliation headline.