Slack Search Feature Disruption - Japan region
Final update
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.
Timeline
- Resolved · May 1, 01:50 UTC
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.
More from Slack
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1211:04 UTC | Some customers experiencing blurry image previews and download issues | minor | 8h 56m |
| Sep 1000:34 UTC | Trouble loading Workspace-level Apps & Workflows settings page is returning blank pages | minor | 2h 40m |
| Aug 1321:21 UTC | Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled | minor | 32d 1h |
| Aug 622:22 UTC | Trouble Using Search Bar For Some Admins | minor | 2h 44m |
| Jul 2802:13 UTC | Feature Degradation Affecting the Receipt of Emails in Slack | minor | 1h 30m |
| Jul 2408:22 UTC | Issue sending messages to channels via certain Workflows | minor | 2h 24m |
Also caused by network
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1901:36 UTC | Elevated errors in Ashburn, VA (IAD) | none | 0m | |
| Sep 1411:59 UTC | Increased wait times for macOS jobs | minor | 1h | |
| Sep 410:57 UTC | Increased errors on High Performance Edge Network - FRA Region | minor | 0m | |
| Sep 214:18 UTC | Upstream network issues | minor | 1h 39m | |
| Sep 116:11 UTC | Service degradation in GCP us-central-1 | none | 19m | |
| Sep 114:44 UTC | Multiple products in us-central1-b are experiencing network service degradation. | major | 4h 8m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.