Highway Outage History
Highway is up right nowPingoru has recorded 50 incidents for Highway: 40 in the last 12 months and 13 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 8 of 720 (1%) |
| May 2026 | 3 | 6 of 744 (1%) |
| June 2026 | 2 | 5 of 720 (1%) |
| July 2026 | 5 | 51 of 744 (7%) |
| August 2026 | 6 | 391 of 744 (53%) |
| September 2026 | 4 | 37 of 720 (5%) |
| October 2026 | 2 | 20 of 587 (3%) |
Incidents, newest first
Minor January 22, 2026 Rate Confirmation Email Delays 17h 12m External API
Started Jan 22, 2026, 07:02 PM UTC· resolved Jan 23, 2026, 12:15 PM UTC
- 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.
Major January 15, 2026 Degraded Performance Across Services 3h 20m External API, Broker Web Application
Started Jan 15, 2026, 03:42 PM UTC· resolved Jan 15, 2026, 07:03 PM UTC
- 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.
Minor January 9, 2026 Issues with Email and Phone Support 1h 32m
Started Jan 09, 2026, 08:03 PM UTC· resolved Jan 09, 2026, 09:36 PM UTC
- 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.
Minor December 1, 2025 Increased Latency 1h 3m External API, Broker Web Application
Started Dec 01, 2025, 04:14 PM UTC· resolved Dec 01, 2025, 05:17 PM UTC
- 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.
Minor November 18, 2025 Cloudflare outtage 2h 59m Broker Web Application
Started Nov 18, 2025, 02:07 PM UTC· resolved Nov 18, 2025, 05:07 PM UTC
- 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.
Minor November 10, 2025 Monitor API Slowness 4h 10m External API, Broker Web Application
Started Nov 10, 2025, 03:53 PM UTC· resolved Nov 10, 2025, 08:03 PM UTC
- 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.
Minor November 6, 2025 Investigating isue with Connect and ELD endpoints 6h 40m External API, Broker Web Application
Started Nov 06, 2025, 04:44 PM UTC· resolved Nov 06, 2025, 11:24 PM UTC
- investigating Nov 06, 2025, 04:44 PM UTC
Noticing latency and load time issues with some endpoints related to Connect and Carrier Vehicles Area. Will update every 30 minutes or as we find more information
- investigating Nov 06, 2025, 05:13 PM UTC
Deploying a hotfix to correct. Next update in 30 minutes or sooner.
- investigating Nov 06, 2025, 05:48 PM UTC
Hotfix in place. Testing but initial results are promising. Next update in 30 minutes.
- investigating Nov 06, 2025, 06:20 PM UTC
Working through connect and onboarding latency issues. Average latency is currently about 2 hours. Next update in 30 minutes.
- investigating Nov 06, 2025, 06:48 PM UTC
Continuing to investigate the situation. Next update in 30 minutes.
- investigating Nov 06, 2025, 07:12 PM UTC
Average latency now down to about 10 minutes. Continuing to investigate and work the issue. Next update in 30 minutes.
- investigating Nov 06, 2025, 07:43 PM UTC
We believe the situation is resolved. Continuing to monitor as latency improves.
- investigating Nov 06, 2025, 08:12 PM UTC
All systems operational. Continuing heightened monitoring.
- resolved Nov 06, 2025, 11:24 PM UTC
This incident has been resolved.
Minor November 5, 2025 Long loading times 58m External API, Broker Web Application
Started Nov 05, 2025, 01:48 PM UTC· resolved Nov 05, 2025, 02:46 PM UTC
- 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.
Minor November 5, 2025 DOT Status for certain carriers potentially inaccurately reflected in SAFER 4h 47m External API, Broker Web Application
Started Nov 05, 2025, 12:51 PM UTC· resolved Nov 05, 2025, 05:38 PM UTC
- 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)
Minor October 31, 2025 Issue with our Secure Rate Con Delivery. 1h 29m Broker Web Application
Started Oct 31, 2025, 01:33 PM UTC· resolved Oct 31, 2025, 03:02 PM UTC
- 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.
Major October 20, 2025 Impacted by AWS outage 10h 31m External API
Started Oct 20, 2025, 11:13 AM UTC· resolved Oct 20, 2025, 09:44 PM UTC
- identified Oct 20, 2025, 11:13 AM UTC
We are currently seeing issues on our east coast region servers relating to AWS outage https://health.aws.amazon.com/health/status.
- identified Oct 20, 2025, 11:27 AM UTC
AWS services are recovering. All of our systems are fully functional, though some downstream APIs we rely on continue to experience issues.
- identified Oct 20, 2025, 12:56 PM UTC
We are actively monitoring the AWS outage and its impact on our partners. Our systems remain fully operational. However, missing data from our partners' services may result in degraded performance for some clients.
- identified Oct 20, 2025, 04:21 PM UTC
We continue to actively monitor the ongoing AWS outage and its cascading effects on our partners and services. Our core systems remain fully operational, but the disruption in data feeds from partners persists, potentially leading to degraded performance for select clients. AWS is experiencing continued elevated error rates and latencies across multiple services in the US-EAST-1 region (Northern Virginia), stemming from a DNS resolution issue with the DynamoDB API endpoint that began around 3:11 a.m. ET today. This has impacted over 70 services, including EC2 launches, Lambda, SQS, and global features like IAM updates, with partial mitigations in place but full recovery still underway. In response, we are evaluating activation of our Disaster Recovery (DR) plan per our established policies. If these regional issues persist beyond the next hour, we will initiate a controlled failover to our secondary region to minimize any further client impact and restore optimal data synchronization. We appreciate your patience and will provide our next update by 1:30 PM CST today, or sooner if conditions change significantly.
- identified Oct 20, 2025, 06:28 PM UTC
AWS services in the US-EAST-1 region are showing strong signs of recovery following the DNS resolution issue with the DynamoDB API endpoint that began early this morning. Core mitigations have been implemented, with over 33 services—including DynamoDB, SQS, and IAM—now fully operational. While elevated error rates persist for new EC2 instance launches and related services like Lambda and RDS, successful operations are increasing across Availability Zones, and backlog processing (e.g., for EventBridge and CloudTrail) is progressing steadily. Our systems have stabilized in tandem, with data latency improving significantly. We no longer anticipate activating our Disaster Recovery plan at this time, as conditions continue to mend. Some residual latency in partner data feeds and system synchronization may still affect a subset of clients intermittently. Our engineering team is actively addressing these to ensure seamless performance. Thank you for your patience—we're nearly through this. The next update will follow by 9:00 AM PDT today, or earlier if full normalization is confirmed. For immediate concerns, contact our support team
- monitoring Oct 20, 2025, 07:53 PM UTC
We are pleased to report that our systems have recovered from the recent AWS outage in the US-EAST-1 region. All data synchronization processes with our partners are now complete, and latency issues have been fully resolved, restoring seamless performance for all clients. AWS has confirmed that the DNS resolution issue impacting DynamoDB and related services has been mitigated, with all affected services—over 70, including EC2, Lambda, and SQS—now operating normally across all Availability Zones. Our team will continue to monitor the situation closely to ensure ongoing stability. No further disruptions are anticipated. Thank you for your patience and support throughout this event. We will provide a final update by 5:00 PM EDT today, or sooner if any new developments arise.
- resolved Oct 20, 2025, 09:44 PM UTC
Our team has completed monitoring and validated system stability. No additional updates are planned, and normal operations have resumed for all clients. For any further assistance, please contact our support team
Notice September 11, 2025 Service Degraded with Integrations 3h 19m External API
Started Sep 11, 2025, 05:50 PM UTC· resolved Sep 11, 2025, 09:09 PM UTC
- 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.
Minor August 27, 2025 Connected integration delays –
Started Aug 27, 2025, 12:30 PM UTC· resolved Aug 27, 2025, 12:30 PM UTC
- 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.
Minor August 4, 2025 Site Performance Degradation Due to Unoptimized Query –
Started Aug 04, 2025, 01:00 PM UTC· resolved Aug 04, 2025, 01:00 PM UTC
- 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.
Minor June 25, 2025 Delayed Data Ingest: Daily FMCSA L&I Data 41d 5h External API, Broker Web Application
Started Jun 25, 2025, 04:43 PM UTC· resolved Aug 05, 2025, 10:09 PM UTC
- 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.
Minor May 3, 2025 Maintenance still in progress 12h 28m External API, Broker Web Application
Started May 03, 2025, 11:04 AM UTC· resolved May 03, 2025, 11:33 PM UTC
- investigating May 03, 2025, 11:04 AM UTC
Scheduled maintenance is still in progress and taking longer than expected. Application functionality is limited. Thank you for your patience. The next update will be provided within the next 30 minutes.
- investigating May 03, 2025, 11:42 AM UTC
We are continuing to investigate the issue. Next update will be provided in 30 minutes.
- investigating May 03, 2025, 12:46 PM UTC
We have deployed a fix to address the root cause and are still monitoring the issue. We will continue to update as we have more information.
- identified May 03, 2025, 05:31 PM UTC
The issue has been identified and a fix is being implemented.
- resolved May 03, 2025, 11:33 PM UTC
All systems and TMS integrations are back to operational status. We will continue to monitor site performance closely in preparation for our standard volume spikes on Monday morning. Please contact your Customer Success team if you are experiencing any issues.
Notice April 22, 2025 Twilio - SMS Delivery Failures Impacting Carrier Login 3h 7m External API, Broker Web Application
Started Apr 22, 2025, 12:27 PM UTC· resolved Apr 22, 2025, 03:34 PM UTC
- monitoring Apr 22, 2025, 12:27 PM UTC
Our provider for SMS is currently experiencing issues, which you can see below. https://status.twilio.com/#development Until this is resolved a subset of carriers leveraging SMS may be unable to login
- resolved Apr 22, 2025, 03:34 PM UTC
This incident is now resolved and SMS messages should be delivered successfully. https://status.twilio.com/#development
Minor February 14, 2025 Important Update on Delayed Release of Monthly SMS Inspection, Violation, and Crash Data 66d 17h External API, Broker Web Application
Started Feb 14, 2025, 06:40 PM UTC· resolved Apr 22, 2025, 12:21 PM UTC
- identified Feb 14, 2025, 06:40 PM UTC
FMCSA representatives have confirmed to us that the data delivery process for monthly SMS inspection, violation, and crash datasets has changed. We understand that the FMCSA data team is working to finalize their new delivery process, but we currently don’t have a timeline for when the latest versions of these datasets will become available. We want to ensure you’re fully aware of the impact this may have. Key Details: - We have received updated BASIC scores - The FMCSA is currently making changes to their data delivery process for monthly SMS inspection, violation, and crash data. - Detailed inspection, violation, and crash datasets have not yet been released for the most recent month. - Unfortunately, we do not have a timeline for when the detailed datasets will be made available from the FMCSA. Please note, while we have the updated BASIC scores, the detailed inspection, violation, and crash data will not be reflected in Highway until those datasets are made available from the FMCSA. We will continue to monitor the situation and will post an update here as soon as we have more information.
- identified Feb 14, 2025, 06:40 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 27, 2025, 04:25 PM UTC
The FMCSA has communicated that they expect to have the SMS data on DataHub by this weekend. January results for SMS inspections, violations and crashes were provided manually to us by the FMCSA and have been updated in Highway.
- resolved Apr 22, 2025, 12:21 PM UTC
The FMCSA has provided the updated SMS information. SMS information has now been updated in Highway.
Notice January 29, 2025 Highway broker user interface facing intermittent loading issues –
Started Jan 29, 2025, 12:30 PM UTC· resolved Jan 29, 2025, 12:30 PM UTC
- resolved Jan 29, 2025, 01:20 PM UTC
Highway's broker user interface was failing to load for some users following a production update from this morning. Issues were reported by users at 6:30am CT and the rollback was completed at 7:10am CT. Systems and interfaces are now functioning as expected.
Notice December 20, 2024 Service Disruption Due to Failed Annual Customer Subscription Update –
Started Dec 20, 2024, 05:49 PM UTC· resolved Dec 20, 2024, 05:49 PM UTC
- resolved Dec 20, 2024, 07:28 PM UTC
Incident Duration: 11:49 AM CT - 12:02 PM CT 1. Summary of Incident: At 11:49am CT on 12/20/2024, we performed an annual update intended to extend the service expiration date for a subset of our subscribed customers from 12/31/2024 to 12/31/2025. An error in our update logic resulted in that subset of subscribed customers being marked as unsubscribed, which in turn led to limited access to highway.com for affected customer users. During the incident window, affected users were redirected to a static page outlining their company’s plan and an outdated credit card form prompting the user to subscribe to Highway. 2. Resolution: Upon detecting the anomaly, our technical team responded within minutes, correcting the update logic error and correctly updating the service expiration date. No further issues have been detected, and we are monitoring for any sign of issues related to this service disruption. 3. Action Plan & Prevention: Code Optimization: Work has begun to solidify the logic of this annual update process to include testing guardrails and ensure a similar error doesn’t recur when we expect to repeat this process in December of 2025. We sincerely apologize for any inconvenience caused to our customers due to this incident. Our team is committed to learning from these events and continually refining our operations to serve you better.