Trimble Connect Outage History

Started Oct 06, 2026, 02:49 PM UTC· resolved Oct 06, 2026, 07:04 PM UTC

1. monitoring Oct 06, 2026, 02:49 PM UTC

   We are seeing disruptions in our <API Name> API and are currently investigating the issue.

2. investigating Oct 06, 2026, 02:49 PM UTC

   We are seeing disruptions in our API and are currently investigating the issue.

3. monitoring Oct 06, 2026, 06:38 PM UTC

   A fix has been implemented; we are closely monitoring system performance.

4. monitoring Oct 06, 2026, 06:38 PM UTC

   A fix has been implemented; we are closely monitoring system performance.

5. monitoring Oct 06, 2026, 07:04 PM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

6. resolved Oct 06, 2026, 07:04 PM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →

Started Sep 30, 2026, 08:39 PM UTC· resolved Sep 30, 2026, 10:47 PM UTC

1. monitoring Sep 30, 2026, 08:39 PM UTC

   We are seeing disruptions relating to file uploads and are currently investigating the issue.

2. investigating Sep 30, 2026, 08:39 PM UTC

   We are seeing disruptions relating to file uploads and are currently investigating the issue.

3. monitoring Sep 30, 2026, 09:17 PM UTC

   We have identified the cause of the issue and are remediating now. We apologize for the inconvenience this has caused

4. investigating Sep 30, 2026, 09:17 PM UTC

   We have identified the cause of the issue and are remediating now. We apologize for the inconvenience this has caused

5. monitoring Sep 30, 2026, 09:51 PM UTC

   Trimble Connect team continue to investigate and are working towards a resolution. We apologize for the inconvenience this has caused.

6. investigating Sep 30, 2026, 09:51 PM UTC

   Trimble Connect team continue to investigate and are working towards a resolution. We apologize for the inconvenience this has caused.

7. monitoring Sep 30, 2026, 10:27 PM UTC

   Trimble Connect team continue to investigate and are working towards a resolution as soon as possible. We apologize for the inconvenience this has caused.

8. investigating Sep 30, 2026, 10:27 PM UTC

   Trimble Connect team continue to investigate and are working towards a resolution as soon as possible. We apologize for the inconvenience this has caused.

9. monitoring Sep 30, 2026, 10:42 PM UTC

   We are implementing and validating a fix. We expect service to restore imminently in the North America region. We are continuing to deploy additional fixes for other regions.

10. investigating Sep 30, 2026, 10:42 PM UTC

    We are implementing and validating a fix. We expect service to restore imminently in the North America region. We are continuing to deploy additional fixes for other regions.

11. monitoring Sep 30, 2026, 10:47 PM UTC

    Service has now been fully restored to all regions. Please accept our apologies for the inconvenience this caused.

12. resolved Sep 30, 2026, 10:47 PM UTC

    Service has now been fully restored to all regions. Please accept our apologies for the inconvenience this caused.

Read the full incident report →

Started Aug 28, 2026, 08:45 AM UTC· resolved Aug 28, 2026, 09:23 AM UTC

1. monitoring Aug 28, 2026, 08:45 AM UTC

   We are seeing disruptions in the Open 3D Model with Public Link in the Component Group Web App Service and are currently investigating the issue.

2. investigating Aug 28, 2026, 08:45 AM UTC

   We are seeing disruptions in the Open 3D Model with Public Link in the Component Group Web App Service and are currently investigating the issue.

3. monitoring Aug 28, 2026, 09:23 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

4. resolved Aug 28, 2026, 09:23 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →

Started May 24, 2026, 01:30 AM UTC· resolved May 24, 2026, 05:13 AM UTC

1. monitoring May 24, 2026, 01:30 AM UTC

   All Trimble Connect services will be temporarily unavailable on May 24, 2026 (Sunday) , for approximately 2 hour due to scheduled maintenance. Downtime Window: 01:30 AM to 03:30 AM UTC Impact: All Trimble Connect systems, applications, and APIs will be inaccessible during this period. Please plan your workflows accordingly. We apologize for the inconvenience and appreciate your understanding as we perform these necessary updates.

2. monitoring May 24, 2026, 03:30 AM UTC

   The scheduled maintenance has been completed.

Read the full incident report →

Started Apr 19, 2026, 08:47 PM UTC· resolved Apr 20, 2026, 05:32 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Feb 23, 2026, 12:46 AM UTC· resolved Feb 23, 2026, 01:00 AM UTC

1. monitoring Feb 23, 2026, 12:46 AM UTC

   Hello Trimble CDE Users, Our team is responding to the alerts and investigating a disruption in CDE - GraphQL -Quadri Cloud AU service. We sincerely apologize for the service interruption and will provide an update soon about the progress of a resolution to this issue. Regards Trimble CDE

2. identified Feb 23, 2026, 12:46 AM UTC

   Hello Trimble CDE Users, Our team is responding to the alerts and investigating a disruption in CDE - GraphQL -Quadri Cloud AU service. We sincerely apologize for the service interruption and will provide an update soon about the progress of a resolution to this issue. Regards Trimble CDE

3. monitoring Feb 23, 2026, 01:00 AM UTC

   Hello Trimble CDE Users, Our team has determined that the issue is now fully resolved. Thank you again for your patience during the incident. Regards Trimble CDE

4. resolved Feb 23, 2026, 01:00 AM UTC

   Hello Trimble CDE Users, Our team has determined that the issue is now fully resolved. Thank you again for your patience during the incident. Regards Trimble CDE

Read the full incident report →

Started Feb 20, 2026, 03:52 PM UTC· resolved Feb 20, 2026, 04:03 PM UTC

1. monitoring Feb 20, 2026, 03:52 PM UTC

   Hello Trimble CDE Users, Our team is responding to the alerts and investigating a disruption in GraphQL - Quadri - EU service. We sincerely apologize for the service interruption and will provide an update soon about the progress of a resolution to this issue. Regards Trimble CDE

2. identified Feb 20, 2026, 03:52 PM UTC

   Hello Trimble CDE Users, Our team is responding to the alerts and investigating a disruption in GraphQL - Quadri - EU service. We sincerely apologize for the service interruption and will provide an update soon about the progress of a resolution to this issue. Regards Trimble CDE

3. monitoring Feb 20, 2026, 04:03 PM UTC

   Hello Trimble CDE Users, Our team has determined that the issue is now fully resolved. Thank you again for your patience during the incident. Regards Trimble CDE

4. resolved Feb 20, 2026, 04:03 PM UTC

   Hello Trimble CDE Users, Our team has determined that the issue is now fully resolved. Thank you again for your patience during the incident. Regards Trimble CDE

Read the full incident report →

Started Dec 10, 2025, 11:06 PM UTC· resolved Dec 11, 2025, 12:54 AM UTC

1. monitoring Dec 10, 2025, 11:06 PM UTC

   We are currently experiencing issues with Public APIs in multiple regions. We are investigating and will provide an update as soon as possible. We apologize for the inconvenience caused.

2. investigating Dec 10, 2025, 11:06 PM UTC

   We are currently experiencing issues with Public APIs in multiple regions. We are investigating and will provide an update as soon as possible. We apologize for the inconvenience caused.

3. monitoring Dec 10, 2025, 11:31 PM UTC

   We have located the issue on the Australia region and are working on a fix. We continue to investigate the impact on the other regions. We apologize for the inconvenience this continues to cause.

4. investigating Dec 10, 2025, 11:31 PM UTC

   We have located the issue on the Australia region and are working on a fix. We continue to investigate the impact on the other regions. We apologize for the inconvenience this continues to cause.

5. monitoring Dec 11, 2025, 12:44 AM UTC

   A fix has been implemented for the issue within the Australia region; we are closely monitoring performance. We apologize for the inconvenience caused.

6. monitoring Dec 11, 2025, 12:44 AM UTC

   A fix has been implemented for the issue within the Australia region; we are closely monitoring performance. We apologize for the inconvenience caused.

7. monitoring Dec 11, 2025, 12:54 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

8. resolved Dec 11, 2025, 12:54 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →

Started Dec 10, 2025, 05:47 PM UTC· resolved Dec 11, 2025, 05:21 PM UTC

1. monitoring Dec 10, 2025, 05:47 PM UTC

   We are seeing delays in the Trimble Connect Processing Service, which is responsible for uploaded 3D model conversions and are currently investigating the issue.

2. investigating Dec 10, 2025, 05:47 PM UTC

   We are seeing delays in the Trimble Connect Processing Service, which is responsible for uploaded 3D model conversions and are currently investigating the issue.

3. monitoring Dec 10, 2025, 11:13 PM UTC

   A fix has been implemented for this issue but we continue to experience latency in some regions as the backlog of executions continues to clear. We have increased resources to process the backlog as soon as possible. We apologize for the inconvenience caused. We will provide an update once the backlog has completely cleared.

4. monitoring Dec 10, 2025, 11:13 PM UTC

   A fix has been implemented for this issue but we continue to experience latency in some regions as the backlog of executions continues to clear. We have increased resources to process the backlog as soon as possible. We apologize for the inconvenience caused. We will provide an update once the backlog has completely cleared.

5. monitoring Dec 11, 2025, 05:21 PM UTC

   Backlog has been cleared and normal service has resumed. We apologize for any inconvenience caused. Thanks for your patience.

6. resolved Dec 11, 2025, 05:21 PM UTC

   Backlog has been cleared and normal service has resumed. We apologize for any inconvenience caused. Thanks for your patience.

Read the full incident report →

Started Oct 20, 2025, 07:59 AM UTC· resolved Oct 21, 2025, 01:29 AM UTC

1. monitoring Oct 20, 2025, 07:59 AM UTC

   Hi All , There is a Major Outage in AWS North Virginia Region( us-east-1). Multiple services hosted on the region got impacted. AWS acknowledged the issue and working on it. Please see the AWS Status page for your reference. AWS Status Page Affected Services:

2. investigating Oct 20, 2025, 07:59 AM UTC

   Hi All , There is a Major Outage in AWS North Virginia Region( us-east-1). Multiple services hosted on the region got impacted. AWS acknowledged the issue and working on it. Please see the AWS Status page for your reference. AWS Status Page Affected Services:

3. monitoring Oct 20, 2025, 09:39 AM UTC

   Latest Update from the AWS side Increased Error Rates and Latencies Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information.

4. monitoring Oct 20, 2025, 09:39 AM UTC

   Latest Update from the AWS side Increased Error Rates and Latencies Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information.

5. monitoring Oct 20, 2025, 04:45 PM UTC

   Latest Update from the AWS side Oct 20 9:13 AM PDT We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT.

6. monitoring Oct 20, 2025, 04:45 PM UTC

   Latest Update from the AWS side Oct 20 9:13 AM PDT We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT.

7. monitoring Oct 20, 2025, 05:05 PM UTC

   Latest Update from the AWS side Oct 20 10:03 AM PDT We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely. We will provide an update by 10:45 AM PDT.

8. monitoring Oct 20, 2025, 05:05 PM UTC

   Latest Update from the AWS side Oct 20 10:03 AM PDT We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely. We will provide an update by 10:45 AM PDT.

9. monitoring Oct 20, 2025, 05:07 PM UTC

   Summary for the AWS Outage: Our Cloud Service provider AWS experienced a major outage in the US-EAST-1 region affecting multiple services, including EC2, Lambda, and DynamoDB. Mitigation steps have been applied, and most services have recovered. Full restoration and validation are in progress. We appreciate your patience and will continue to provide updates.

10. monitoring Oct 20, 2025, 05:07 PM UTC

    Summary for the AWS Outage: Our Cloud Service provider AWS experienced a major outage in the US-EAST-1 region affecting multiple services, including EC2, Lambda, and DynamoDB. Mitigation steps have been applied, and most services have recovered. Full restoration and validation are in progress. We appreciate your patience and will continue to provide updates.

11. monitoring Oct 20, 2025, 05:45 PM UTC

    Latest Update from the AWS side Oct 20 10:38 AM PDT Our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. We are applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside.

12. monitoring Oct 20, 2025, 05:45 PM UTC

    Latest Update from the AWS side Oct 20 10:38 AM PDT Our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. We are applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside.

13. monitoring Oct 20, 2025, 06:30 PM UTC

    Latest Update from the AWS side Oct 20 11:22 AM PDT Our mitigations to resolve launch failures for new EC2 instances continue to progress and we are seeing increased launches of new EC2 instances and decreasing networking connectivity issues in the US-EAST-1 Region. We are also experiencing significant improvements to Lambda invocation errors, especially when creating new execution environments (including for Lambda@Edge invocations). We will provide an update by 12:00 PM PDT.

14. monitoring Oct 20, 2025, 06:30 PM UTC

    Latest Update from the AWS side Oct 20 11:22 AM PDT Our mitigations to resolve launch failures for new EC2 instances continue to progress and we are seeing increased launches of new EC2 instances and decreasing networking connectivity issues in the US-EAST-1 Region. We are also experiencing significant improvements to Lambda invocation errors, especially when creating new execution environments (including for Lambda@Edge invocations). We will provide an update by 12:00 PM PDT.

15. monitoring Oct 21, 2025, 12:14 AM UTC

    Latest Update from the AWS side Oct 20 3:53 PM PDT Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary.

16. monitoring Oct 21, 2025, 12:14 AM UTC

    Latest Update from the AWS side Oct 20 3:53 PM PDT Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary.

17. monitoring Oct 21, 2025, 01:29 AM UTC

    Our Cloud provider outages has been resolved. Thanks for your patience.

18. resolved Oct 21, 2025, 01:29 AM UTC

    Our Cloud provider outages has been resolved. Thanks for your patience.

Read the full incident report →

Started Aug 23, 2025, 12:51 AM UTC· resolved Sep 30, 2026, 10:23 PM UTC

1. monitoring Aug 23, 2025, 12:51 AM UTC

   We are seeing disruptions in the Service and are currently investigating the issue. Get Current User Information Get Current User Information User Information User Information

2. monitoring Aug 23, 2025, 06:58 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →

Started Aug 17, 2025, 01:30 AM UTC· resolved Sep 30, 2026, 08:59 PM UTC

1. monitoring Aug 17, 2025, 01:30 AM UTC

   There will be maintenance break on all Trimble Connect regions on Sun August 17th, 2025, 1:30 - 2:30 AM UTC. During this time, we expect temporary slowness in operations related to 3D Views. Features that involve creating views, listing views, opening views and updating views (including all views embedded in ToDos and BCF Topics), may experience longer response times than normally, but other than that will operate normally. After the maintenance has completed, the response times will return back to normal. We apologize for the inconvenience.

2. monitoring Aug 17, 2025, 02:30 AM UTC

   The scheduled maintenance has been completed.

Read the full incident report →

Started May 04, 2025, 09:00 AM UTC· resolved Aug 28, 2026, 09:09 AM UTC

1. monitoring May 04, 2025, 09:00 AM UTC

   There will be a maintenance break in the Trimble Connect Australia region on Sun May 4th, 2025, 09:00-12:00 UTC. During this time, all Connect services in the Australia region are inoperational. This update is a mandatory part of our platform maintenance. We apologize for the inconvenience.

2. monitoring May 04, 2025, 12:00 PM UTC

   The scheduled maintenance has been completed.

Read the full incident report →

Started Jan 13, 2025, 10:10 AM UTC· resolved Aug 22, 2026, 10:27 AM UTC

1. monitoring Jan 13, 2025, 10:10 AM UTC

   We are seeing disruptions in our public API(Europe) below services and are currently investigating the issue. Folder Item Listing Organizer Service Overall Region Health Project Information Project Listing Project Search Property Set Service System Search ToDo Listing User Information User Listing

2. monitoring Jan 13, 2025, 11:20 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →

Started Nov 17, 2024, 06:21 AM UTC· resolved May 22, 2026, 10:57 AM UTC

1. monitoring Nov 17, 2024, 06:21 AM UTC

   We are seeing performance degradation in the Open 3D Model with Public Link and are currently investigating the issue.

2. monitoring Nov 17, 2024, 09:06 AM UTC

   The issue causing the disruptions has been resolved. Thanks for your patience.

Read the full incident report →