Skip to content
Slack · Apps and SaaSMay 1, 2026, 01:50 UTC

Slack Search Feature Disruption - Japan region

MinorNetworkUpdated 17h ago
May 1, 01:50 UTCMay 1, 01:50 UTC
Duration
0m
Impact
Minor
Root cause
Network
Slack, 90 days
7 incidents
Affected
Search
Status page

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

  1. 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

Also caused by network

All
StartedIncidentDuration
Sep 1901:36 UTCElevated errors in Ashburn, VA (IAD)Cloudflare0m
Sep 1411:59 UTCIncreased wait times for macOS jobsCircleCI1h
Sep 410:57 UTCIncreased errors on High Performance Edge Network - FRA RegionNetlify0m
Sep 214:18 UTCUpstream network issuesFly.io1h 39m
Sep 116:11 UTCService degradation in GCP us-central-1ClickHouse19m
Sep 114:44 UTCMultiple products in us-central1-b are experiencing network service degradation.Google Cloud4h 8m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.