Provider
SlackIncident detail
Issue loading activity feed in Slack
Issue loading activity feed in Slack
Timeline window
Jan 23, 2026, 5:03 AM UTC to Jan 29, 2026, 5:16 PM UTC
Sponsored placement
Google AdSense placeholder
This slot is reserved for future AdSense placement. It stays as a non-invasive placeholder until a client ID and slot ID are configured.
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
Investigating
We’re investigating a Feature Degradation affecting a number of users. Some users may be unable to load their activity feed and may encounter the following error message: “Something’s fishy! Slack can’t seem to load your activity feed. ”We’ll provide updates as soon as possible, as more information becomes available. We apologize for any inconvenience this may cause.
Jan 23, 2026, 5:03 AM UTC
Monitoring
Our work on this issue is still ongoing. Current status and actions being taken: We have identified the source of the ongoing issue related to activity feed and message functionality and are actively working on a fix. We'll provide another update as soon as it becomes available until the impact is resolved for all users.
Jan 23, 2026, 5:43 AM UTC
Monitoring
This issue is now resolved for all users. Current status and recent actions taken: The issue affecting the activity feed and message functionality has been resolved. We’ve taken steps to prevent this from happening again, and all systems are now operating normally. Previous impact to end users: During the impact, some users experienced issues with the activity feed and messaging, including degraded performance and errors. We apologize for any disruptions to your day.
Jan 23, 2026, 6:47 AM UTC
Resolved
Starting 8:27 PM PST until 10:01 PM PST on January 22, 2026, some users experienced issues loading activity feed in Slack. We traced this to a backend resource that unexpectedly hit capacity limits. This resulted in activity feed processes no longer serving traffic. We promptly adjusted the configuration and increased capacity limits for the backend resource, resolving the issue for all affected users.
Jan 29, 2026, 5:16 PM UTC