Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled
InvestigatingPossible issues
Started · 2026-08-14 15:49 UTC
Official incident updatePossibly — Slack may have issues
slack.com may be experiencing issues such as errors or slow responses. The latest automated check was run 2026-08-14 17:20 UTC from primary location. This is not a confirmed global outage.
Possible issues
- Current status
- Possible issues
- Last check
- Checked every minute
- Last 24 hours
- 48.485%
Current issue started 1h 31m ago
Latest 2026-08-14 17:20 UTC · Primary location
1 incident, 1h 31m down
- Official status
- Possible issues
- Our check
- Operational
- Active incident
- Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled
- Last outage
- 2026-08-14
- Response time
- 189 ms
- User reports
- Normal
None today
Current incident
Response time
Latest 118 ms
Loading response-time chart…
Uptime
Availability from independent checks, with recorded incidents and downtime in each window.
Today
48.485%
1 incident, 1h 31m down
Last 7 days
48.485%
1 incident, 1h 31m down
Last 30 days
48.485%
1 incident, 1h 31m down
Last 365 days
48.485%
1 incident, 1h 31m down
Latest Slack incidents
Recorded outages with duration and start time.
Last recorded 2026-08-14 15:49 UTC
| Incident | Duration | Started |
|---|---|---|
Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled Investigating | Ongoing | 2026-08-14 15:49 UTC |
How this status checker works
Who's Down Today monitors Slack independently of the company that runs it. We send reachability checks from our primary location every minute and record response time, HTTP errors, and timeouts.
When Slack publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Frequently asked questions
Is Slack down right now?
- Possibly — Slack may have issues. Who's Down Today currently shows Slack as possible issues. Check the live status, recent incidents, and response-time chart on this page. If the site works for you, the issue may be regional or limited to some features.
Is Slack down for everyone or just me?
- A confirmed issue on this page means our sources detected a problem, but that does not always mean every user is affected. Some incidents are regional, affect only some features, or appear as slow loading instead of a full outage.
What should I do if slack.com is up but I still cannot access it?
- Try opening slack.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Slack outage.
How does Who's Down Today check if Slack is down?
- We combine independent HTTP reachability checks with public status information where it exists. When Slack publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
What does a Slack outage mean?
- An outage on this page means recorded incidents or failed checks indicated that Slack was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.
Can this page tell me the root cause of a Slack outage?
- Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Slack's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.
How do I report an issue with Slack?
- Use the report form on this page if Slack looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.