Trimble Viewpoint experienced a major incident on October 29, 2025 affecting ProContractor and ProContractor Cloud and 1 more component, lasting 8d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:13 PM UTC
We are aware that several Trimble applications are currently unavailable due to a global network issue affecting Microsoft Azure. This issue is impacting access to our Azure-hosted applications. Our teams are actively working with Microsoft to resolve the problem, and we will continue to provide updates on our status page as more information becomes available.
- investigating Oct 29, 2025, 04:34 PM UTC
We are continuing to investigate this issue.
- identified Oct 29, 2025, 05:00 PM UTC
Microsoft Azure continues to experience global DNS issues, which is affecting access to some of our applications that rely on their services. We continue to work closely with Microsoft on the issue.
- identified Oct 29, 2025, 05:01 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 29, 2025, 06:28 PM UTC
Microsoft has started rolling back the configuration changes that caused this issue. We are beginning to see recovery in some applications, though not all are fully restored yet. We will provide another update as additional services recover.
- identified Oct 29, 2025, 07:57 PM UTC
Microsoft has updated their timeline and now estimates that the rollback process may take up to an additional 4 hours to complete before full recovery is achieved. We will continue to monitor progress and share updates as more information becomes available.
- monitoring Oct 29, 2025, 08:45 PM UTC
We are seeing most applications in a recovered state at this time. We will continue update until all applications are fully recovered.
- monitoring Oct 30, 2025, 05:29 AM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 30, 2025, 07:13 PM UTC
We are continuing to monitor for any further issues.
- resolved Nov 06, 2025, 04:39 PM UTC
This incident has been resolved.