Procore incident
Application Degradation: Upstream Errors and Login Unavailability
Procore experienced a critical incident on July 6, 2026 affecting Login and Web Interface and 1 more component, lasting 2h 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 06, 2026, 12:51 PM UTC
Our engineering team is investigating an issue causing upstream errors when navigating the platform and errors when attempting to login to Procore. We are actively working towards a solution. Additional updates will be provided as new information becomes available.
- investigating Jul 06, 2026, 12:52 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 06, 2026, 01:25 PM UTC
Our engineering team has implemented a solution to remediate intermittent upstream connect errors and login unavailability affecting some customers when accessing the platform. We are monitoring the situation to ensure a complete resolution. Additional updates will be provided as new information becomes available.
- monitoring Jul 06, 2026, 01:51 PM UTC
Our engineering team has observed that this impact was a result of a Third-party vendor issue. We are continuing to investigate and ensure impact is fully mitigated and will not recur. Additional updates will be provided as information becomes available.
- monitoring Jul 06, 2026, 02:20 PM UTC
Our engineering team is observing long load times for some users on the Project Home page as a follow-up from the earlier event. We are actively working to mitigate this experience. Additional updates will be provided as new information becomes available.
- monitoring Jul 06, 2026, 02:44 PM UTC
We are observing normal behavior on the Procore Web Application. Our engineering team will continue to monitor this incident. Additional updates will be provided as new information becomes available.
- resolved Jul 06, 2026, 03:28 PM UTC
During the incident, users experienced issues navigating the Procore Web Application. Our engineering team has restored normal functionality after making adjustments to mitigate impact from our Third-party Vendor. This incident has been resolved.