PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Procore is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Procore. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Procore issues today?

As of Oct 12, 2026 17:31 UTC, 0 users had reported issues with Procore in the previous 24 hours.

How can I report a Procore outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Procore down right now?

NormalOfficial status last polled Oct 12, 2026 17:28 UTCprocore.com Official status page

Are you on the Procore team and see something inaccurate? Report it to us. We respond within one business day.

Is Procore down right now?

No. Procore has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 17:31 UTC

Normal

Procore is operating normally

As of Oct 12, 2026 17:31 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 16, 2026 18:02 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Procore.

Incident days

No recorded incident

8h 22m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Procore. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

8h 22m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Procore outage on September 16 — 8h 22m disruption

Sep 16, 09:40 AM → Sep 16, 06:02 PM · 8h 22m · medium

An incident affecting the Procore service was detected on September 16, 2026. The disruption was identified through automated monitoring signals. Service was fully restored on September 16, 2026, at 18:02 UTC.

Duration

8h 22m

tracked by PulseWatch

Impact

The Procore service experienced a medium-severity disruption lasting 8 hours and 22 minutes. This incident was detected via automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded.

Incident timeline

Sep 16, 09:40 AM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 16, 09:40 AM
Status updated: possible issue
Sep 16, 06:02 PM
Signals cleared — incident resolved

Official updates

Sep 16, 09:40 AM
Procore status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.8%

90-day uptime

94.0%

Calculated from Procore's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Procore: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/16/2026, 9:40:51 AM · 8h 22m

09:40 AM06:02 PM

Detection9/16/2026, 9:40:51 AM · 26d ago

Detected — medium severity

ResolvedMedium