Global IT infrastructure status

SLACK

🟠 Partial outage

Incident: Slack Search Feature Disruption - Japan region

Identified

Started
2026-05-01 01:50 UTC
143 days ago
Last update
2026-05-01 01:50 UTC
143 days ago
Running for
143d 22h

Timeline

  1. 01 May · 01:50 UTC 🟠 Identified rss

    At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack.We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster was being recovered.As of 00:45 UTC, May 1, 2026, Slack Search functionality is fully operational.We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. 

  2. 01 May · 01:50 UTC 🟠 Identified rss

    At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack.We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster was being recovered.As of 00:45 UTC, May 1, 2026, Slack Search functionality is fully operational.We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. 

Source

Official Slack status — view original incident ↗

IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.