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 Slack is down?

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

How many people have reported Slack issues today?

As of Oct 3, 2026 08:27 UTC, 0 users had reported issues with Slack in the previous 24 hours.

How can I report a Slack 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.

Communication

Is Slack down right now?

NormalOfficial status last polled Oct 3, 2026 08:25 UTCslack.com Official status page

Business messaging platform.

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

Is Slack down right now?

No. Slack 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 3, 2026 08:27 UTC

Normal

Slack is operating normally

As of Oct 3, 2026 08:27 UTC

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

Reports 24h

Last incident

Oct 1, 2026 19:03 UTC

Trend

0/15m

Baseline

9/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 Slack.

Incident days

No recorded incident

66h 10m

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 Slack. 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

2 incidents

Busiest day

66h 10m

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

Slack: vendor-reported incident on October 1 (tracked 6h 1m)

Oct 1, 01:01 PM → Oct 1, 07:03 PM · 6h 1m · high

Slack reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 6h 1m, from Thu, 01 Oct 2026 13:01:33 GMT to Thu, 01 Oct 2026 19:03:24 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

6h 1m

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

Oct 1, 01:01 PM
The vendor reported an incident on its own status page; PulseWatch began tracking it
Oct 1, 01:01 PM
Status updated: possible issue
Oct 1, 07:03 PM
PulseWatch closed the incident

Official updates

Oct 1, 01:01 PM
Slack reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

90.5%

90-day uptime

96.5%

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

Other communication 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

Slack: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 1:01:33 PM · 6h 1m

01:01 PM07:03 PM

Detection10/1/2026, 1:01:33 PM · 1d ago

Detected — high severity

ResolvedMedium