- Detected by Pingoru
- May 27, 2026, 12:54 PM UTC
- Resolved
- May 27, 2026, 03:17 PM UTC
- Duration
- 2h 23m
Affected: External APIBroker Web ApplicationCarrierOnboarding
Timeline · 3 updates
-
investigating May 27, 2026, 12:54 PM UTC
Some users have reported performance degradation within Highway's broker web application. Our teams are investigating the issue and will provide an update by 08:30 CDT.
-
monitoring May 27, 2026, 01:25 PM UTC
Highway's infrastructure and engineering teams have identified the issue, implemented a fix and are observing signs of recovery. Our teams will continue to monitor site performance through recovery and provide subsequent updates as needed.
-
resolved May 27, 2026, 03:17 PM UTC
Site performance has remained within acceptable limits since our last update, and we are considering this incident as being resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 04:35 PM UTC
- Resolved
- May 13, 2026, 07:57 PM UTC
- Duration
- 3h 21m
Affected: External APIBroker Web ApplicationCarrierOnboarding
Timeline · 2 updates
-
monitoring May 13, 2026, 04:35 PM UTC
L&I Data for Wednesday, June 13, 2026, has not been provided by the FMCSA. We are aware and monitoring this issue and are working toward resolution
-
resolved May 13, 2026, 07:57 PM UTC
L&I Data for Wednesday, May 13, 2026, has been loaded, and this issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 03:43 PM UTC
- Resolved
- Apr 08, 2026, 11:06 PM UTC
- Duration
- 7h 22m
Affected: External APIBroker Web Application
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 06:14 PM UTC
- Resolved
- Mar 09, 2026, 07:40 PM UTC
- Duration
- 1h 26m
Affected: Onboarding
Timeline · 3 updates
-
investigating Mar 09, 2026, 06:14 PM UTC
We are currently experiencing issues with our carrier login process. We are actively investigating this issue.
-
monitoring Mar 09, 2026, 06:37 PM UTC
We have identified the root cause of the carrier login issue and have implemented a fix. We are currently monitoring the system to ensure stability.
-
resolved Mar 09, 2026, 07:40 PM UTC
The issue impacting the carrier login process has been fully resolved. All systems are operating normally. We appreciate your patience while we worked to restore service.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 08:42 PM UTC
- Resolved
- Feb 24, 2026, 12:00 AM UTC
- Duration
- 3h 18m
Affected: External APIBroker Web Application
Timeline · 4 updates
-
monitoring Feb 23, 2026, 08:42 PM UTC
Due to an active service disruption at Samsara, Load Lock Alerts and Load Lock+ arrival and delivery updates related to carriers connected to Samsara may be impacted. Our engineering teams are monitoring this situation and will ensure these services return to normal once the incident at Samsara is resolved.
-
monitoring Feb 23, 2026, 09:03 PM UTC
Samsara has stated that the issue has been identified and a fix is in process. We will continue to monitor this issue and ensure our services resume operating as normal once the incident at Samsara is resolved.
-
monitoring Feb 23, 2026, 09:51 PM UTC
Samsara has resolved its service disruption. We are seeing all systems fully operational.
-
resolved Feb 24, 2026, 12:00 AM UTC
Following Samsara's confirmation that it's service disruption is resolved, as well continuous monitoring thereafter, we can confirm that all features of Load Lock+ and Load Lock are functioning as expecting. We appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 05:50 PM UTC
- Resolved
- Feb 23, 2026, 07:13 PM UTC
- Duration
- 1h 22m
Affected: Broker Web Application
Timeline · 3 updates
-
investigating Feb 23, 2026, 05:50 PM UTC
We have detected a partial service disruption related to an outage at the upstream intelligence/reporting provider used to display data visualization. We are working closely with this provider to identify and resolve this issue. We will provide subsequent updates at least every half hour.
-
investigating Feb 23, 2026, 06:10 PM UTC
Performance of our data visualizations have returned to normal. We are continuing to work with our upstream intelligence/reporting provider and will continue monitoring performance.
-
resolved Feb 23, 2026, 07:13 PM UTC
Performance of data visualizations continues to remain normal. Additionally, our upstream provider identified and confirmed full resolution the issue. We appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 08:09 PM UTC
- Resolved
- Feb 04, 2026, 10:31 PM UTC
- Duration
- 2h 21m
Affected: Broker Web Application
Timeline · 3 updates
-
monitoring Feb 04, 2026, 08:09 PM UTC
We are experiencing intermittent performance from a third party partner that may affect carrier users logging in. We will provide an update once service is fully restored..
-
monitoring Feb 04, 2026, 09:23 PM UTC
Our partner has indicated they have resolved issues. We are seeing our performance return. We will continue to monitor.
-
resolved Feb 04, 2026, 10:31 PM UTC
All functionality has returned to normal.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 07:02 PM UTC
- Resolved
- Jan 23, 2026, 12:15 PM UTC
- Duration
- 17h 12m
Affected: External API
Timeline · 4 updates
-
investigating Jan 22, 2026, 07:02 PM UTC
We are currently experiencing delays in processing rate confirmations. This is due to an issue with one of our third-party providers. Our team is actively investigating the root cause and working closely with the provider to resolve it as quickly as possible. We will post updates here as more information becomes available. Affected Services: Rate Confirmations Impact: Users may notice longer-than-usual wait times when submitting or retrieving rate confirmations. Other services remain operational.
-
identified Jan 22, 2026, 08:19 PM UTC
We have identified the source of the issue and our teams are working with third parties to resolve.
-
identified Jan 23, 2026, 01:21 AM UTC
We have identified the issue with our third party provider, we are continuing to work with them and exploring additional options to support our customers.
-
resolved Jan 23, 2026, 02:22 PM UTC
We are happy to report that the issue causing delays with rate confirmation emails has now been fully resolved, and normal processing and delivery have been restored. The root cause was identified as a major email reputation and blocklist service inadvertently marking certain outbound emails from our email provider as spam. This led to temporary delivery issues and processing backlogs for confirmations. Our team worked quickly to address the underlying filtering problem in coordination with the involved services, ensuring clean delivery resumed. As an added safeguard, we have implemented a secondary email delivery pathway we can leverage in the event we see the problem in the future.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 03:42 PM UTC
- Resolved
- Jan 15, 2026, 07:03 PM UTC
- Duration
- 3h 20m
Affected: External APIBroker Web Application
Timeline · 6 updates
-
investigating Jan 15, 2026, 03:42 PM UTC
We are currently experiencing degraded performance across multiple services. We are investigating and will update this status when more information is available. Next update in 30 minutes.
-
investigating Jan 15, 2026, 04:15 PM UTC
Still under investigation. Still experiencing service degradation. Next update in 30 minutes.
-
investigating Jan 15, 2026, 04:43 PM UTC
Still under investigation. Still experiencing service degradation. Next update in 30 minutes.
-
identified Jan 15, 2026, 05:09 PM UTC
Issue has been identified and we are seeing signs of recovery. Next update in 30 minutes.
-
monitoring Jan 15, 2026, 05:28 PM UTC
The issue has been resolved. We are continuing to monitor the situation. Site performance is returning to normal.
-
resolved Jan 15, 2026, 07:03 PM UTC
This incident has been resolved and all services are operational.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 08:03 PM UTC
- Resolved
- Jan 09, 2026, 09:36 PM UTC
- Duration
- 1h 32m
Timeline · 4 updates
-
investigating Jan 09, 2026, 08:03 PM UTC
Highway's upstream customer engagement provider, which we use for phone and email support, is experiencing a service disruption. We are working with the provider to resolve the issue as soon as we can, and we appreciate your patience. We'll provide an update when we have more information.
-
investigating Jan 09, 2026, 08:32 PM UTC
Due to a disruption with an upstream provider, our phone and email support systems are currently unavailable. We are awaiting a resolution from the provider and appreciate your patience. Next update in 30 minutes.
-
monitoring Jan 09, 2026, 09:01 PM UTC
We are seeing signs of recovery with our upstream provider, and some support functionality has been restored. We are continuing to monitor the situation closely while the provider works toward a full resolution. We appreciate your patience and will provide another update in 30 minutes.
-
resolved Jan 09, 2026, 09:36 PM UTC
Our upstream provider has confirmed that service is now restored. We appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 04:14 PM UTC
- Resolved
- Dec 01, 2025, 05:17 PM UTC
- Duration
- 1h 3m
Affected: External APIBroker Web Application
Timeline · 3 updates
-
investigating Dec 01, 2025, 04:14 PM UTC
We are currently experiencing increased latency and are actively working the issue.
-
monitoring Dec 01, 2025, 04:28 PM UTC
The situation appears to be resolved. We will continue monitoring the situation.
-
resolved Dec 01, 2025, 05:17 PM UTC
Situation resolved. All services operating normally.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 02:07 PM UTC
- Resolved
- Nov 18, 2025, 05:07 PM UTC
- Duration
- 2h 59m
Affected: Broker Web Application
Timeline · 3 updates
-
monitoring Nov 18, 2025, 02:07 PM UTC
We are aware of a major global outage affecting Cloudflare services that began at approximately 18:36 UTC on November 18, 2025. At this time: - Our own infrastructure and internal systems remain fully operational. - Some third-party providers and customer-facing services that rely on Cloudflare may experience degraded performance or intermittent errors. We are actively monitoring the situation and are in contact with affected partners. We will provide updates here as soon as we observe any direct impact to our platform or when the situation is resolved. Current Cloudflare status: https://www.cloudflarestatus.com/ We appreciate your patience and will keep you informed.
-
monitoring Nov 18, 2025, 02:29 PM UTC
We are aware of an ongoing outage affecting Twilio services, including authentication and login functionality, which began at approximately 05:19 PST on November 18, 2025. At this time: - Our own infrastructure and internal systems remain fully operational. - New logins are unavailable for customers who are currently logged out, as they rely on Twilio services. Existing sessions are unaffected. We are actively monitoring the situation. We will provide updates here as soon as we observe any changes to our platform or when the issue is resolved. Current Twilio status: https://status.twilio.com/ We appreciate your patience and will keep you informed.
-
resolved Nov 18, 2025, 05:07 PM UTC
The global Cloudflare outage has been fully resolved as of 20:47 UTC on November 18, 2025. All downstream impacts to our partners and third-party providers have cleared. Our systems are operating normally, and we no longer observe any related issues. We will continue monitoring closely to ensure continued stability. If you’re still experiencing problems, please reach out to our Customer Success team for assistance.
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 03:53 PM UTC
- Resolved
- Nov 10, 2025, 08:03 PM UTC
- Duration
- 4h 10m
Affected: External APIBroker Web Application
Timeline · 3 updates
-
investigating Nov 10, 2025, 03:53 PM UTC
We are currently experiencing some slowness on the Monitor API. We are researching the issue and will update in 30 minutes or as new information becomes available.
-
investigating Nov 10, 2025, 04:17 PM UTC
We have located and resolved the issue. We are continuing to monitor the situation.
-
resolved Nov 10, 2025, 08:03 PM UTC
We believe the problem has been fully resolved with the fix deployed and systems stable. If you're still experiencing any problems, please reach out to our Customer Success team for immediate assistance. Thank you for your patience — we’re here to help.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 04:44 PM UTC
- Resolved
- Nov 06, 2025, 11:24 PM UTC
- Duration
- 6h 40m
Affected: External APIBroker Web Application
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 01:48 PM UTC
- Resolved
- Nov 05, 2025, 02:46 PM UTC
- Duration
- 58m
Affected: External APIBroker Web Application
Timeline · 5 updates
-
investigating Nov 05, 2025, 01:48 PM UTC
Users are experiencing long loading times across the application. Our engineering and infrastructure teams are actively investigating the root cause. We’ll provide updates every 30 minutes or as new information becomes available.
-
identified Nov 05, 2025, 02:03 PM UTC
We have identified the cause of the slowness. We are still actively working to resolve this issue. We’ll provide updates every 30 minutes or as new information becomes available.
-
identified Nov 05, 2025, 02:07 PM UTC
We have brought the site performance back to the expected level. Our team is continuing to monitor and improve the situation.
-
monitoring Nov 05, 2025, 02:21 PM UTC
We have implemented some improvements and continue to monitor the site health
-
resolved Nov 05, 2025, 02:46 PM UTC
The site has remained fully operational since our fix. Our teams reacted quickly to respond to the issue and we believe the issue is resolved. If you notice any problems please reach out to our customer success team.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 12:51 PM UTC
- Resolved
- Nov 05, 2025, 05:38 PM UTC
- Duration
- 4h 47m
Affected: External APIBroker Web Application
Timeline · 2 updates
-
investigating Nov 05, 2025, 12:51 PM UTC
Starting yesterday, we began to see updates on SAFER and other FMCSA data endpoints that appear to be inaccurately portraying the DOT status of a carrier. The FMCSA L&I database and portal seems to be unaffected at this time. We have put preventative measures in place to prevent invalid updates impacting a carrier's status in Highway. Example DOT numbers that show an Inactive status in SAFER but appear to be active in L&I. We have contacted the FMCSA for an update. Selected list of impacted DOT numbers: 3951719 3325099 3415623 3492559 3548499
-
resolved Nov 05, 2025, 05:38 PM UTC
The FMCSA has confirmed that a recent change was made to how DOT numbers are managed following lapsed biennial MCS-150 updates. The new process now automatically sets a DOT number to Inactive within 60–90 days of a missed filing, per the regulation, rather than waiting up to 14 months. This change affects how certain carriers’ DOT statuses appear in public FMCSA data, such as SAFER. We will explore opportunities in the future to proactively alert you of a carrier's missed filing and impending Inactive status. Highway’s carrier status data is fully up to date. For questions or concerns about a particular carrier's DOT status, please contact [email protected] for help. (edited)
Read the full incident report →
- Detected by Pingoru
- Oct 31, 2025, 01:33 PM UTC
- Resolved
- Oct 31, 2025, 03:02 PM UTC
- Duration
- 1h 29m
Affected: Broker Web Application
Timeline · 5 updates
-
investigating Oct 31, 2025, 01:33 PM UTC
We have begun investigating reports of delays and errors in rate confirmation processing. Affected users may experience issues with generating, sending, or receiving confirmations via email, portal, or API. Our engineering team is actively diagnosing the root cause and working to restore full functionality. We’ll post updates here every 30 minutes or as new information becomes available.
-
investigating Oct 31, 2025, 01:58 PM UTC
We have identified the issue affecting rate confirmation processing. Our team is actively working to resolve it and restore normal service. We appreciate your patience—fix is in progress.
-
investigating Oct 31, 2025, 02:43 PM UTC
We’ve successfully deployed a fix for the Secure Rate Confirmation Delivery The team is actively monitoring key systems and metrics to confirm full stability. No further issues have been observed so far. We’ll provide another update in 30 minutes or sooner if needed.
-
monitoring Oct 31, 2025, 02:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 31, 2025, 03:02 PM UTC
We believe the problem has been fully resolved with the fix deployed and systems stable. If you're still experiencing any problems, please reach out to our Customer Success team for immediate assistance. Thank you for your patience — we’re here to help.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 11:13 AM UTC
- Resolved
- Oct 20, 2025, 09:44 PM UTC
- Duration
- 10h 31m
Affected: External API
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2025, 05:50 PM UTC
- Resolved
- Sep 11, 2025, 09:09 PM UTC
- Duration
- 3h 19m
Affected: External API
Timeline · 4 updates
-
investigating Sep 11, 2025, 05:50 PM UTC
Significant latency observed with external webhooks and API calls. Currently investigating.
-
investigating Sep 11, 2025, 07:13 PM UTC
We have discovered the issue. We are deploying a fix and are monitoring the situation.
-
investigating Sep 11, 2025, 08:00 PM UTC
All APIs have returned to a healthy and functional state. We will continue to monitor though believe the issue is resolved.
-
resolved Sep 11, 2025, 09:09 PM UTC
The incident has been resolved and all services are operational.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 01:02 PM UTC
- Resolved
- Aug 27, 2025, 12:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 28, 2025, 01:02 PM UTC
Between approximately 7:30 AM CT and 8:50 AM CT this morning, Highway experienced a period of elevated latency that may have impacted system response times. After system performance was restored, an investigation was started to determine the root cause. We determined that internal processes had changed causing an unexpected spike in utilization.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 10:25 PM UTC
- Resolved
- Aug 04, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 05, 2025, 10:25 PM UTC
After a recent feature launch, our production environment experienced elevated response times from approximately 8-10am on Monday 8/4. During this time, some end-users saw noticeably slower page loads and occasional time-outs. No data integrity or security issues were observed. The slowdown was traced to an inefficient database query executed by the new functionality. Performance returned to normal after performing a manual update to our internal feature settings and did not require a redeployment of the application. A fix for the inefficient query was committed and deployed the evening of 8/4.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2025, 04:43 PM UTC
- Resolved
- Aug 05, 2025, 10:09 PM UTC
- Duration
- 41d 5h
Affected: External APIBroker Web Application
Timeline · 2 updates
-
investigating Jun 25, 2025, 04:43 PM UTC
We have observed consistent delays this week in the dissemination of the FMCSA's daily L&I data files. Historically, daily L&I data is released from the FMCSA by 7:30am CT and promptly ingested by our system shortly thereafter. This week, we have observed delays ranging from 1-5 hours. We are in contact with FMCSA personnel regarding a resolution and have just now been informed that today's data will be distributed shortly.
-
resolved Aug 05, 2025, 10:09 PM UTC
FMCSA L&I data release schedule has returned to normal.
Read the full incident report →