Is Highway down?

We are aware of an issue with tracking loads assigned to ELD-connected carriers using Motive. We are evaluating the impact and will provide further updates as we’re able.

There is an ongoing service degradation between Highway and carriers that are ELD-connected via Motive. Customers and affected carriers are being provided with additional information.

The ongoing service degradation between Highway and carriers that are ELD-connected via Motive has been resolved. Customers and affected carriers have been provided additional information.

We are aware that small number of Microsoft 365 users could still be experiencing delayed delivery or delivery failures for one-time passcodes or other system emails. The underlying issue exists between Microsoft and Highway's independent, third party automated email vendor. Highway has been asked to direct users who are still experiencing this issue to submit a delisting request per the instructions provided in the error message: This can be done by sending an email with a copy of the error message, and the blocked IP address, to "[email protected]". Delisting requests can also be made via the Office 365 Anti-Spam IP Delist Portal at https://sender.office.com/ Unfortunately, the delisting requests must come from directly the intended recipient. Highway is unable to submit delisting requests on behalf of the intended recipient.

Highway is currently monitoring a service-impacting disruption with one of our upstream providers that serves one-time passcode requests. Some Highway users have reported that delivery of one-time passcodes is delayed or failing. This is due to an issue between our upstream provider and the target recipients' service provider. While this issue is not within our control, we are diligently monitoring this incident and will provide subsequent updates as we receive more information. We appreciate your patience.

Highway is continuing to monitor the service disruption with an upstream provider that serves one-time passcodes. Our provider has confirmed that the issue is widespread and affecting deliverability to a large service provider related to many target recipients. Unfortunately, we have not been provided any other meaningful updates. We will communicate more information as soon as it becomes available.

The service provider that was experiencing a disruption to delivery of one-time passcodes has confirmed that the underlying issue has been resolved. We appreciate your patience and understanding.

Some users have reported performance degradation within Highway's broker web application. Our teams are investigating the issue and will provide an update by 09:00 CDT.

Our team has identified the cause of the issue and is continuing to make updates to address stability.

Our engineering teams have implemented a fix and are observing site performance return to normal thresholds. We are continuing to monitor, and we appreciate your patience.

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue.

We are currently observing failures with TIA-integrated and webhook-integrated TMS configurations. These failures are stemming from a change in the size of the Event ID field in each carrier alert being sent from Highway to affected TMS integrations. Immediate developer action is required to update the underlying validation on this field and begin accepting `bigint` values instead of `int` for this field specifically. Once this has been updated, the Highway team can re-send any resulting failures. Please reach out to our Solutions Engineering team with any questions.

The health of all TAI integrations has been restored and failed alerts have been successfully resent. We are continuing to work with proprietary TMS webhook integrations. Please continue to reach out to our Solutions Engineering team with any questions.

Our teams have confirmed that all TAI-integrated configurations are functioning as normal. We are observing similar behavior with McLeod-integrated configurations and are working with McLeod's engineering team to enable `bigint` values instead of `int` for the same affected data field. Please continue reaching out to our Solutions Engineering team with any questions.

We are continuing to work with McLeod's engineering team to implement the acceptance of `bigint` instead of `int` values for the Event ID field in each carrier alert being sent from Highway to McLeod. We appreciate your patience.

We're continuing to work with McLeod to fully resolve the issues impacting our mutual brokers. For some brokers, McLeod has already staged the code fix that can be deployed by performing a Production Application Server Restart. Before performing the restart, it is important that you verify the status of your code fix. You can do this by reaching out to your McLeod Account Representative directly or checking for any notifications from McLeod related to recent releases. Until the code is staged and the restart takes place both real time monitoring alerts from Highway and inbound load lock data to Highway could be impacted.

This incident has been resolved.