Monday June 10, 2019

Incident

Calls are not working for some customers

Issue Summary:

On June 10th 2019 from 9:20am a.m. PDT - 1:33 p.m. PDT, all Slack Call features were unavailable for customers. A change occurred during a system update that made certain credentials unavailable to Slack servers, which caused the outage. Once the correct credentials were provided, all customers could successfully make calls again in Slack. At 1:33 p.m. PDT the issue was resolved.

1:30 PM PST

Great news! Calls are working again. We're very sorry for the disruption and appreciate you standing by while we got this fixed up.

2:19 PM PST

We've identified the problem and we’re working on a fix to get Calls working again. More details to come as they become available.

1:28 PM PST

Our team is still looking into the trouble folks are having with Calls. We'll continue to update you on our progress.

12:46 PM PST

We're still exploring possible fixes for this issue. We apologize for the disruption and we hope to be back to normal soon.

12:16 PM PST

We're still trying to pin down the root cause of this Calls issue. We hope to bring some good news soon and appreciate your patience.

11:45 AM PST

Some people may be seeing issues with Slack Calls. We’re on the case and will be back with more details soon. Thank you for your patience in the meantime.

11:14 AM PST

Services affected

Calls

Status

Resolved

Incident

Trouble loading channels

Issue Summary:

On 10 June, 2019 at 9:40 a.m. PDT, we deployed a version to our desktop app that caused a sudden increase in the number of connections to our servers. These connections were rate-limited by Slack’s servers in order to protect themselves. During this time, some customers were unable to load their workspaces, including channels and messages. We launched an investigation, but the system recovered soon after, allowing people to reconnect to Slack. At 10:56 a.m. PDT the issue was resolved.

10:52 AM PST

We're happy to report that we're in the clear and everybody should be able to access their channels again. Sorry for the disruption, and thank you for bearing with us while we worked to fix things up.

10:59 AM PST

Some folks may be having trouble loading their channels in Slack. We’re currently investigating and will have more information shortly. Thank you for your patience.

10:31 AM PST

Services affected

Connections

Status

Resolved

Incident

We’re investigating an issue with the Outlook Calendar Integration

Issue Summary:

On June 10, 2019 at 11:30 a.m. PDT, we received an unexpected increase in the number of attempts to sign up for the Outlook Calendar app. This caused an outage of the application, resulting in degraded functionality and some new sign-ups failing. At 2:22 p.m. PDT, we increased the load capacity. This resolved the issue and everything was running smoothly again by 2:50 p.m. PDT. Going forward, we will review our scaling policy to ensure this doesn’t happen again.

8:43 AM PST

Good news: Outlook calendar integrations are working properly for everyone again. We're sorry for any inconvenience here, and appreciate you sticking with us.

3:00 PM PST

Our engineers are still working on a fix for the `/ocal` integration. Unfortunately, interaction with the app is also broken in addition to the trouble with installation. Thanks for your patience as we get things back to normal!

1:33 PM PST

Some users are seeing `Server Error` page when trying to install the Outlook Calendar App. We are aware and will update as we know more. Thanks for bearing with us!

1:03 PM PST

Services affected

Apps/Integrations/APIs

Status

Resolved

Incident

Users are unable to create workspaces if the name includes CJK characters

Issue Summary:

On June 7, 2019, we rolled out an update to the workspace creation flow that contained a bug. This resulted in customers receiving an error message when creating a new team if the workspace name contained any Chinese, Japanese, or Korean characters. On June 10, 2019 at 3:12 a.m. PDT, we deployed the fix and customers were able to create new teams again.

3:41 PM PST

The problem whereby users were unable to create workspaces successfully when using CJK characters in the workspace name, has been resolved. Thank you for your patience. If you are still having trouble in this area, please drop us a line at feedback@slack.com.

3:21 AM PST

We have identified the cause of the trouble users are facing when creating a workspace using CJK characters. We are actively working on a resolution. Thanks for sticking with us.

2:37 AM PST

We are still working to resolve the issue whereby users are unable to create workspaces when using CJK characters. For now, those impacted can work around this problem by creating a temporary workspace name excluding CJK characters, which can then be changed when this problem has been resolved.

2:08 AM PST

Users are currently facing trouble creating new Slack workspaces, if the workspace name includes CJK characters. We are on the case, and apologise for the inconvenience.

1:37 AM PST

Some people may be having an issue with Slack. We’re currently investigating and will have more information shortly. Thank you for your patience.

1:26 AM PST

Services affected

Workspace/Org Administration

Status

Resolved

Incident

We are seeing some issues with webhooks

We've determined unusual activity with webhooks was a minor issue and are handling these on a case by case basis. Thanks for your understanding!

2:58 PM PST

Some workspaces may be receiving permission errors when attempting to post to incoming webhooks. We are aware of the problem and are actively working to fix it.

1:59 PM PST

Services affected

Apps/Integrations/APIs

Status

Resolved