Trimble Transportation Outage History

Started Sep 28, 2026, 05:24 AM UTC· resolved Sep 28, 2026, 11:50 AM UTC

1. monitoring Sep 28, 2026, 05:24 AM UTC

   We are aware of a recently published security advisory from Citrix that affects certain Citrix components used in our environment. Citrix services remain available, and we do not expect disruption for most users. If any maintenance is required that could affect access, we will provide advance notice whenever possible. We take the security of our platform seriously and will continue to monitor the situation closely.

2. investigating Sep 28, 2026, 05:24 AM UTC

   We are aware of a recently published security advisory from Citrix that affects certain Citrix components used in our environment. Citrix services remain available, and we do not expect disruption for most users. If any maintenance is required that could affect access, we will provide advance notice whenever possible. We take the security of our platform seriously and will continue to monitor the situation closely.

3. monitoring Sep 28, 2026, 10:15 AM UTC

   We are responding to a Citrix security advisory that may affect some of our Citrix services. We are actively applying the recommended updates and protective measures as a precaution. Citrix services remain available, and we do not expect disruption for users.

4. in progress Sep 28, 2026, 10:15 AM UTC

   We are responding to a Citrix security advisory that may affect some of our Citrix services. We are actively applying the recommended updates and protective measures as a precaution. Citrix services remain available, and we do not expect disruption for users.

5. monitoring Sep 28, 2026, 11:19 AM UTC

   We will be performing scheduled maintenance at 7:30AM ET September 28, 2026 to upgrade the NetScaler ADC/Gateway software to a vendor-recommended secure version. This upgrade is being completed to address multiple security vulnerabilities identified by Citrix and to help maintain the security and reliability of the environment. We do not expect any downtime during this maintenance window. However, users may experience a brief disconnect while the upgrade is in progress. If this occurs, users should be able to reconnect immediately.

6. resolved Sep 28, 2026, 11:19 AM UTC

   We will be performing scheduled maintenance at 7:30AM ET September 28, 2026 to upgrade the NetScaler ADC/Gateway software to a vendor-recommended secure version. This upgrade is being completed to address multiple security vulnerabilities identified by Citrix and to help maintain the security and reliability of the environment. We do not expect any downtime during this maintenance window. However, users may experience a brief disconnect while the upgrade is in progress. If this occurs, users should be able to reconnect immediately.

7. monitoring Sep 28, 2026, 11:50 AM UTC

   This scheduled maintenance has been completed.

8. resolved Sep 28, 2026, 11:50 AM UTC

   This scheduled maintenance has been completed.

Read the full incident report →

Started Sep 04, 2026, 11:27 AM UTC· resolved Sep 07, 2026, 05:51 PM UTC

1. monitoring Sep 04, 2026, 11:27 AM UTC

   A subset of Microsoft 365 Exchange Online users may experience delays or failures receiving e-mails sent by Trimble. This is an issue within the Microsoft 365 ecosystem and is not caused by Trimble systems or infrastructure. Microsoft is currently analyzing the behavior and review service telemetry to identify the underlying cause and determine the most effective mitigation. As we receive additional information from Microsoft, we will provide updates. For the latest information, please visit the Service Health page within your Microsoft 365 portal.

2. investigating Sep 04, 2026, 11:27 AM UTC

   A subset of Microsoft 365 Exchange Online users may experience delays or failures receiving e-mails sent by Trimble. This is an issue within the Microsoft 365 ecosystem and is not caused by Trimble systems or infrastructure. Microsoft is currently analyzing the behavior and review service telemetry to identify the underlying cause and determine the most effective mitigation. As we receive additional information from Microsoft, we will provide updates. For the latest information, please visit the Service Health page within your Microsoft 365 portal.

3. monitoring Sep 04, 2026, 12:24 PM UTC

   Microsoft has identified a specific anti-spam filtering model that is affecting a subset of email traffic. As an initial mitigation, Microsoft is allow-listing the affected IP addresses that were subject to throttling. They are also working to disable the filtering model responsible for the impact.

4. investigating Sep 04, 2026, 12:24 PM UTC

   Microsoft has identified a specific anti-spam filtering model that is affecting a subset of email traffic. As an initial mitigation, Microsoft is allow-listing the affected IP addresses that were subject to throttling. They are also working to disable the filtering model responsible for the impact.

5. monitoring Sep 04, 2026, 02:08 PM UTC

   Telemetry shows that the service is performing as expected for new emails and this is in line with organizations confirming that the issue no longer occurring. We're monitoring email queues and performing final validations to confirm the issue is fully resolved.

6. monitoring Sep 04, 2026, 02:08 PM UTC

   Telemetry shows that the service is performing as expected for new emails and this is in line with organizations confirming that the issue no longer occurring. We're monitoring email queues and performing final validations to confirm the issue is fully resolved.

7. monitoring Sep 07, 2026, 05:51 PM UTC

   Microsoft has mitigated the Exchange Online issue that caused delays or failures when receiving emails sent by Trimble. Email delivery has returned to normal, and no further impact is expected. This incident originated within the Microsoft 365 ecosystem and was not caused by Trimble systems or infrastructure.

8. resolved Sep 07, 2026, 05:51 PM UTC

   Microsoft has mitigated the Exchange Online issue that caused delays or failures when receiving emails sent by Trimble. Email delivery has returned to normal, and no further impact is expected. This incident originated within the Microsoft 365 ecosystem and was not caused by Trimble systems or infrastructure.

Read the full incident report →

Started Jun 24, 2026, 02:19 PM UTC· resolved Jun 24, 2026, 03:14 PM UTC

1. monitoring Jun 24, 2026, 02:19 PM UTC

   Trimble Cloud Services is aware of an issue affecting the Central US SMTP Relay Servers, which may be causing degraded availability for some customers. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We will provide additional updates as more information becomes available.

2. investigating Jun 24, 2026, 02:19 PM UTC

   Trimble Cloud Services is aware of an issue affecting the Central US SMTP Relay Servers, which may be causing degraded availability for some customers. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We will provide additional updates as more information becomes available.

3. monitoring Jun 24, 2026, 02:27 PM UTC

   Trimble Cloud Services has implemented a fix for the Central US SMTP Relay Server issue, and service availability has returned to expected levels. We are continuing to monitor the environment to ensure mail flow remains stable. Additional updates will be provided if any further impact is identified.

4. monitoring Jun 24, 2026, 02:27 PM UTC

   Trimble Cloud Services has implemented a fix for the Central US SMTP Relay Server issue, and service availability has returned to expected levels. We are continuing to monitor the environment to ensure mail flow remains stable. Additional updates will be provided if any further impact is identified.

5. monitoring Jun 24, 2026, 03:14 PM UTC

   Trimble Cloud Services has confirmed that the Central US SMTP Relay Server issue has been resolved. Mail flow has returned to normal, and we have completed monitoring with no further impact observed. We appreciate your patience while our teams worked to resolve this issue.

6. resolved Jun 24, 2026, 03:14 PM UTC

   Trimble Cloud Services has confirmed that the Central US SMTP Relay Server issue has been resolved. Mail flow has returned to normal, and we have completed monitoring with no further impact observed. We appreciate your patience while our teams worked to resolve this issue.

Read the full incident report →

Started Jan 22, 2026, 08:30 PM UTC· resolved Jan 23, 2026, 06:27 AM UTC

1. monitoring Jan 22, 2026, 08:30 PM UTC

   Customers utilizing a Microsoft 365 tenant for email services may experience delays or intermittent failures when sending or receiving email. At this time, the issue appears to be related to Microsoft 365 services and is not the result of any outage or recent change within the Trimble hosted environment. Although Microsoft has not yet published an official service advisory, we are observing behavior consistent with a broader Microsoft-side service disruption. Customers utilizing the Trimble Transportation Enterprise SMTP Relay services are not affected by this issue. We are actively monitoring the situation and have engaged Microsoft Support for additional visibility. At this time, Microsoft has not provided an estimated time to resolution. Further updates will be shared as additional information becomes available.

2. investigating Jan 22, 2026, 08:30 PM UTC

   Customers utilizing a Microsoft 365 tenant for email services may experience delays or intermittent failures when sending or receiving email. At this time, the issue appears to be related to Microsoft 365 services and is not the result of any outage or recent change within the Trimble hosted environment. Although Microsoft has not yet published an official service advisory, we are observing behavior consistent with a broader Microsoft-side service disruption. Customers utilizing the Trimble Transportation Enterprise SMTP Relay services are not affected by this issue. We are actively monitoring the situation and have engaged Microsoft Support for additional visibility. At this time, Microsoft has not provided an estimated time to resolution. Further updates will be shared as additional information becomes available.

3. monitoring Jan 22, 2026, 08:51 PM UTC

   Microsoft has confirmed this issue is related to their infrastructure and is not related to Trimble infrastructure or services. We have included the Microsoft official statement regarding the disruption below For the most up-to-date information and status updates, please refer to the Microsoft 365 Service Health Status page: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to monitor the situation and share updates as they become available. From Microsoft: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Collecting message traces may be delayed or fail. - Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. Current status: We're continuing to review what actions are required to restore the affected infrastructure to a heathy state and rebalance the service traffic to achieve recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Thursday, January 22, 2026, at 11:00 PM UTC

4. investigating Jan 22, 2026, 08:51 PM UTC

   Microsoft has confirmed this issue is related to their infrastructure and is not related to Trimble infrastructure or services. We have included the Microsoft official statement regarding the disruption below For the most up-to-date information and status updates, please refer to the Microsoft 365 Service Health Status page: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to monitor the situation and share updates as they become available. From Microsoft: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Collecting message traces may be delayed or fail. - Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. Current status: We're continuing to review what actions are required to restore the affected infrastructure to a heathy state and rebalance the service traffic to achieve recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Thursday, January 22, 2026, at 11:00 PM UTC

5. monitoring Jan 23, 2026, 06:27 AM UTC

   Microsoft has confirmed the previously reported email delivery issues related to Microsoft 365 infrastructure have been resolved. The issue was not related to Trimble infrastructure or services, and no impact was identified within the Trimble hosted environment. Email delivery for customers utilizing Microsoft 365 tenants should now be operating normally. We will continue to monitor service health and will provide additional updates if necessary.

6. resolved Jan 23, 2026, 06:27 AM UTC

   Microsoft has confirmed the previously reported email delivery issues related to Microsoft 365 infrastructure have been resolved. The issue was not related to Trimble infrastructure or services, and no impact was identified within the Trimble hosted environment. Email delivery for customers utilizing Microsoft 365 tenants should now be operating normally. We will continue to monitor service health and will provide additional updates if necessary.

Read the full incident report →

Started Oct 20, 2025, 08:42 PM UTC· resolved Oct 21, 2025, 02:55 PM UTC

1. monitoring Oct 20, 2025, 08:42 PM UTC

   The Trimble Transportation Cloud team is aware of an issue that may be impacting Mile Server API calls. Our team is actively working to identify and resolve the issue. Updates will be provided here as they become available. For the most up-to-date information, please visit the Trimble MAPS Status Page

2. investigating Oct 20, 2025, 08:42 PM UTC

   The Trimble Transportation Cloud team is aware of an issue that may be impacting Mile Server API calls. Our team is actively working to identify and resolve the issue. Updates will be provided here as they become available. For the most up-to-date information, please visit the Trimble MAPS Status Page

3. monitoring Oct 20, 2025, 09:40 PM UTC

   We are pleased to report that the increased latency observed in our European data center has been resolved. System performance has returned to normal levels, and we expect this will correct any recent issues with TMS calculations. Our team continues to work diligently with our infrastructure partner to resolve the primary issue affecting our US data center. Restoring full service remains our highest priority. Thank you for your continued patience.

4. investigating Oct 20, 2025, 09:40 PM UTC

   We are pleased to report that the increased latency observed in our European data center has been resolved. System performance has returned to normal levels, and we expect this will correct any recent issues with TMS calculations. Our team continues to work diligently with our infrastructure partner to resolve the primary issue affecting our US data center. Restoring full service remains our highest priority. Thank you for your continued patience.

5. monitoring Oct 21, 2025, 01:23 AM UTC

   We are pleased to report that the increased latency observed in our European data center has been resolved. System performance has returned to normal levels, and we expect this will correct any recent issues with TMS calculations. Our team continues to work diligently with our infrastructure partner to resolve the primary issue affecting our US data center. Restoring full service remains our highest priority. Thank you for your continued patience.

6. monitoring Oct 21, 2025, 01:23 AM UTC

   We are pleased to report that the increased latency observed in our European data center has been resolved. System performance has returned to normal levels, and we expect this will correct any recent issues with TMS calculations.Our team continues to work diligently with our infrastructure partner to resolve the primary issue affecting our US data center. Restoring full service remains our highest priority.Thank you for your continued patience.

7. monitoring Oct 21, 2025, 02:55 PM UTC

   Full service has been restored and a period of stability observed. The incident has been resolved.

8. resolved Oct 21, 2025, 02:55 PM UTC

   Full service has been restored and a period of stability observed. The incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 04:33 PM UTC· resolved Oct 21, 2025, 01:24 AM UTC

1. monitoring Oct 20, 2025, 04:33 PM UTC

   We are actively investigating an issue that may be impacting the SaaS User Management Application. Our team is working to identify the cause and implement a solution as quickly as possible. We apologize for any inconvenience this may cause and will provide an update as soon as more information becomes available.

2. investigating Oct 20, 2025, 04:33 PM UTC

   We are actively investigating an issue that may be impacting the SaaS User Management Application. Our team is working to identify the cause and implement a solution as quickly as possible. We apologize for any inconvenience this may cause and will provide an update as soon as more information becomes available.

3. monitoring Oct 21, 2025, 01:24 AM UTC

   Our infrastructure partner has mitigated the issue that caused the SaaS User Management Application to be unavailable. The service is now fully operational. We will continue to monitor to ensure stability. Thank you for your patience during this disruption.

4. resolved Oct 21, 2025, 01:24 AM UTC

   Our infrastructure partner has mitigated the issue that caused the SaaS User Management Application to be unavailable. The service is now fully operational. We will continue to monitor to ensure stability. Thank you for your patience during this disruption.

Read the full incident report →

Started Sep 10, 2025, 01:09 PM UTC· resolved Sep 10, 2025, 02:09 PM UTC

1. resolved Sep 10, 2025, 01:09 PM UTC

   Some customer environments may remain unavailable following the scheduled maintenance window. After investigating, the Trimble Transportation Cloud Services team has confirmed that the issue originates on Microsoft Azure’s side. Microsoft has issued a Service Health Alert for the East US2 Region, indicating that service management operations may not complete successfully and could result in errors. This Azure platform issue has extended our maintenance window beyond the planned timeframe. We are in active communication with the Microsoft Azure Operations Team and are working closely with them to restore services as quickly as possible. Thank you for your patience and understanding as we work through this Azure-related incident.

2. identified Sep 10, 2025, 01:09 PM UTC

   Some customer environments may remain unavailable following the scheduled maintenance window. After investigating, the Trimble Transportation Cloud Services team has confirmed that the issue originates on Microsoft Azure’s side. Microsoft has issued a Service Health Alert for the East US2 Region, indicating that service management operations may not complete successfully and could result in errors. This Azure platform issue has extended our maintenance window beyond the planned timeframe. We are in active communication with the Microsoft Azure Operations Team and are working closely with them to restore services as quickly as possible. Thank you for your patience and understanding as we work through this Azure-related incident.

3. resolved Sep 10, 2025, 02:09 PM UTC

   The issue impacting some customer environments following the scheduled maintenance window has been resolved. All affected services have now been fully restored, and systems are operating normally. We sincerely appreciate your patience and understanding while we collaborated with Microsoft to resolve this incident.

4. resolved Sep 10, 2025, 02:09 PM UTC

   The issue impacting some customer environments following the scheduled maintenance window has been resolved. All affected services have now been fully restored, and systems are operating normally. We sincerely appreciate your patience and understanding while we collaborated with Microsoft to resolve this incident.

Read the full incident report →

Started Aug 09, 2025, 12:43 PM UTC· resolved Aug 09, 2025, 12:59 PM UTC

1. resolved Aug 09, 2025, 12:43 PM UTC

   We are currently aware of and investigating issues affecting D2Link. Our team is working to identify the cause and restore normal service as quickly as possible. We will provide updates as more information becomes available.

2. investigating Aug 09, 2025, 12:43 PM UTC

   We are currently aware of and investigating issues affecting D2Link. Our team is working to identify the cause and restore normal service as quickly as possible. We will provide updates as more information becomes available.

3. resolved Aug 09, 2025, 12:59 PM UTC

   Resolved — The issues affecting D2Link have been identified and resolved. All services are now operating normally. We will continue to monitor to ensure full stability.

4. resolved Aug 09, 2025, 12:59 PM UTC

   Resolved — The issues affecting D2Link have been identified and resolved. All services are now operating normally. We will continue to monitor to ensure full stability.

Read the full incident report →

Started Jul 23, 2025, 04:51 PM UTC· resolved Jul 24, 2025, 11:59 AM UTC

1. resolved Jul 23, 2025, 04:51 PM UTC

   We are currently investigating intermittent connectivity issues affecting CrushFTP services in the Central US region. Users may experience delays or temporary disruptions when accessing the Web Portal, SFTP, or automated job functions. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide updates here as more information becomes available. Thank you for your patience.

2. investigating Jul 23, 2025, 04:51 PM UTC

   We are currently investigating intermittent connectivity issues affecting CrushFTP services in the Central US region. Users may experience delays or temporary disruptions when accessing the Web Portal, SFTP, or automated job functions. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide updates here as more information becomes available. Thank you for your patience.

3. resolved Jul 23, 2025, 07:54 PM UTC

   The issue affecting connectivity to CrushFTP services in the Central US region appears to have stabilized. All services are currently operating as expected. Our team will continue to closely monitor the environment to ensure continued stability.

4. monitoring Jul 23, 2025, 07:54 PM UTC

   The issue affecting connectivity to CrushFTP services in the Central US region appears to have stabilized. All services are currently operating as expected. Our team will continue to closely monitor the environment to ensure continued stability.

5. resolved Jul 24, 2025, 11:59 AM UTC

   The intermittent connectivity issues impacting CrushFTP services in the Central US region have been fully resolved. All systems are now operating normally. We will continue to monitor for any further issues, but no additional impact is expected at this time. Thank you for your patience and understanding during this incident.

6. resolved Jul 24, 2025, 11:59 AM UTC

   The intermittent connectivity issues impacting CrushFTP services in the Central US region have been fully resolved. All systems are now operating normally. We will continue to monitor for any further issues, but no additional impact is expected at this time. Thank you for your patience and understanding during this incident.

Read the full incident report →

Started Jul 23, 2025, 03:00 PM UTC· resolved Jul 23, 2025, 10:29 PM UTC

1. resolved Jul 23, 2025, 03:00 PM UTC

   Users are currently experiencing login issues across multiple Domo instances related to Single Sign-On (SSO) configurations. Our engineering team is investigating this issue as a top priority and is working towards a resolution to restore access for affected users. We will provide further updates as more information becomes available. If you have any questions please open a case with our Support Team to further assist - https://crmtransportation.my.site.com/service/login

2. investigating Jul 23, 2025, 03:00 PM UTC

   Users are currently experiencing login issues across multiple Domo instances related to Single Sign-On (SSO) configurations. Our engineering team is investigating this issue as a top priority and is working towards a resolution to restore access for affected users. We will provide further updates as more information becomes available. If you have any questions please open a case with our Support Team to further assist - https://crmtransportation.my.site.com/service/login

3. resolved Jul 23, 2025, 06:15 PM UTC

   We have successfully tested a new authentication method to resolve the login issues across Domo instances. We are now rolling out this solution to all client instances, which is expected to take approximately one hour. Following the rollout, we will verify access with several clients. If they are able to log in successfully, we will send an email notification to all clients informing them that access has been restored. Please note that users will need to use a new URL for login, but all other aspects of the login process will remain unchanged. Thank you for your patience as we work to resolve this issue.

4. investigating Jul 23, 2025, 06:15 PM UTC

   We have successfully tested a new authentication method to resolve the login issues across Domo instances. We are now rolling out this solution to all client instances, which is expected to take approximately one hour. Following the rollout, we will verify access with several clients. If they are able to log in successfully, we will send an email notification to all clients informing them that access has been restored. Please note that users will need to use a new URL for login, but all other aspects of the login process will remain unchanged. Thank you for your patience as we work to resolve this issue.

5. resolved Jul 23, 2025, 07:35 PM UTC

   The update for the authentication method has been successfully applied to all client instances. We are now performing comprehensive testing on each instance to ensure optimal functionality. This testing phase is anticipated to take several hours. We will provide the next update once testing is complete. Should you have any questions or concerns, please do not hesitate to contact us. Thank you for your continued understanding and patience.

6. monitoring Jul 23, 2025, 07:35 PM UTC

   The update for the authentication method has been successfully applied to all client instances. We are now performing comprehensive testing on each instance to ensure optimal functionality. This testing phase is anticipated to take several hours. We will provide the next update once testing is complete. Should you have any questions or concerns, please do not hesitate to contact us. Thank you for your continued understanding and patience.

7. resolved Jul 23, 2025, 10:29 PM UTC

   We are pleased to inform you that the login issue has been fully resolved. All client instances have been successfully tested and are now functioning correctly with the new authentication method. Clients can now log in using the updated URL. Thank you for your patience and cooperation throughout this process. If you have any further questions or need assistance, please feel free to reach out.

8. resolved Jul 23, 2025, 10:29 PM UTC

   We are pleased to inform you that the login issue has been fully resolved. All client instances have been successfully tested and are now functioning correctly with the new authentication method. Clients can now log in using the updated URL. Thank you for your patience and cooperation throughout this process. If you have any further questions or need assistance, please feel free to reach out.

Read the full incident report →

Started Jul 18, 2025, 03:30 PM UTC· resolved Jul 18, 2025, 10:20 PM UTC

1. resolved Jul 18, 2025, 03:30 PM UTC

   A critical zero-day vulnerability has been identified in Crush. While there are currently no indications that this vulnerability has been exploited, we are taking proactive steps to protect your data by disabling the Web Portal. SFTP access and automated jobs remain unaffected at this time. We will begin patching at 6:00 PM EST on July 18, 2025. During this maintenance, all Crush services — including SFTP and automated jobs — will be unavailable for approximately 1 hour. We will restore all services as soon as the update is successfully applied.

2. investigating Jul 18, 2025, 03:30 PM UTC

   A critical zero-day vulnerability has been identified in Crush. While there are currently no indications that this vulnerability has been exploited, we are taking proactive steps to protect your data by disabling the Web Portal. SFTP access and automated jobs remain unaffected at this time. We will begin patching at 6:00 PM EST on July 18, 2025. During this maintenance, all Crush services — including SFTP and automated jobs — will be unavailable for approximately 1 hour. We will restore all services as soon as the update is successfully applied.

3. resolved Jul 18, 2025, 09:03 PM UTC

   As the security of your data is our top priority, our dedicated security team and 24/7 monitoring tools continuously safeguard our servers against potential threats. In addition to our normal security procedures, we have engaged directly with CrushFTP Support. Based on the indicators of compromise provided by CrushFTP, we have thoroughly reviewed this server and have found no evidence that the server was compromised or that any data was impacted in any way. The Trimble Transportation Cloud Services Operations Team will be applying the security patch at 6:00 PM EST on July 18, 2025. During this maintenance window, all CrushFTP services — including the Web Portal, SFTP access, and automated jobs — will be unavailable. We expect to have all CrushFTP services fully restored by 7:00 PM EST. We will continue to monitor and work closely with CrushFTP to ensure your data remains secure.

4. investigating Jul 18, 2025, 09:03 PM UTC

   As the security of your data is our top priority, our dedicated security team and 24/7 monitoring tools continuously safeguard our servers against potential threats. In addition to our normal security procedures, we have engaged directly with CrushFTP Support. Based on the indicators of compromise provided by CrushFTP, we have thoroughly reviewed this server and have found no evidence that the server was compromised or that any data was impacted in any way. The Trimble Transportation Cloud Services Operations Team will be applying the security patch at 6:00 PM EST on July 18, 2025. During this maintenance window, all CrushFTP services — including the Web Portal, SFTP access, and automated jobs — will be unavailable. We expect to have all CrushFTP services fully restored by 7:00 PM EST. We will continue to monitor and work closely with CrushFTP to ensure your data remains secure.

5. resolved Jul 18, 2025, 09:45 PM UTC

   The Trimble Transportation Cloud Services Operations Team will be applying the security patch in 15 minutes, at 6:00 PM EST on July 18, 2025. During this maintenance window, all CrushFTP services — including the Web Portal, SFTP access, and automated jobs — will be unavailable. We expect to have all CrushFTP services fully restored by 7:00 PM EST.

6. in progress Jul 18, 2025, 09:45 PM UTC

   The Trimble Transportation Cloud Services Operations Team will be applying the security patch in 15 minutes, at 6:00 PM EST on July 18, 2025. During this maintenance window, all CrushFTP services — including the Web Portal, SFTP access, and automated jobs — will be unavailable. We expect to have all CrushFTP services fully restored by 7:00 PM EST.

7. resolved Jul 18, 2025, 10:20 PM UTC

   The security patches addressing the recently identified CrushFTP vulnerability have been successfully applied. All CrushFTP services — including the Web Portal, SFTP access, and automated jobs — have been fully restored and are operating normally. At this time, we have no indication that this vulnerability was exploited. Thank you for your understanding and cooperation as we worked to ensure the security of your data. If you have any questions or encounter any issues, please reach out to our support team. For ongoing updates, please visit status.tmwcloud.com.

8. resolved Jul 18, 2025, 10:20 PM UTC

   The security patches addressing the recently identified CrushFTP vulnerability have been successfully applied. All CrushFTP services — including the Web Portal, SFTP access, and automated jobs — have been fully restored and are operating normally. At this time, we have no indication that this vulnerability was exploited. Thank you for your understanding and cooperation as we worked to ensure the security of your data. If you have any questions or encounter any issues, please reach out to our support team. For ongoing updates, please visit status.tmwcloud.com.

Read the full incident report →

Started May 14, 2025, 06:12 PM UTC· resolved May 14, 2025, 11:06 PM UTC

1. resolved May 14, 2025, 06:12 PM UTC

   Truckmate is currently experiencing a latency issue with PC*Miler Webservices that is currently impacting the ability for the Mileage Service to process jobs successfully. As a result, TruckMate Support is temporarily stopping all Mileage Services on your environment to ensure that no mileage jobs are lost. Once normal service is restored, we will automatically restart your Mileage Services and all jobs will catch up and process. Please do not attempt to restart your Mileage Service in the meantime as this will result in data loss. Status on PC*Miler can be found at https://status.trimblemaps.com/

2. investigating May 14, 2025, 06:12 PM UTC

   Truckmate is currently experiencing a latency issue with PC*Miler Webservices that is currently impacting the ability for the Mileage Service to process jobs successfully. As a result, TruckMate Support is temporarily stopping all Mileage Services on your environment to ensure that no mileage jobs are lost. Once normal service is restored, we will automatically restart your Mileage Services and all jobs will catch up and process. Please do not attempt to restart your Mileage Service in the meantime as this will result in data loss. Status on PC*Miler can be found at https://status.trimblemaps.com/

3. resolved May 14, 2025, 11:06 PM UTC

   The latency issue with PC*Miler Webservices has been mitigated. Mileage Services in TruckMate have resumed normal operation, and all queued mileage jobs have processed successfully. No action is needed from users. For continued updates on PC*Miler availability, please visit: https://status.trimblemaps.com/

4. resolved May 14, 2025, 11:06 PM UTC

   The latency issue with PC*Miler Webservices has been mitigated. Mileage Services in TruckMate have resumed normal operation, and all queued mileage jobs have processed successfully. No action is needed from users. For continued updates on PC*Miler availability, please visit: https://status.trimblemaps.com/

Read the full incident report →