Thursday February 21, 2019
Incident
Errors when accessing Slack
Technical Summary:
On February 21 between 7:00am PT to 9:20am PT, some users experienced connectivity issues with Slack.
The connectivity issue arose from a misconfiguration that was discovered by our engineers. At 8:45am PT a change in the configuration led to users being able to successfully connect to Slack again.
We’re hard at work on scoping preventative measures to ensure this doesn’t happen again in the future.
8:50 PM PST
The issue some folks were running into with Slack failing to load has now been resolved. Thank you for your patience while we sorted that out.
9:20 AM PST
Slack is not loading for a small number of people. We're sorry for the trouble - our team is working to find the cause and fix the issue.
5:52 AM PST
We're currently looking into the reports of Slack not loading correctly for some people. Apologies for the disruption.
4:50 AM PST
Services affected
Connectivity
Messaging
Status
Incident
Incident
Delayed push notifications
Technical Summary:
On February 21st at 4:22PM PST, we deployed a database change, which caused unexpected delays for processes such as notifications and link/image previews in Slack. The problem was identified and corrected, however a backlog of notifications and previews had formed in the meantime. We continued to monitor this backlog after the fix was implemented, and by 5:20PM PST, all functionality returned to normal.
6:52 PM PST
We're seeing that push notifications are arriving on time once again. However, if you're still experiencing troubles, please let us know at feedback@slack.com.
5:26 PM PST
Push notifications may be running slower than expected. We’re investigating and will have an update shortly.
5:15 PM PST
Services affected
Notifications
Status
Incident