A Slack notification outage is affecting threads, group DMs

Some Slack users are finding that their notifications aren’t showing up on the platform this morning, or that their corresponding messages are harder to find than usual. A few of my colleagues are reporting similar issues on The Verge’s Slack channels, and I’ve been receiving repeated notifications for thread messages that I’ve already marked as read. The issues also seem to be affecting tags for other users — if a colleague hasn’t responded to your pings, DM them directly for now.

Slack is aware that “notifications may be missing for some users” and logged an incident report at 7:52AM ET today, later confirming that the issue is impacting threads. “We’re currently investigating the issue and we’ll be back when we have more information,” Slack announced on its status page. “We’re sorry for any interruption to your day.”

It’s unclear what’s causing the disruption to notifications or how many Slack users have been impacted. There’s a visible spike on Downdetector, but very few reports have been logged. 

For myself, at least, some notifications are coming through, but several minutes after a message has been sent. As of 10:10AM ET, Slack said that “other notifications should be working as expected, but threads may not be loading correctly.” It also logged a separate note that reports some users are having trouble adding new members to multi-person DM’s (group chats for up to nine people.)

Update, January 27th: Added more updates from Slack.