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 Acuity Scheduling is down?

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

How many people have reported Acuity Scheduling issues today?

As of Oct 4, 2026 16:04 UTC, 0 users had reported issues with Acuity Scheduling in the previous 24 hours.

How can I report a Acuity Scheduling 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 Acuity Scheduling down right now?

NormalOfficial status last polled Oct 4, 2026 15:03 UTCacuityscheduling.com Official status page

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

Is Acuity Scheduling down right now?

No. Acuity Scheduling 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 4, 2026 16:04 UTC

Normal

Acuity Scheduling is operating normally

As of Oct 4, 2026 16:04 UTC

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

Reports 24h

Last incident

Sep 21, 2026 20:45 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 Acuity Scheduling.

Incident days

No recorded incident

72h 1m

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 Acuity Scheduling. 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

72h 1m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Reliability

Detected by PulseWatch

30-day uptime

90.0%

90-day uptime

95.7%

Calculated from Acuity Scheduling'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 →

ResolvedHigh

Acuity Scheduling: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Acuity Scheduling or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 8:45:17 PM · 3d 0h

08:45 PM08:45 PM

Detection9/18/2026, 8:45:17 PM · 15d ago

Detected — high severity

ResolvedMedium