Slack App service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for app.slack.com. Compare the regional responses with the problem you see in Slack App.
Find Slack App help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
The app.slack.com entrypoint does not prove that your workspace messages or huddles work.
The checker above requests app.slack.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Slack App action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For Slack, compare the application, integration and status entrypoints separately: Slack API status check, Slack Status status check, Slack status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse messaging checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Select workspace messaging, huddles or the exact feature involved.
Open the website in your browser and compare it with the result above.
Open Slack App help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Workspace, channel/huddle action, client/device, network type and exact error time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Slack App.
These are troubleshooting comparisons, not claims that Slack App is currently experiencing a particular incident.
Compare the same workspace and channel in the web and desktop clients.
For a huddle problem, distinguish joining from microphone/speaker failure and compare device permissions and another participant.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Slack App seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open app.slack.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Slack App issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Slack App support.
Run the app.slack.com check and compare its original timestamps and responses with your actual error. The app.slack.com entrypoint does not prove that your workspace messages or huddles work.
Use the community buttons on this page to share whether the service works for you. For help from Slack App, use the official help/reporting resource linked above. Select workspace messaging, huddles or the exact feature involved.
Compare the same workspace and channel in the web and desktop clients. For a huddle problem, distinguish joining from microphone/speaker failure and compare device permissions and another participant.
Workspace, channel/huddle action, client/device, network type and exact error time.