<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
        <channel>
            <title>Slack System Status</title>
            <link>https://dev.slack-status.com</link>
            <description>History of Slack System Status</description>
            <lastBuildDate>Tue, 18 Nov 2025 08:27:13 -0800</lastBuildDate>
                        <item>
                <title>Incident: Issues with login</title>
                <description>
                    This issue is now resolved. Users should be able to log in to Slack without encountering a blank page. We apologize for the disruption this may have caused to your day.
                </description>
                <pubDate>Tue, 18 Nov 2025 08:27:13 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-11/19eda44d909afb9d
                </link>
                <guid>
                    https://dev.slack-status.com/2025-11/19eda44d909afb9d
                </guid>
            </item>
                        <item>
                <title>Outage: Testing Templates</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: &amp;lt;What actions we&apos;ve taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the &quot;resolved&quot; status if needed&amp;gt;Scope: &amp;lt;Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted&amp;gt;Previous impact to end users: &amp;lt;Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.&amp;gt;Required resolution steps: &amp;lt;Any steps users should take for the issue to be resolved on their end&amp;gt;We apologize for any disruptions to your day.
                </description>
                <pubDate>Tue, 18 Nov 2025 08:39:19 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-11/cbd95cec4ae4ca51
                </link>
                <guid>
                    https://dev.slack-status.com/2025-11/cbd95cec4ae4ca51
                </guid>
            </item>
                        <item>
                <title>Incident: Trouble with search</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: Restarted the server.We apologize for any disruptions to your day.
                </description>
                <pubDate>Wed, 19 Nov 2025 05:21:40 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-11/96e4328d31e11478
                </link>
                <guid>
                    https://dev.slack-status.com/2025-11/96e4328d31e11478
                </guid>
            </item>
                        <item>
                <title>Incident: Trouble with Search</title>
                <description>
                    US region customers are currently experiencing search functionality issues due to Solr out-of-memory errors following a search index update. The incident affects search performance, with customers seeing either complete search failures or elevated latency with partial results.Teams are actively engaged and attempting to swap back to the previous stable index without force loading.We&apos;ll provide an update within 30 minutes, including further details on current actions being taken.Issue: The Engineering team became aware of a feature degradation impacting Search functionality. The issue was triggered following a scheduled update to the search index, which resulted in resource exhaustion and instability across the search cluster. Our team has provisioned maximum additional infrastructure capacity to stabilize the environment and is actively working to revert the system to the previous stable search index.Impact: During this time, the majority of customers in the US region may experience significant degradation. Symptoms include search queries &quot;hanging&quot; (timeouts), high latency, or search returning incomplete/partial results.&amp;nbsp;Next Update: Check the status page for updates. An update will be posted to the incident thread in 30 minutes, or sooner if additional information becomes available.
                </description>
                <pubDate>Tue, 02 Dec 2025 13:00:15 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-12/e867fbc7bb36852b
                </link>
                <guid>
                    https://dev.slack-status.com/2025-12/e867fbc7bb36852b
                </guid>
            </item>
                        <item>
                <title>Incident: Issues with login</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: &amp;lt;What actions we&apos;ve taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the &quot;resolved&quot; status if needed&amp;gt;Scope: &amp;lt;Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted&amp;gt;Previous impact to end users: &amp;lt;Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.&amp;gt;Required resolution steps: &amp;lt;Any steps users should take for the issue to be resolved on their end&amp;gt;We apologize for any disruptions to your day.
                </description>
                <pubDate>Wed, 10 Dec 2025 11:45:50 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-12/44d6e855d1552384
                </link>
                <guid>
                    https://dev.slack-status.com/2025-12/44d6e855d1552384
                </guid>
            </item>
                        <item>
                <title>Incident: Issues with login</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: Issue has been resolved. Temporary network outage.Scope: All users on NA180Previous impact to end users: Users unable to login from login.salesforce.comRequired resolution steps: noneWe apologize for any disruptions to your day.
                </description>
                <pubDate>Wed, 10 Dec 2025 11:45:15 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-12/2b97f0cb8dab21f0
                </link>
                <guid>
                    https://dev.slack-status.com/2025-12/2b97f0cb8dab21f0
                </guid>
            </item>
                        <item>
                <title>Incident: Test Incident - TestTestTest</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: The Slack Engineering team determined that the primary database became unavailable but failed to gracefully migrate traffic to the secondary partition. Our team performed a manual failover of traffic to the secondary partition.Scope: 100% of users across all regions, intermittent failures to load or create Slack Canvases.Previous impact to end users: During the impact period, users across all regions may have experienced intermittent failures to load or create Slack Canvases.Required resolution steps:&amp;nbsp;You may need to restart your Slack client to restore functionality.We apologize for any disruptions to your day.
                </description>
                <pubDate>Wed, 10 Dec 2025 11:48:04 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-12/ad1515e459cd6abc
                </link>
                <guid>
                    https://dev.slack-status.com/2025-12/ad1515e459cd6abc
                </guid>
            </item>
                        <item>
                <title>Incident: This is a new test incident</title>
                <description>
                    This issue is now resolved for all users.Current status and recent actions taken: A recent change was rolled back to resolve this incident.Scope: Only users who had initiated huddles in the past 2 hours were affected.Previous impact to end users: Users may not be able to leave an initiated huddle.&amp;nbsp;Required resolution steps: No additional resolution steps are required.We apologize for any disruptions to your day.
                </description>
                <pubDate>Wed, 10 Dec 2025 11:47:22 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2025-12/647034f15b97cf00
                </link>
                <guid>
                    https://dev.slack-status.com/2025-12/647034f15b97cf00
                </guid>
            </item>
                        <item>
                <title>Incident: New EDIT - Increased HTTP 5xx errors resulting in trouble accessing Canvases</title>
                <description>
                    Update #1
                </description>
                <pubDate>Tue, 17 Feb 2026 13:48:20 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2026-02/1833b43a6686f5c5
                </link>
                <guid>
                    https://dev.slack-status.com/2026-02/1833b43a6686f5c5
                </guid>
            </item>
                        <item>
                <title>Incident: Test Incident 2</title>
                <description>
                    Test Details&amp;nbsp;
                </description>
                <pubDate>Tue, 17 Feb 2026 13:49:27 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2026-02/df6ed2be3a69ce2e
                </link>
                <guid>
                    https://dev.slack-status.com/2026-02/df6ed2be3a69ce2e
                </guid>
            </item>
                        <item>
                <title>Incident: TEST SLACK DM not working as expected</title>
                <description>
                    We&apos;re investigating a new incident.Current impact to end users: Slack DM issuesWe&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
                </description>
                <pubDate>Tue, 24 Feb 2026 08:30:44 -0800</pubDate>
                <link>
                https://dev.slack-status.com/2026-02/c5b66c1819fe670f
                </link>
                <guid>
                    https://dev.slack-status.com/2026-02/c5b66c1819fe670f
                </guid>
            </item>
                    </channel>
    </rss>
