Procore incident

Intermittent Application Latency and Errors

Minor Resolved View vendor source →

Procore experienced a minor incident on June 22, 2026 affecting Web Interface, lasting 10h 38m. The incident has been resolved; the full update timeline is below.

Started
Jun 22, 2026, 02:00 PM UTC
Resolved
Jun 23, 2026, 12:39 AM UTC
Duration
10h 38m
Detected by Pingoru
Jun 22, 2026, 02:00 PM UTC

Affected components

Web Interface

Update timeline

  1. investigating Jun 22, 2026, 02:00 PM UTC

    Our engineering team is investigating an issue causing some users to intermittently errors 5XX errors or long load times across the platform. We are actively working towards a solution. Additional updates will be provided as new information becomes available.

  2. identified Jun 22, 2026, 02:18 PM UTC

    Our engineering team has identified the cause for some users to experience intermittent errors and long load times when navigating the Procore platform. We are actively working towards a solution. Additional updates will be provided as new information becomes available.

  3. monitoring Jun 22, 2026, 02:46 PM UTC

    Our engineering team is actively monitoring an issue with a third-party cloud service provider that is resulting in intermittent errors for a portion of customers accessing and navigating the Procore platform. While we are tracking signs of stabilization, performance may remain intermittent as the provider works toward a resolution. If you encounter an error page or slow loading times, please refresh your browser or retry your action. Additional updates will be provided as new information becomes available.

  4. resolved Jun 23, 2026, 12:39 AM UTC

    During the incident, a subset of users experienced intermittent error pages and loading disruptions when attempting to access or navigate the platform. These performance fluctuations stemmed from an issue with a third-party cloud service provider. Our engineering team has verified that all network error signals have completely subsided, normal functionality has been fully restored, and this incident has been resolved.