<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
        <id>https://status.slack.com</id>
        <link rel="alternate" type="text/html" href="https://dev.slack-status.com" />
        <link rel="self" type="application/atom+xml" href="https://dev.slack-status.com/feed/atom" />
        <title>Slack System Status</title>
        <updated>2026-02-17T13:48:20-08:00</updated>
        <author>
            <name>Slack</name>
        </author>
                <entry>
            <id>
                https://dev.slack-status.com/2026-02/1833b43a6686f5c5
            </id>
            <published>2026-02-17T13:45:29-08:00</published>
            <updated>2026-02-17T13:48:20-08:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-02/1833b43a6686f5c5" />
            <title>Incident: New EDIT - Increased HTTP 5xx errors resulting in trouble accessing Canvases</title>
            <summary>
                Update #1
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;1:45pm PST&lt;/small&gt;
                We are aware of an issue where users may observe increased HTTP 5xx errors in the form of different failure scenarios across Slack services. We are investigating the root cause and a well defined impacted experience with the highest priority, and apologize for any inconvenience this is causing for users. EDIT EDIT EDIT!
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;1:48pm PST&lt;/small&gt;
                Update #1
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-02/df6ed2be3a69ce2e
            </id>
            <published>2026-02-17T13:49:27-08:00</published>
            <updated>2026-05-28T00:39:59-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-02/df6ed2be3a69ce2e" />
            <title>Incident: Test Incident 2</title>
            <summary>
                TEST TEST TEST 88888
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;1:49pm PST&lt;/small&gt;
                Test Details&amp;nbsp;
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;12:39am PDT&lt;/small&gt;
                TEST TEST TEST 88888
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-02/c5b66c1819fe670f
            </id>
            <published>2026-02-24T08:30:44-08:00</published>
            <updated>2026-02-24T08:30:44-08:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-02/c5b66c1819fe670f" />
            <title>Incident: TEST SLACK DM not working as expected</title>
            <summary>
                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.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;8:30am PST&lt;/small&gt;
                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.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/8167aba49c749279
            </id>
            <published>2026-06-04T11:19:31-07:00</published>
            <updated>2026-06-04T11:19:31-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/8167aba49c749279" />
            <title>Incident: Trouble with search</title>
            <summary>
                We’re investigating an issue impacting search. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:19am PDT&lt;/small&gt;
                We’re investigating an issue impacting search. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/c7bc424a4520beb2
            </id>
            <published>2026-06-04T11:25:03-07:00</published>
            <updated>2026-06-04T11:25:03-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/c7bc424a4520beb2" />
            <title>Incident: Trouble connecting to Slack</title>
            <summary>
                Users may be unable to connect to Slack or send messages at the moment. 

We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:25am PDT&lt;/small&gt;
                Users may be unable to connect to Slack or send messages at the moment. 

We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/84eb20635844097f
            </id>
            <published>2026-06-04T11:26:41-07:00</published>
            <updated>2026-06-04T11:26:41-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/84eb20635844097f" />
            <title>Incident: Widespread connectivity issues</title>
            <summary>
                Many customers are experiencing trouble connecting to Slack. We&apos;re very sorry for the disruption. We&apos;re actively investigating and we&apos;ll provide another update within 30 minutes.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:26am PDT&lt;/small&gt;
                Many customers are experiencing trouble connecting to Slack. We&apos;re very sorry for the disruption. We&apos;re actively investigating and we&apos;ll provide another update within 30 minutes.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/653a93276c91b483
            </id>
            <published>2026-06-04T11:28:32-07:00</published>
            <updated>2026-06-04T11:28:32-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/653a93276c91b483" />
            <title>Incident: Trouble with search</title>
            <summary>
                We’re investigating an issue impacting search. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:28am PDT&lt;/small&gt;
                We’re investigating an issue impacting search. We’re on the case and will provide another update once we have more details to share. Thank you for your patience in the meantime.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/710d9d22c424e053
            </id>
            <published>2026-06-04T11:33:45-07:00</published>
            <updated>2026-06-04T11:33:45-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/710d9d22c424e053" />
            <title>Incident: Trouble connecting to Slack</title>
            <summary>
                Users may be unable to connect to Slack or send messages at the moment. 

We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:33am PDT&lt;/small&gt;
                Users may be unable to connect to Slack or send messages at the moment. 

We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/768cba60de129fac
            </id>
            <published>2026-06-05T01:23:48-07:00</published>
            <updated>2026-06-05T01:23:48-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/768cba60de129fac" />
            <title>Incident: Users cannot switch Workspaces</title>
            <summary>
                Users cannot switch Workspaces and instead see a spinner in the left-hand menu. We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;1:23am PDT&lt;/small&gt;
                Users cannot switch Workspaces and instead see a spinner in the left-hand menu. We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/aa196cdebbb34e6c
            </id>
            <published>2026-06-05T10:57:09-07:00</published>
            <updated>2026-06-05T11:03:12-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/aa196cdebbb34e6c" />
            <title>Incident: Trouble connecting to Slack</title>
            <summary>
                TEST TEST TEST - RESOLVED
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;10:57am PDT&lt;/small&gt;
                Users may be unable to connect to Slack or send messages at the moment. 

We apologize for the disruption. We are working to resolve this as our highest priority, and we&apos;ll provide another update in 30 minutes.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;10:59am PDT&lt;/small&gt;
                TEST TEST TEST - Update 2
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;11:01am PDT&lt;/small&gt;
                TEST TEST TEST - RESOLVED
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/edea60eb2734b215
            </id>
            <published>2026-06-05T11:07:21-07:00</published>
            <updated>2026-06-05T11:10:09-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/edea60eb2734b215" />
            <title>Incident: Issues with login</title>
            <summary>
                &amp;nbsp;TEST TEST - RESOLVED (EDITED)
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:07am PDT&lt;/small&gt;
                Some users may be unable to log into Slack. We apologize for the inconvenience and will continue sharing updates as they become available.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;11:08am PDT&lt;/small&gt;
                TEST TEST - Update 2
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;11:10am PDT&lt;/small&gt;
                &amp;nbsp;TEST TEST - RESOLVED (EDITED)
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/5dc95beffddb29e4
            </id>
            <published>2026-06-08T11:30:01-07:00</published>
            <updated>2026-06-08T11:30:48-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/5dc95beffddb29e4" />
            <title>Incident: Issues with login</title>
            <summary>
                We&apos;ve implemented a directory change to move traffic. Thanks.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;11:30am PDT&lt;/small&gt;
                Some users may be unable to log into Slack. We apologize for the inconvenience and will continue sharing updates as they become available.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;11:30am PDT&lt;/small&gt;
                We&apos;ve implemented a directory change to move traffic. Thanks.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/ed7ac110ac12047e
            </id>
            <published>2026-06-09T21:21:50-07:00</published>
            <updated>2026-06-09T21:21:50-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/ed7ac110ac12047e" />
            <title>Incident: John Lee Test</title>
            <summary>
                10 June Test
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;9:21pm PDT&lt;/small&gt;
                10 June Test
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/ab5e18d9cfec0494
            </id>
            <published>2026-06-09T21:23:24-07:00</published>
            <updated>2026-06-09T21:51:43-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/ab5e18d9cfec0494" />
            <title>Incident: John Lee Test2</title>
            <summary>
                a second note for 1425
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;9:23pm PDT&lt;/small&gt;
                Ooops - we are still working on it.&amp;nbsp;
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;9:51pm PDT&lt;/small&gt;
                a second note for 1425
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/b5b59b5e2da70ad1
            </id>
            <published>2026-06-09T21:26:05-07:00</published>
            <updated>2026-06-09T21:34:51-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/b5b59b5e2da70ad1" />
            <title>Incident: System-wide service disruption (template) - John lee</title>
            <summary>
                A number of Slack features are currently unavailable, including loading conversations, sending messages, uploading files, and using search.

We are addressing this as our highest priority, and will provide an update within 30 minutes. Thank you for bearing with us in the meantime.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;9:26pm PDT&lt;/small&gt;
                A number of Slack features are currently unavailable, including loading conversations, sending messages, uploading files, and using search.

We are addressing this as our highest priority, and will provide an update within 30 minutes. Thank you for bearing with us in the meantime.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/38d400c2e6045702
            </id>
            <published>2026-06-09T21:38:36-07:00</published>
            <updated>2026-06-09T21:47:41-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/38d400c2e6045702" />
            <title>Incident: Performance Degradation – Middle East (Dubai) Region</title>
            <summary>
                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.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;9:38pm PDT&lt;/small&gt;
                We&apos;re investigating a new incident.Current impact to end users: &amp;lt;Describe the issue and how it manifests for end users, including details like which specific functionality or features are impacted, and any error messages or other symptoms a user may encounter.&amp;gt;We&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;9:47pm PDT&lt;/small&gt;
                &amp;lt;Summarize any notable changes from the previous update OR if there aren&apos;t changes from the previous update, specifically state that here.&amp;gt;Current status and actions being taken: &amp;lt;What actions we&apos;re currently taking in our investigation or remediation efforts; are we trying to identify the cause, have identified the cause, preparing to ship a fix, etc.&amp;gt;Estimated time to resolution: &amp;lt;Rough timeframe in which impact might be resolved, if we have an estimate.&amp;gt;Scope: &amp;lt;Roughly what percentage of users are impacted; which categories of users, regions, devices, etc. are impacted; absolute number of errors and/or impacted users can be included ONLY IF sending email to ONE customer&amp;gt;We&apos;ll continue to provide updates every 30 minutes until the impact is resolved for all users.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;9:47pm PDT&lt;/small&gt;
                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.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/cc2978035e4aca1e
            </id>
            <published>2026-06-11T03:11:58-07:00</published>
            <updated>2026-06-11T03:30:58-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/cc2978035e4aca1e" />
            <title>Incident: Slack Threads Not Loading</title>
            <summary>
                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.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;3:11am PDT&lt;/small&gt;
                We&apos;re investigating a new incident.Current impact to end users: Slack users are unable to load Threads.We&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;3:28am PDT&lt;/small&gt;
                &amp;lt;Summarize any notable changes from the previous update OR if there aren&apos;t changes from the previous update, specifically state that here.&amp;gt;Current status and actions being taken: &amp;lt;What actions we&apos;re currently taking in our investigation or remediation efforts; are we trying to identify the cause, have identified the cause, preparing to ship a fix, etc.&amp;gt;Estimated time to resolution: &amp;lt;Rough timeframe in which impact might be resolved, if we have an estimate.&amp;gt;Scope: &amp;lt;Roughly what percentage of users are impacted; which categories of users, regions, devices, etc. are impacted; absolute number of errors and/or impacted users can be included ONLY IF sending email to ONE customer&amp;gt;Current impact to end users: &amp;lt;Describe the symptoms impacted users may experience, which functionality or features are affected, relevant error messages, etc.&amp;gt;Known workarounds: &amp;lt;Any steps users could take to continue using Slack or impacted features before the issue is fully resolved&amp;gt;We&apos;ll continue to provide updates every 30 minutes until the impact is resolved for all users.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;3:30am PDT&lt;/small&gt;
                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.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/0a57df32942814ba
            </id>
            <published>2026-06-11T03:26:58-07:00</published>
            <updated>2026-06-11T03:39:08-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/0a57df32942814ba" />
            <title>Incident: Huddle issues in Slack</title>
            <summary>
                We&apos;re investigating a new incident.Current impact to end users:&amp;nbsp;Some users cannot load HuddlesWe&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;3:26am PDT&lt;/small&gt;
                We&apos;re investigating a new incident.Current impact to end users:&amp;nbsp;Some users cannot load HuddlesWe&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/a94fbd4e89936743
            </id>
            <published>2026-06-11T05:43:08-07:00</published>
            <updated>2026-06-11T05:45:56-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/a94fbd4e89936743" />
            <title>Incident: Multiple slack users cannot see canvas or messages</title>
            <summary>
                This issue is now resolved for all users.Current status and recent actions taken: TEST&amp;nbsp;Scope:&amp;nbsp;All CustomersPrevious impact to end users TEST&amp;nbsp;Required resolution steps: TESTWe apologize for any disruptions to your day.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;5:43am PDT&lt;/small&gt;
                We&apos;re investigating a new incident.Current impact to end users:&amp;nbsp;Several Slack users are unable to view Canvas or messages.We&apos;ll provide an update within 30 minutes including further details on scope and actions being taken to resolve the issue.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;5:44am PDT&lt;/small&gt;
                Our work on this issue is still ongoing.Current status and actions being taken: &amp;nbsp;A recent update patch has been identified as the cause of the issue and a rollback or fix forward in under discussionWe&apos;ll provide another update in 30 minutes until the impact is resolved for all users.
                &lt;/p&gt;
                                &lt;p&gt;
                &lt;small&gt;5:45am PDT&lt;/small&gt;
                This issue is now resolved for all users.Current status and recent actions taken: TEST&amp;nbsp;Scope:&amp;nbsp;All CustomersPrevious impact to end users TEST&amp;nbsp;Required resolution steps: TESTWe apologize for any disruptions to your day.
                &lt;/p&gt;
                            </content>
        </entry>
                <entry>
            <id>
                https://dev.slack-status.com/2026-06/62ec522bb1d310d2
            </id>
            <published>2026-06-11T05:47:22-07:00</published>
            <updated>2026-06-11T05:47:22-07:00</updated>
            <link rel="alternate" type="text/html" href="https://dev.slack-status.com/2026-06/62ec522bb1d310d2" />
            <title>Incident: Some users experiencing trouble sending or receiving messages</title>
            <summary>
                Some users may be experiencing delays or failures when sending or receiving messages, including DMs and threads. We&apos;re sorry for the disruption and are actively investigating. We&apos;ll share another update within 30 minutes.
            </summary>
            <content type="html">
                                &lt;p&gt;
                &lt;small&gt;5:47am PDT&lt;/small&gt;
                Some users may be experiencing delays or failures when sending or receiving messages, including DMs and threads. We&apos;re sorry for the disruption and are actively investigating. We&apos;ll share another update within 30 minutes.
                &lt;/p&gt;
                            </content>
        </entry>
            </feed>
