Issues with the Slack platform

Slack are continuing to work on re-sending the events that should have been delivered between 16:48 UTC yesterday and 06:45 UTC this morning. When we receive these events, we'll update incident timelines accordingly with any pinned messages.

Once Slack confirms that they've delivered all the events, we'll share an update here and resolve the incident.

Slack failed to deliver events to us between 16:48 UTC yesterday and 06:45 UTC this morning. Their status page mentions they are replaying these events, but we haven't yet seen this happening. As a result, you might see that things like emoji reactions (for pinning messages to the timeline, or creating follow-ups) didn't work, or that posting a link didn't result in an attachment being added.

Until we have a clearer picture from Slack, we would recommend re-trying these actions. We'll post an update here once we have an idea of whether Slack intend to re-send these events to us.

The Slack outage is now fully resolved.
Error rates returned to normal at around 00:20 UTC. Real-time events recovered around 0700 UTC, and have been received at a normal rate since then.
Please reach out via Slack or support@incident.io "support@incident.io": mailto:support@incident.io if you have any questions or concerns.

Slack’s latest update indicates that the recovery could take some time. We are still seeing a percentage of failures communicating with Slack’s API, and we’re not receiving real-time events from Slack. We are still keeping a close eye on the situation.

If you have a shared Slack channel with us for support, you can also reach us by emailing us at support@incident.io "support@incident.io": mailto:support@incident.io.

We're continuing to see a low level of errors from the Slack platform. Customers may well see delays in posting and updating messages, creating channels, and other operations within Slack.

The Slack outage is also affecting the real-time events that Slack send us, meaning we can't respond to messages in the channel, or handle emoji reactions. The /inc command is currently unaffected.

Our web dashboard remains unaffected and can be used to perform incident operations as usual.

Our internal support tool is also experiencing issues (due to the same Slack outage) so responses in customer Slack channels may also be delayed.

We're continuing to see a low level of errors from the Slack platform. Customers may well see delays in posting and updating messages, creating channels, and other operations within Slack.

Our web dashboard remains unaffected and can be used to perform incident operations as usual.

We are seeing issues with Slack again: incident channels may be slow to create, and messages are likely to be delayed. We are monitoring the situation.

We have now seen Slack's platform stabilise, and so we are resolving this incident. Delayed Slack messages and updates should now have been processed.

We're once again seeing increased error rates from the Slack platform. Customers are likely to still see delays in posting and updating messages, creating channels, and other operations within Slack.

Our web dashboard remains unaffected and can be used to perform incident operations as usual.

The error rate has decreased significantly, and our Slack app appears to be behaving mostly as expected.

We'll continue monitoring the situation, and update again when we're fully confident that the impact is over.

We're still seeing increased latency and error rates from the Slack platform. We are rolling out a change to change the frequency at which we retry operations to mitigate the impact. Customers are likely to still see delays in posting and updating messages, creating channels, and other operations within Slack.

We have identified increased error rates with Slack. Messages may be slow to send, and channels could be slow to create. Interactions with buttons and messages are likely to be slow, or fail completely. Our web dashboard remains fully operational.

Slack have reported this incident here: https://slack-status.com/2025-02/1b757d1d0f444c34