May 7, 08:49 UTC
Identified - Cloudflare is aware of, and investigating, an issue with accessing the 1.1.1.1 website. Further detail will be provided as more information becomes available.

THIS IS A SCHEDULED EVENT May 13, 15:00 - 20:00 UTC

May 7, 07:28 UTC
Scheduled - We will be performing scheduled maintenance in SYD (Sydney) datacenter on 2026-05-13 between 15:00 and 20:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

THIS IS A SCHEDULED EVENT May 12, 05:00 - 13:00 UTC

May 7, 06:22 UTC
Scheduled - We will be performing scheduled maintenance in YUL (Montréal) datacenter on 2026-05-12 between 05:00 and 13:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

From 12:07 PM PST until 1:30 PM PST on January 14, 2026, some users were unable to add payment methods to their Slack billing pages.A recent backend change to our payment processing configuration unexpectedly added a new required field, causing errors when attempting to add the methods. We reversed the field requirement, resolving the issue for all users.

This issue is now resolved.Current status and recent actions taken: Affected users may have experienced performance issues in Slack.Scope: This issue did not affect any specific region, but a small percentage of users may have been impacted globally.Previous impact to end users: The majority of errors were retired successfully, but small number of users may have experienced errors when performing various tasks in Slack. Required resolution steps: No steps required.We apologize for any disruptions to your day

Starting around 11:50 AM PST until around 3:15 PM PST on January 8, 2026, some users experienced a variety of performance issues in Slack, such as significant delays or a total inability to send and receive messages, load channels, or view threads.We traced this to a routine backend configuration job which unexpectedly caused some services to reload or become unresponsive. To mitigate the impact, we promptly paused the problematic job and restarted the affected services, resolving the issue for all users.

Between 1:05 PM and 5:26 PM PST on December 23, 2025, some users may have encountered a "Something's fishy!" error when attempting to load message threads.We traced this to a backend job that consumed an excessive amount of system resources, leading to a portion of a database becoming unresponsive. To mitigate, we optimized the resource allocation for these background tasks and restarted the affected database segments, resolving the issue for affected users.

Starting at around 7:00 AM until 12:10 PM PST on December 15, 2025, some users may have experienced issues triggering or using workflows containing the Jira connector or the Jira Cloud app in Slack.An upstream provider encountered an issue that resulted in trouble using the Jira connector. Once the upstream provider resolved the issue, the app returned to normal functionality.

From 7:12 AM to 4:50 PM PST on December 8, 2025, some users encountered a "Something's fishy!" error when loading  threads or experienced delays or a blank screen when loading specific channels in Slack.We identified the cause as a recent configuration change that triggered unexpected rate limiting on backend components responsible for fetching message data for threads. We reverted the problematic change, resolving the issue for all users.

Beginning around 7:45 PM PST until around 8:11 PM PST on December 4, 2025, some users experienced slow or incomplete searches in Slack.A backend configuration change caused an unexpected spike in queries to a search-related database service. We reversed the backend configuration, which resolved the impact to the search feature. While we managed any temporarily unindexed content, users were able to perform searches in Slack as expected, but some content may have been temporarily missing.We closely monitored internal health metrics for a period of time to ensure the issue was fully resolved by December 5, 2025 at around 1:10 PM PST.

Between 11:51 AM PST and 9:10 PM PST on December 2, 2025, some users experienced issues with the Slack search functionality. Affected users may have encountered a range of symptoms, including the display of incorrect search results, missing messages, noticeably degraded or slow performance, and in some cases, a complete failure to load any search content.We traced this back to a temporary, unexpected surge in resource demand that impacted a critical backend service responsible for processing search results. We increased resources for this service to mitigate impact and stabilize the search functionality, however, during this time, a backlog of unindexed content was created. This backlog prevented content from appearing in search results for some users.To resolve this, we began re-processing the accumulated backlog of unindexed content back into our search systems. Once the indexing process was complete, all messages and content shared during the initial impact window became fully searchable, resolving the issue for all users.

Between 2:08 PM PST and 2:34 PM PST on December 4, 2025, some users may have experienced 500 errors when trying to open a Canvas. Current status and recent actions taken: We have resolved the issue by reverting a web cache configuration setting that was causing the disruption. Users should no longer be experiencing trouble connecting to or loading Canvases in Slack.Scope: This issue did not affect any specific region, but a percentage of users may have been impacted globally.Previous impact to end users: Users experienced issues loading and accessing Canvases.Required resolution steps: NoneThis issue is now resolved for all users. We’re sorry for the disruption we brought to your day.

Starting around 1:45 AM PST until 4:30 AM PST on November 28, 2025, some users encountered connectivity issues, including difficulty accessing and loading their workspaces and receiving "Server error" messages.We traced this issue to a backend database service reaching unexpected capacity limits, which led to a spike in error rates and request timeouts. We immediately increased capacity limits for the affected databases, restoring full functionality and service stability to all impacted services.

Following a period of monitoring and with user validation now received, this issue has been resolved. We apologize for any inconvenience this issue may have caused. 

Between 10:10 AM PST and 10:25 AM PST on November 10, 2025, some users may have temporarily been unable to connect to Slack or experienced a degree of latency when attempting to use features such as huddles, workflows, or message delivery.We traced this back to a spike in traffic to core backend Slack functions. This traffic temporarily overwhelmed a subset of backend components, leading to brief increase in connection failures. The traffic spike subsided and connectivity was restored for all users by around 10:25 AM PST. To mitigate the risk of reoccurrence, we adjusted backend traffic routing rules to relieve affected systems and continued closely monitoring our health metrics. We determined the issue was fully resolved and necessary measures were in place by 12:30 PM PST.We continue to implement additional measures to reduce the likelihood of this recurring in the future.

Between 1:00 AM and 8:00 AM PST on November 12, 2025, some users experienced delays when attempting to use AI features, including message summaries and search.An upstream provider experienced latency with their services, resulting in backend errors for some Slack AI functions. To mitigate the issue, we temporarily routed traffic to a separate version. After the upstream provider resolved their issue, affected Slack AI functionality was successfully restored.

Beginning around 11:00 AM PST and lasting until 2:24 PM PST on November 8, 2025, some enterprise users experienced a blank page when attempting to sign into Slack. Non-enterprise users would have successfully been able to sign into Slack.We traced this issue to a configuration error tied to the workspace directory page (the page users are typically directed to after logging in), which caused incorrect redirects. During the incident, affected users may have successfully accessed Slack by navigating directly to https://app.slack.com as a temporary workaround.To quickly mitigate the impact, we rolled Slack back to a confirmed working version, resolving the issue for all users.

THIS IS A SCHEDULED EVENT May 19, 17:00 - 23:00 UTC

May 6, 08:18 UTC
Scheduled - We will be performing scheduled maintenance in ICN (Seoul) datacenter on 2026-05-19 between 17:00 and 23:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

THIS IS A SCHEDULED EVENT May 13, 16:00 - 21:00 UTC

May 6, 03:48 UTC
Scheduled - We will be performing scheduled maintenance in MEL (Melbourne) datacenter on 2026-05-13 between 16:00 and 21:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

THIS IS A SCHEDULED EVENT May 12, 09:00 - 11:30 UTC

May 6, 14:34 UTC
Scheduled - We will be performing scheduled maintenance in PHX (Phoenix) datacenter on 2026-05-12 between 09:00 and 11:30 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.