Slack: Slack Search Feature Disruption - Japan region
Affected components: Search
Timeline of updates
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
53bbaba61288e5cf…
Impact, status and times are the vendor’s own, as last archived. View on slack-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Slack, started 2026-05-01 01:50 UTC, resolved after 0 min, 1 update(s).
- Title
- Slack Search Feature Disruption - Japan region
- Vendor
- Slack
- Date
- URL
- https://rewindex.com/company/slack/incidents/1548
Slack profileRecent Slack incidentsAll outages on May 1, 2026Slack in May 2026MarkdownJSON