Fleetworthy Outage History

Started Oct 21, 2026, 10:50 PM UTC· resolved Oct 26, 2026, 01:56 PM UTC

1. investigating Oct 21, 2026, 10:50 PM UTC

   Dear Fleetworthy Customers, Status: Under Maintenance The Rapid Log site is currently offline while our team performs unplanned maintenance. We are applying updates to protect our application from a known security vulnerability. What this means for you: Rapid Log is temporarily unavailable. We understand this may disrupt your work, and we apologize for the inconvenience. What we're doing: Our team is actively working to apply the necessary updates and will bring the site back online as soon as it is safe to do so. Protecting the security of our application and your data is our top priority. Next update: We will post another update as soon as we have more information. Thank you for your patience and understanding.

2. investigating Oct 22, 2026, 12:54 PM UTC

   Dear Fleetworthy Customers, Status: Under Maintenance The Rapid Log site remains offline while our team performs unplanned maintenance. Efforts continue to apply updates and software upgrades to protect our application from a known security vulnerability. What this means for you: Rapid Log is temporarily unavailable. We understand this may disrupt your work, and we apologize for the inconvenience. What we're doing: Our team is actively working to apply the necessary updates and will bring the site back online as soon as it is safe to do so. Protecting the security of our application and your data is our top priority. Next update: We will post another update as soon as we have more information. Thank you for your patience and understanding.

3. identified Oct 22, 2026, 03:00 PM UTC

   Dear Fleetworthy Customers, Status: Under Maintenance Update Self-hosted Instances: Updates have been applied to restore functionality allowing users with self-hosted instances to utilize the Rapid Log application. Update Cloud-hosted Instances: Rapid Log Cloud Hosted instances remain offline while our team continues to apply updates and software upgrades to protect our application from a known security vulnerability. What this means for you: Rapid Log Cloud is temporarily unavailable. We understand this may disrupt your work, and we apologize for the inconvenience. What we're doing: Our team is actively working to apply the necessary updates and will bring the site back online as soon as it is safe to do so. Protecting the security of our application and your data is our top priority. Next update: We will post another update as soon as we have more information. Thank you for your patience and understanding.

4. monitoring Oct 22, 2026, 04:54 PM UTC

   Rapid Log Maintenance Completed – Services Restored Status: Resolved (Partial – Website Maintenance Ongoing) Update: The unplanned maintenance on Rapid Log is now complete. The known security vulnerabilities have been secured. Current service status: - Rapid Log Cloud: Fully restored - Rapid Log Self-Hosted: Fully restored - Rapidlog.com: http://Rapidlog.com website: Under construction What to expect: The Rapidlog.com: http://Rapidlog.com website remains under construction while we perform additional maintenance on some underlying features. Thank you for your patience and understanding while we worked to protect our application and your data.

5. resolved Oct 26, 2026, 01:56 PM UTC

   The incident affecting service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Oct 21, 2026, 10:44 PM UTC· resolved Oct 21, 2026, 11:19 PM UTC

1. investigating Oct 21, 2026, 10:44 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to Weigh Station Bypass service. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. monitoring Oct 21, 2026, 11:03 PM UTC

   Dear Fleetworthy Customers, Status: Resolved Start: October 21, 2026, 4:15 PM MDT End: October 21, 2026, 4:55 PM MDT Problem: While performing updates to the Bypass environment, an issue was introduced that temporarily interrupted underlying services. The net effect was a loss of bypass delivery to all users. Resolution: Our team identified the issue and restored the affected services. Bypass delivery has resumed and the service is operating normally. We apologize for the disruption this caused. If you continue to experience any issues, please contact our support team.

3. resolved Oct 21, 2026, 11:19 PM UTC

   The incident affecting Weigh Station Bypass service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Oct 20, 2026, 02:18 PM UTC· resolved Oct 22, 2026, 01:06 PM UTC

1. investigating Oct 20, 2026, 02:18 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to Portal service. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. investigating Oct 20, 2026, 03:29 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to Toll Activity Reporting Data. Our engineering and operations teams are actively working to identify the cause and restore function. Further updates will be provided as more information becomes available.

3. identified Oct 20, 2026, 06:36 PM UTC

   Dear Fleetworthy Customers, Status: Fixing We have identified the underlying cause of the issue affecting the delivery of Toll transaction activity in the Fleetworthy toll portal. Also via API Reporting in the Bestpass Customer Portal. A fix is being implemented to restore access to reporting data. We will provide further updates as more information becomes available.

4. identified Oct 20, 2026, 08:36 PM UTC

   Dear Fleetworthy Customers. Status: Fixing Our teams continue to focus on restoring the delivery of Toll Activity Data to our customers. We are closely monitoring the restoration process which is progressing as expected. There is no firm ETA on full restoration and resolution at this time. We will continue to share updates until the issue is resolved.

5. monitoring Oct 20, 2026, 10:17 PM UTC

   Dear Fleetworthy Customers. Significant progress has been met with remediation efforts. Customer are now able to view Toll Activity data up to approximately midday October 19, 2026. Monitoring and validation remain top priorities as we continue to work toward resolution. There is no firm ETA on full restoration and resolution at this time. We will continue to share updates until the issue is resolved.

6. monitoring Oct 21, 2026, 12:49 PM UTC

   Dear Fleetworthy Customers. Status: Recovering Toll activity in the portal is now showing current data through the morning of Oct 21. There is a short delay in the newest activity. Our team is continuing to work on completing the remaining follow-up work. We will continue to share updates until we are fully restored, or sooner if anything changes.

7. monitoring Oct 21, 2026, 04:33 PM UTC

   Dear Fleetworthy Customers. Status: Resolved – Monitoring All data updates have resumed, and the Toll transaction data is now updating automatically in real-time. Tolling API data from October 15 onward is available. However, if your integration uses a short look-back window, it may have missed some transactions during this period. We recommend reviewing your data for any gaps. What we’re doing Our team will be reaching out directly to customers with Toll API Integrations to help recover any missing transaction data from this window. We are still working to determine the underlying cause and will share more information as it becomes available. Thank you for your patience. If you have any questions or concerns, please contact Customer Service for assistance.

8. monitoring Oct 21, 2026, 10:23 PM UTC

   Status: Recovering – Monitoring We’re pleased to report continued progress in restoring toll data. Toll data availability continues to improve as expected, and our team is actively monitoring the service to keep it moving in the right direction. What we’re doing We are continuing to monitor data flow, complete remaining follow-up work, and investigate the underlying cause. We’ll share more information as it becomes available. Need help? If you notice anything suspicious, such as missing transactions, unexpected delays, or data that doesn’t look right, please contact Fleetworthy Support and we’ll be glad to assist. We’ll provide our next update tomorrow morning, or sooner if anything changes. Thank you for your continued patience.

9. resolved Oct 22, 2026, 01:06 PM UTC

   Status: Resolved Dear Fleetworthy Customers, We’re writing with an update on the recent toll data incident. Service has been restored, and customer-facing toll data is back to its expected freshness across accounts. What’s working • Toll360 now shows toll data as expected, alongside the standard toll activity in the portal. • Toll data is flowing normally, and our regular data processing is up to date and back on schedule. What to expect today Toll Genius data is currently behind while we process a backlog from the outage. We expect it to be fully up to date by the end of day today. If you rely on Toll Genius for time-sensitive work, you may notice some delay until then. If you have an API integration If your integration uses a short look-back window, it may have missed some transactions during the outage and may need a one-time catch-up request to retrieve them. We are reaching out directly to affected Toll API customers and partners, and our Support Engineers can work with you case by case to recover any missing data. Next steps We are still investigating the underlying cause of the incident and will share more as it becomes available. If you notice anything unexpected, such as missing transactions or data that doesn’t look right, or if you need additional assistance, please contact Fleetworthy Support. Thank you for your patience and continued trust. The Fleetworthy Team

Read the full incident report →

Started Oct 06, 2026, 04:54 PM UTC· resolved Oct 06, 2026, 07:56 PM UTC

1. investigating Oct 06, 2026, 04:54 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to our marketing websites at fleetworthy.com and bestpass.com. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. monitoring Oct 06, 2026, 05:00 PM UTC

   Service has been restored to bestpass.com and fleetworthy.com, and we are closely monitoring the results. We will confirm resolution once the issue has been fully validated.

3. resolved Oct 06, 2026, 07:56 PM UTC

   The incident affecting the bestpass.com and fleetworthy.com marketing sites has been resolved. Normal operation has been fully restored. Thank you for your patience during this time.

Read the full incident report →

Started Sep 28, 2026, 06:59 PM UTC· resolved Oct 13, 2026, 03:11 PM UTC

1. identified Sep 28, 2026, 06:59 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to Haul service. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. resolved Oct 13, 2026, 03:11 PM UTC

   The incident affecting Haul service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Sep 21, 2026, 05:14 PM UTC· resolved Oct 06, 2026, 12:53 AM UTC

1. investigating Sep 21, 2026, 05:14 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to Driver Safety service. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. investigating Sep 21, 2026, 06:33 PM UTC

   Fleetworthy Go Service Disruption Status: Investigating We are aware of an issue affecting some devices that received the update to Fleetworthy Go version 5.2.1. Affected devices may experience a loss of Heads Up, Safety, and Bypass Notifications for drivers. Our Engineering and Live Services Incident Response teams are actively investigating the underlying cause of this issue. As part of remediation efforts, the Live Services Incident Response team is sending remote management commands to affected devices to restore full application functionality. Subscribers experiencing this issue are encouraged to contact Fleetworthy Support for assistance. We will provide updates as more information becomes available.

3. investigating Sep 21, 2026, 06:41 PM UTC

   Dear Fleetworthy Customers, We are aware of an issue affecting some Apple iOS devices that received the update to Fleetworthy Go version 5.2.1. Affected devices may experience a loss of Heads Up, Safety, and Bypass Notifications for drivers. Our Engineering and Live Services Incident Response teams are actively investigating the underlying cause of this issue. As part of remediation efforts, the Live Services Incident Response team is sending remote management commands to affected devices to restore full application functionality. Subscribers experiencing this issue are encouraged to contact Fleetworthy Support for assistance. We will provide updates as more information becomes available.

4. monitoring Oct 02, 2026, 10:28 PM UTC

   Dear Fleetworthy Customers, We are providing an update on the issue affecting some Apple iOS devices that received the update to Drivewyze iOS Mobile App v5.2.1. Affected devices may experience a loss of Heads Up, Safety, and Bypass Notifications for drivers. The underlying cause of the issue has been identified by our Engineering team. Steps for quick remediation are in place and are currently being executed by the Live Services Incident Response team. Our Engineering and Live Services teams have confidence in the issue diagnosis and remediation plan, given the high success rate and significant drop in failure rates observed to date. Our teams continue proactively correcting the state for affected devices. The team will also be deploying additional improvements and safeguards to increase velocity toward full resolution over the coming days. Please continue to contact our support team if you continue to experience issues receiving alerts. We will provide further updates as more information becomes available.

5. resolved Oct 06, 2026, 12:53 AM UTC

   The incident affecting Weigh Station Bypass service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

6. resolved Oct 06, 2026, 12:54 AM UTC

   Dear Fleetworthy Customers, We are writing to confirm that the issue affecting some Apple iOS devices that received the update to Drivewyze iOS Mobile App v5.2.1 has been resolved. Our Engineering team introduced new logic in backend services, requiring no application update, that gracefully manages requests with invalid credentials and allows affected devices to self-heal. This fix has resolved the underlying cause of the loss of Heads Up, Safety, and Bypass Notifications for drivers. If you continue to experience issues, please contact Fleetworthy/Drivewyze Support for assistance. Thank you for your patience while we worked through this issue.

Read the full incident report →

Started Aug 20, 2026, 10:26 PM UTC· resolved Aug 20, 2026, 10:46 PM UTC

1. investigating Aug 20, 2026, 10:26 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to the CP Suite portal including People, Asset, and Carrier pages that's resulting in no data displaying. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. resolved Aug 20, 2026, 10:46 PM UTC

   The incident affecting service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Aug 18, 2026, 05:46 PM UTC· resolved Aug 26, 2026, 09:30 PM UTC

1. monitoring Aug 18, 2026, 05:46 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to service in Oregon that's resulting in increased pull-in instructions. The cause has been identified and we've communicated the fix back to the Oregon DOT team. We are currently monitoring for the fix to be applied so that bypass rates in Oregon return to normal. Further updates will be provided as more information becomes available.

2. monitoring Aug 26, 2026, 09:28 PM UTC

   A fix has been implemented, and we are closely monitoring the results. We will confirm resolution once the issue has been fully validated.

3. resolved Aug 26, 2026, 09:30 PM UTC

   The incident affecting service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Aug 05, 2026, 04:05 PM UTC· resolved Aug 05, 2026, 08:53 PM UTC

1. investigating Aug 05, 2026, 04:05 PM UTC

   Dear Fleetworthy Customers, We want to make you aware of an issue affecting CPSuite Alerting. What happened CPSuite Alerting stopped filtering alerts by location. As a result, some drivers received alert emails that did not correspond to their actual location. Impact Some drivers may have received alert emails unrelated to their current location. We have disabled alerting to stop any further incorrect emails from going out. However, some emails that were already queued for delivery before alerts were disabled may still arrive. Resolution status • Alerting has been disabled to prevent additional incorrect emails. • Our engineering team is actively working on a fix. • We will notify you once alerting has been restored and confirmed to be filtering correctly. We apologize for the inconvenience and will share an update as soon as the fix is deployed. Fleetworthy Incident Response Team

2. identified Aug 05, 2026, 04:21 PM UTC

   Status: Identified Dear Fleetworthy Customers, We want to make you aware of an issue affecting CPSuite Alerting. What happened CPSuite Alerting stopped filtering alerts by location. As a result, some drivers received alert emails that did not correspond to their actual location. Impact Some drivers may have received alert emails unrelated to their current location. We have disabled alerting to stop any further incorrect emails from going out. However, some emails that were already queued for delivery before alerts were disabled may still arrive. Resolution status • The issue has been identified. • Alerting has been disabled to prevent additional incorrect emails. • Our engineering team is actively working on a fix. • We will notify you once alerting has been restored and confirmed to be filtering correctly. We apologize for the inconvenience and will share an update as soon as the fix is deployed. Fleetworthy Incident Response Team

3. identified Aug 05, 2026, 07:16 PM UTC

   Status: In Progress Dear Fleetworthy Customers, This is an update regarding the CPSuite Alerting location filtering issue. Current status Our engineering team continues to work on resolving the issue. We are actively developing and testing a fix to restore correct location-based filtering for alerts. What this means for you Alerting remains disabled while we work through the fix to prevent any further incorrect alert emails from being sent. Next steps We will continue to provide updates as we progress through applying the fix, and will notify you as soon as alerting has been restored and confirmed to be working correctly. We appreciate your patience and apologize for any inconvenience this issue has caused. Fleetworthy Incident Response Team

4. monitoring Aug 05, 2026, 08:21 PM UTC

   Status: Monitoring Dear Fleetworthy Customers, This is an update regarding the CPSuite Alerting location filtering issue. Current status Our engineering team has deployed a fix for this issue. We have re-enabled location-based alerts. What this means for you Alerting has been re-enabled and all future alert notifications should be delivered and received as expected. Next steps We will continue to monitor the fix to ensure a smooth transition to production status. We appreciate your patience and apologize for any inconvenience this issue has caused. Fleetworthy Incident Response Team

5. resolved Aug 05, 2026, 08:53 PM UTC

   Status: Resolved Dear Fleetworthy Customers, We are writing to let you know that the CPSuite Alerting location filtering issue has been fully resolved. Summary • The issue causing alerts to bypass location filtering has been fixed and verified. • Alerting is back online and functioning normally. • No further action is needed on your part. We apologize for any inconvenience this issue may have caused and thank you for your patience while we worked through the resolution. If you have any questions or continue to notice unexpected alerts, please reach out to our support team. Fleetworthy Incident Response Team

Read the full incident report →

Started Jul 15, 2026, 06:17 PM UTC· resolved Jul 15, 2026, 08:40 PM UTC

1. investigating Jul 15, 2026, 06:17 PM UTC

   Status: Investigating Dear Fleetworthy Customers, We are aware of an issue affecting some users of the CPSuite Portal. Affected users are able to log in successfully but may see a blank dashboard immediately after login. Workaround: Refreshing your browser will resolve the display issue. Our team is actively investigating the root cause. We will provide an update as more information becomes available. We apologize for the inconvenience and appreciate your patience. Fleetworthy Incident Response Team

2. identified Jul 15, 2026, 06:39 PM UTC

   Status: Identified Dear Fleetworthy Customers, We have identified the cause of an issue affecting some users of the CPSuite Portal. Affected users are able to log in successfully but may see a blank dashboard immediately after login. Workaround: Refreshing your browser will resolve the display issue. Our team is actively working on a fix and will provide an update once the issue has been resolved. We apologize for the inconvenience and appreciate your patience. Fleetworthy Incident Response Team

3. monitoring Jul 15, 2026, 06:57 PM UTC

   Status: Monitoring Dear Fleetworthy Customers, A fix has been implemented for the issue affecting some users of the CPSuite Portal, where affected users were able to log in successfully but saw a blank dashboard immediately after login. Workaround (if still needed): Refreshing your browser will resolve the display issue. We are currently monitoring the results to ensure the issue has been fully resolved. We will provide a final update shortly. We apologize for the inconvenience and appreciate your patience. Fleetworthy Incident Response Team

4. resolved Jul 15, 2026, 08:40 PM UTC

   Status: Resolved Dear Fleetworthy Customers, The issue affecting some users of the CPSuite Portal, where affected users were able to log in successfully but saw a blank dashboard immediately after login, has been resolved. All users should now be able to access their dashboard data without needing to refresh their browser. If you continue to experience this issue, please reach out to our support team. Thank you for your patience throughout this incident. Fleetworthy Incident Response Team

Read the full incident report →

Started Jul 13, 2026, 04:55 PM UTC· resolved Jul 14, 2026, 12:49 AM UTC

1. investigating Jul 13, 2026, 04:55 PM UTC

   We are currently investigating reports of a disruption to service to the Toll Portal. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. investigating Jul 13, 2026, 05:10 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage We are currently investigating an issue affecting the Bestpass Customer Portal. Our Operations and IT teams are actively engaged and working to identify the root cause and restore access as quickly as possible. Impact: • Customer-facing portals are temporarily inaccessible. • Toll operations continue to function as expected; there is no impact to toll processing or transactions. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

3. investigating Jul 13, 2026, 05:46 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage Our Operations and IT teams continue to investigate the issue affecting the Bestpass Customer Portal. Impact: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

4. investigating Jul 13, 2026, 06:53 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage Our Operations and IT teams continue to investigate the issue affecting the Bestpass Customer Portal. Impact: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

5. investigating Jul 13, 2026, 07:45 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage Our Operations and IT teams continue to investigate the issue affecting the Bestpass Customer Portal. Impact: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

6. investigating Jul 13, 2026, 08:58 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage Our Operations and IT teams continue to investigate the issue affecting the Bestpass Customer Portal. There are no specific updates that we are able to provide at this time. Our team members continue to be engaged working on finding resolution as our top priority. Impact: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

7. investigating Jul 13, 2026, 10:03 PM UTC

   Dear Fleetworthy Customers, Investigating — Customer Portal Outage Our Operations and IT teams continue to investigate the issue affecting the Bestpass Customer Portal. There are no specific updates that we are able to provide at this time. Our team members continue to be engaged working on finding resolution as our top priority. Impact: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. We will provide updates as more information becomes available. Fleetworthy Operations & IT Team

8. investigating Jul 13, 2026, 11:19 PM UTC

   Dear Fleetworthy Customers, Update — Customer Portal Outage (Ongoing) We understand this outage has now been ongoing for an extended amount of time and we sincerely apologize for the length of this disruption. Our Operations and IT teams have remained engaged throughout and continue to work to identify and resolve the root cause. Current Status: • Customer-facing portals are temporarily inaccessible. • Toll data collection continues. • Processing times may be affected. What we're doing: Our teams have escalated this incident internally and are working closely with AWS Escalation Support as we work to resolve issues identified in our cloud environment. We recognize the impact this extended downtime has on your ability to access account and billing information, and we are treating this as a top priority. We will continue to provide updates as they become available, and will notify you as soon as portal access is restored. We appreciate your patience. Fleetworthy Incident Response Team

9. resolved Jul 14, 2026, 12:49 AM UTC

   Dear Fleetworthy customers. Resolved — Customer Portal Outage We are pleased to confirm that the issue affecting the Bestpass Customer Portal has been resolved. All sites and services have fully recovered. Summary: This incident was caused by a network configuration issue within our cloud environment. Our teams, working closely with AWS Escalation Support, identified and corrected the issue, restoring full service. Current Status: • All customer-facing portals are fully accessible. • Toll data collection and processing has resumed. A detailed root cause analysis is currently underway. We will share further updates as that analysis is completed. We sincerely apologize for the disruption and appreciate your patience throughout this incident. Fleetworthy Incident Response Team

Read the full incident report →

Started Jul 09, 2026, 01:05 PM UTC· resolved Jul 09, 2026, 01:32 PM UTC

1. investigating Jul 09, 2026, 01:05 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to service of CP Suite. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. identified Jul 09, 2026, 01:19 PM UTC

   We have identified the underlying cause of the issue affecting the availability of CP Suite. A fix is being developed and implemented. We will continue to share updates until the issue is resolved.

3. resolved Jul 09, 2026, 01:32 PM UTC

   The incident affecting service to CP Suite has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Jul 07, 2026, 08:38 PM UTC· resolved Jul 08, 2026, 01:41 PM UTC

1. investigating Jul 07, 2026, 08:38 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to our drivewyze.com where it is being flagged as a "Dangerous Site" by Google Safe Browsing. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. identified Jul 07, 2026, 10:02 PM UTC

   We have identified the underlying cause of the issue causing the warning from Google. Drivewyze.com will currently redirect you to https://fleetworthy.com/ as we continue to work with Google to have the warning removed. We will continue to share updates until the issue is resolved.

3. resolved Jul 08, 2026, 01:41 PM UTC

   We've resolved an issue that was intermittently affecting access to drivewyze.com "drivewyze.com": http://drivewyze.com and related services. All systems are now fully operational. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started Jul 02, 2026, 04:03 PM UTC· resolved Jul 02, 2026, 05:44 PM UTC

1. investigating Jul 02, 2026, 04:03 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to services for Bestpass, ITM, and Payviam services. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. identified Jul 02, 2026, 04:26 PM UTC

   We have identified the underlying cause of the issue affecting the delivery of service. A fix is being developed and implemented. We will continue to share updates until the issue is resolved.

3. monitoring Jul 02, 2026, 04:59 PM UTC

   A fix has been implemented, and we are closely monitoring the results. We will confirm resolution once the issue has been fully validated.

4. resolved Jul 02, 2026, 05:44 PM UTC

   The incident affecting service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started May 20, 2026, 03:37 PM UTC· resolved May 20, 2026, 05:31 PM UTC

1. investigating May 20, 2026, 03:37 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to service for eFleet Forms. Our engineering and operations teams are actively working to identify the cause. Further updates will be provided as more information becomes available.

2. identified May 20, 2026, 04:20 PM UTC

   We have identified the underlying cause of the issue affecting the delivery of service. A fix is being developed and implemented. We will continue to share updates until the issue is resolved.

3. monitoring May 20, 2026, 05:12 PM UTC

   A fix has been implemented, and we are closely monitoring the results. We will confirm resolution once the issue has been fully validated.

4. resolved May 20, 2026, 05:31 PM UTC

   The incident affecting eFleet form services has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Feb 19, 2026, 01:33 PM UTC· resolved Feb 19, 2026, 02:58 PM UTC

1. investigating Feb 19, 2026, 01:33 PM UTC

   Dear Fleetworthy Customers, We are currently investigating reports of a disruption to service due to redirection from Toll Portal to maintenance page. Our engineering and operations teams are actively working on the condition. Further updates will be provided as more information becomes available.

2. resolved Feb 19, 2026, 02:58 PM UTC

   The incident affecting service has been resolved. Normal operation has been fully restored. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Oct 29, 2025, 04:05 PM UTC· resolved Oct 30, 2025, 12:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 03:03 PM UTC· resolved Oct 20, 2025, 09:24 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 08, 2025, 08:44 PM UTC· resolved Oct 10, 2025, 09:57 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →