<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:keystone.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://keystone.instatus.com/history.atom"/>
  <title>keystone Status - Incident history</title>
  <updated>2026-01-22T19:34:00.000+00:00</updated>
  <author>
    <name>keystone</name>
  </author>
  
<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s401nmi1pcedmhc1qm</id>
  <published>2026-01-22T19:34:00.000+00:00</published>
  <updated>2026-01-22T19:34:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s401nmi1pcedmhc1qm"/>
  <title>Microsoft 365 Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>19:34:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Microsoft is reporting a major outage involving Exchange, Microsoft 365 Admin Center and security related portals.  Email is being affected at this time..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>13:13:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  Microsoft is reporting that all systems are operational this morning.  Please contact us if you continue to experience issues..</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>20:50:16</var> GMT+0</small><br /><strong>Investigating</strong> -
  User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.

More info: Users may be receiving a &quot;451 4.3.2 temporary server issue&quot; error message when attempting to send or receive email through Outlook.
 
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Collecting message traces.
- Searching within SharePoint Online and/or Microsoft OneDrive.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams.
- Receiving presence or location information in Microsoft Teams.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
 
Current status: While we&#039;ve restored the affected infrastructure to a heathy state, further load balancing is required to mitigate persistent impact. We&#039;ve identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.
 
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
 
Root cause: A portion of dependent service infrastructure in the North America region isn&#039;t processing traffic as expected.
 
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC.</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>20:33:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  Microsoft has identified the root cause:

Root cause: A portion of dependent service infrastructure in the North America region isn&#039;t processing traffic as expected.

Next update by: Thursday, January 22, 2026, at 11:00 PM UTC.</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>20:32:13</var> GMT+0</small><br /><strong>Investigating</strong> -
  Below is the current status from Microsoft:

Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
 
Current status: We&#039;ve identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting our load balancing processes and general service availability. We&#039;re working to restore this infrastructure to a heathy state and rebalance the service traffic to achieve recovery.
 
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
 
Next update by: Thursday, January 22, 2026, at 10:00 PM UTC

More information can be found at status.cloud.microsoft..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s401nji1pcfxa7f06s</id>
  <published>2025-12-02T19:30:00.000+00:00</published>
  <updated>2025-12-02T19:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s401nji1pcfxa7f06s"/>
  <title>Delay in receiving tickets submitted via e-mail</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Email Processing</p>
    <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing a delay in receiving tickets submitted via email. If you need help immediately, please contact us by phone or via Keystone Support Chat..</p>
<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>23:44:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incoming email issue has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s401nfi1pc2qyq6bd0</id>
  <published>2025-11-18T13:38:00.000+00:00</published>
  <updated>2025-11-18T13:38:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s401nfi1pc2qyq6bd0"/>
  <title>Cloudflare Global Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:38:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Cloudflare is experiencing a global outage impacting a large number of internet sites and platforms. 

We are monitoring it, here: https://www.cloudflarestatus.com/
&quot;Investigating - Cloudflare is experiencing an internal service degradation. Some services may be intermittently impacted. We are focused on restoring service. We will update as we are able to remediate. More updates to follow shortly.
Nov 18, 2025 - 11:48 UTC&quot;.</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>16:16:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  Cloudflare is reporting that the issue has been fully resolved. Please reach out to us if you are experiencing any remaining issues..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>16:16:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Issues are partially resolved. We are still detecting issues with some platforms. We will continue monitoring..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s401nbi1pc788teqmq</id>
  <published>2025-10-09T18:57:00.000+00:00</published>
  <updated>2025-10-09T18:57:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s401nbi1pc788teqmq"/>
  <title>Microsoft 365 outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>18:57:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are experiencing issues with Microsoft 365.  Microsoft has posted the following to their official status page:

We’re investigating reports of issues accessing Microsoft 365 services. More details can be found in the Microsoft 365 admin center Service Health Dashboard under MO1169016..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>19:49:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  Microsoft is stating that the issue is resolved:

We’ve identified that a portion of network infrastructure in North America was misconfigured, which caused traffic across the region to become unhealthy. We’ve taken mitigating action to rebalance traffic in the affected infrastructure, and we’ve observed service health improve to normal levels across all impacted services..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>19:08:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  Update from Microsoft:

While we’re observing service health recovering, we’ve received additional reports of issues accessing the Microsoft 365 admin center related to this issue. We expect these issues to resolve as service health improves.

This quick update is designed to give the latest information on this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301n8i1pcd4v02gbl</id>
  <published>2025-09-17T16:30:00.000+00:00</published>
  <updated>2025-09-17T16:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301n8i1pcd4v02gbl"/>
  <title>Inbound call issues from Verizon Wireless</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> FluentStream Voice</p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have reports of calling issues affecting inbound calls from several providers, including Verizon Wireless, across KeyStone Voice.
Our provider is currently working on a resolution..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>20:22:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our provider has let us know that this issue has been resolved, and calls should be working properly at this time.
If you continue to have issues, please give us a call at 423.464.6424.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301n5i1pcdyps8ssv</id>
  <published>2025-07-16T14:21:00.000+00:00</published>
  <updated>2025-07-16T14:21:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301n5i1pcdyps8ssv"/>
  <title>Barracuda Email Filtering Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>14:21:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Barracuda Email Gateway Defense is experiencing issues - Please see the latest info below:

Update - A fix has been implemented, and mail flow capacity is returning to normal levels.
Jul 16, 2025 - 14:10 UTC
Identified - We have identified an issue impacting mail flow in the US, DE, CA, and AU regions. We are working to resolve the issue. User interface accessibility may also be affected by this issue.
Jul 16, 2025 - 13:41 UTC.</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>14:24:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  Monitoring - The issue has been resolved. We are monitoring the system.
Jul 16, 2025 - 15:05 UTC
Update - Mail flow has recovered and is back to normal in the UK, DE, CA, and AU regions. Capacity is back to normal for the US region, and deferral rates are improving. User interface accessibility may continue to be affected by this issue.
Jul 16, 2025 - 14:51 UTC.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301n2i1pcfczedxe1</id>
  <published>2025-07-10T17:46:00.000+00:00</published>
  <updated>2025-07-10T17:46:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301n2i1pcfczedxe1"/>
  <title>Spectrum Outage - Cleveland, Bradley County</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Spectrum</p>
    <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>17:46:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Spectrum Cable is experiencing an outage in the Cleveland/Bradley County TN. 
This may be power or weather related. Spectrum is aware and will provide updates..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>19:05:13</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are seeing this resolved from our end. Please let us know if you are still having any issues..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301myi1pchacj636f</id>
  <published>2025-07-10T14:45:00.000+00:00</published>
  <updated>2025-07-10T14:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301myi1pchacj636f"/>
  <title>Microsoft Outlook Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>14:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The following issue has been announced by Microsoft. Currently, there are issues being experienced with Outlook across multiple customers. We are including the notice below:

&quot;Title: Users may be unable to access their mailbox using any connection methods

User impact: Users may be unable to access their mailbox using any connection methods.

More info: Impacted connection methods include, but may not be limited to:

- Outlook.com

- Outlook Mobile

- Outlook desktop client

Current status: We&#039;re continuing to apply the configuration changes to fix the underlying problem and completing additional validation efforts to ensure authentication components are properly configured. In parallel to the current deployment of the configuration change fix, we&#039;re reviewing options to leverage an expedited deployment methodology in regions which are experiencing the highest levels of impact to provide the most effective relief where possible.

Start time: Wednesday, July 9, 2025, at 10:20 PM UTC

Next update by: Thursday, July 10, 2025, at 4:30 PM UTC&quot;.</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>18:13:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  Title: Users may be unable to access their mailbox using any connection methods

User impact: Users may have been unable to access their mailbox using any connection methods.

More info: Impacted connection methods include, but may not be limited to:

- Outlook.com

- Outlook Mobile

- Outlook desktop client

Current status: The configuration change has fully saturated in all affected infrastructure. We&#039;ve verified that the service is healthy by monitoring telemetry and confirming resolution with previously affected customers.

Start time: Wednesday, July 9, 2025, at 10:20 PM UTC

End time: Thursday, July 10, 2025, at 5:25 PM UTC

This is the final update for this incident..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>18:12:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  Here is the latest update from Microsoft:

&quot;Title: Users may be unable to access their mailbox using any connection methods

User impact: Users may be unable to access their mailbox using any connection methods.

More info: Impacted connection methods include, but may not be limited to:

- Outlook.com

- Outlook Mobile

- Outlook desktop client

Current status: We’ve begun a broad expedited deployment of the configuration change across all affected infrastructure. We expect most impacted users will experience relief within the next two hours, as the fix saturates the environment. We’re closely monitoring service health telemetry to ensure the recovery continues as expected. We understand how impactful incidents of this type can be, and we&#039;re continuing to open any additional workstreams to expedite recovery and restore availability.

Start time: Wednesday, July 9, 2025, at 10:20 PM UTC

Next update by: Thursday, July 10, 2025, at 6:30 PM UTC&quot;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mui1pca3oa2imy</id>
  <published>2025-06-12T19:17:00.000+00:00</published>
  <updated>2025-06-12T19:17:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mui1pca3oa2imy"/>
  <title>Google Global Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Googe Workspace</p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating a global outage impacting a number of google services including Gmail, Google Calendar, Drive, Docs, Meet, etc. 

We are monitoring the situation and will update when Google provides an update
https://www.google.com/appsstatus/dashboard/.</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:45:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  Google has posted full resolution of this issue..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:19:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  Google has confirmed resolution except for Google Meet.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mqi1pc6tw19ue7</id>
  <published>2025-04-15T18:00:00.000+00:00</published>
  <updated>2025-04-15T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mqi1pc6tw19ue7"/>
  <title>KeyStone Voice Call Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> FluentStream Voice</p>
    <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received notification from a subset of customers that they are experiencing quality issues with their voice services.
We are working now to assess the spread of the reported issues and are working with the provider to find a cause.

If you are currently experiencing voice issues, please let us know..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>11:57:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our provider has let us know that they have resolved the issue within the Lumen network. If you are still experiencing issues, please call and let us know.

Thank you!.</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>20:29:26</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received information from our Provider:

&quot;Earlier this morning, we became aware of an issue within the Lumen network that impacted audio on inbound and outbound calls. As of 1:40PM EST, Lumen was removed from our outbound routing to alleviate calling issues and take an alternative route. Inbound calling is still affected by this. At this time, we are working with Lumen and escalating the Lumen ticket to higher level management to obtain a faster resolution.

Thank you for your patience!&quot;

We&#039;ll update as soon as we get more info from our provider. Outbound calling should no longer be affected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mni1pc1y405rys</id>
  <published>2025-03-01T21:33:00.000+00:00</published>
  <updated>2025-03-01T21:33:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mni1pc1y405rys"/>
  <title>MS365 Global Outages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>21:33:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving many reports of users unable to login or use email. 
This appears to be transient, and many users are reporting that they initially had issues, but are now able to use the platform normally. 

If you are still having issues please reach out to our offices or open a support ticket. We have opened a ticket with Microsoft directly and will update here as we know more it&#039;s so stupid.</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>14:17:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  This has been resolved by Microsoft. If you are still experiencing any issues, please reach out to our Service Desk for support..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mji1pc13mfef8i</id>
  <published>2025-02-24T16:59:00.000+00:00</published>
  <updated>2025-02-24T16:59:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mji1pc13mfef8i"/>
  <title>Random Workstation System Performance Reports</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Platform</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:59:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving widespread reports of system performance issues.

We are attempting to correlate where this impact could be originating. 

If you are experiencing this issue, please open a ticket from your machine, or give us a call so we can log it to gather more data. 

We will update this incident as often as we have news/info..</p>
<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>21:39:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:03:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  In most of the instances we have seen, allowing the computer to sit long enough to finish a back-end processing has fixed a number of these reports. 

If you are still experiencing this issue, please let our service desk know!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mgi1pcb1zu1u6g</id>
  <published>2024-11-25T17:34:00.000+00:00</published>
  <updated>2024-11-25T17:34:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mgi1pcb1zu1u6g"/>
  <title>Microsoft Login Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>17:34:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received reports of Microsoft logins being slow or unavailable.
Microsoft is aware and is working on a fix:

Users may be unable to access or use some Microsoft 365 services and features

Issue ID: MO941162
Affected services: Exchange Online, Microsoft 365 suite, Microsoft Power Automate in Microsoft 365, Microsoft Purview, Microsoft Teams, SharePoint Online, Universal Print
Status: Service degradation
Issue type: Incident
Start time: Nov 24, 2024, 9:54 PM EST

More info
The affected scenarios are as follows:

Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)

Users may be unable to use the following features within Microsoft Teams:
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. 
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.

Users may experience the following issues with Microsoft Purview:
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations. 

Users may be unable to export content or set and view labels within Microsoft Fabric.

Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.

Users may be unable to use the search feature within SharePoint Online.

Users may be unable to perform the following actions within Microsoft Defender for Office365:
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.

Users leveraging Universal Print may experience the following issues: 
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.

Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.

Users may be unable to access their bookings within Microsoft Bookings.

Users may be unable to use some Microsoft Copilot features including:
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.

Scope of impact
Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.

Preliminary root cause
A recent change has resulted in a portion of infrastructure not operating as expected.


Current status
Nov 25, 2024, 11:44 AM EST
We&#039;re rerouting traffic to alternate infrastructure to expedite mitigation. In parallel, we&#039;re resolving complications leading to the delays in targeted server restarts.

This quick update is designed to give the latest information on this issue..</p>
<p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>21:52:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301mbi1pcb4433hd0</id>
  <published>2024-09-12T12:29:00.000+00:00</published>
  <updated>2024-09-12T12:29:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301mbi1pcb4433hd0"/>
  <title>Possible Microsoft 365 Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>12:29:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving reports about Microsoft 365 access being extremely limited. Many customers are not able to access office.com and use the online applications.
We&#039;ve also received reports that Multi-Factor Authentication sent via Microsoft is affected.

We are investigating and will post updates as we learn more info..</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>14:40:12</var> GMT+0</small><br /><strong>Resolved</strong> -
  Microsoft is reporting the issue to be resolved.
If you are continuing to have issues, please reach out to the Help Desk.
Update from Microsoft: &quot;Final status: After an extended period of monitoring our network telemetry, we&#039;ve confirmed the issue is now resolved.&quot;.</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>13:15:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  Microsoft has worked with the affected ISP and resolved the issue - services are being restored.
Update from Microsoft:
&quot;Current status: We&#039;ve worked with the third-party Internet Service Provider (ISP) and confirmed that a change within their managed-environment resulted in impact. The ISP has reverted the change and we&#039;re now seeing signs of recovery. We&#039;re continuing to monitor network telemetry data to ensure a full recovery.&quot;.</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>12:35:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have received the following update from Microsoft:
&quot;Title: Users may be unable to access one or more Microsoft 365 services
User impact: Users may be unable to access one or more Microsoft 365 services.
Current status: We&#039;re reviewing network telemetry logs to identify the root cause of the issue and develop our remediation plan.
Scope of impact: Impact is specific to a subset of users who are attempting to access the service from the North America region.&quot;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301m6i1pc91z96a9y</id>
  <published>2024-08-22T14:54:00.000+00:00</published>
  <updated>2024-08-22T14:54:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301m6i1pc91z96a9y"/>
  <title>Bitlocker Keys required for start-up</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> General Announcement</p>
    <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>14:54:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are aware of a bug related to Bitlocker causing some DELL computers to be unable to boot fully after a restart. 

Our team is investigating a fix and roll-back of any impacted machines. In the meantime, we urge our user NOT to reboot for any reason until we have been able to track down the root cause of this issue, and have deployed a fix. 

We apologize for any impact and are working diligently for the fastest resolution. If you are placed in an urgent situation, please call our offices so we can assist you with a work-around..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:04:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are still working on the last case-by-case issues related to this incident. If you are experiencing any persisting or new issues, please call our service desk at 423.464.6424 Option 1 to report your issue so we can prioritize it..</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>12:00:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  Last night, our engineering team pushed and tested a rollback of the trouble component. We are confident that this will eliminate any further impact, but are leaving this case open until we get past a couple of days. 

However, if you experience anything related to the described behavior, please call our service desk at 423.464.6424 Option 1 to report your issue so we can prioritize it..</p>
<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>17:16:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have successfully identified the machines that could potentially be impacted, and are working with our platform vendor to pull some historical reports to help us narrow down the final fixes. 

For now, our standing guidance:
Do not reboot any Dell machine that hasn&#039;t already prompted for a Bitlocker key. 

We will post here with any updates..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301m3i1pc5r73b7h4</id>
  <published>2024-08-12T20:44:00.000+00:00</published>
  <updated>2024-08-12T20:44:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301m3i1pc5r73b7h4"/>
  <title>Google Workspace Outage (GWS)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>20:44:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving reports of users unable to sign in, connect to apps, and various other Goole Workspace-related issues. 

Google had reported global outages and impacts. 

We are keeping tabs on this as it develops
https://www.google.com/appsstatus/dashboard/.</p>
<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>14:53:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301lzi1pcemvm0zew</id>
  <published>2024-05-13T20:12:00.000+00:00</published>
  <updated>2024-05-13T20:12:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301lzi1pcemvm0zew"/>
  <title>Duo Push Delivery Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Duo</p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>20:12:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  From DUO SOC:

Push Delivery Failures

New incident: Investigating 

We are currently investigating an issue causing failures with Duo Push. We are working to correct the issue as soon as possible.

Please check back here or subscribe to updates for any changes. 

Time posted

May 13, 15:49 EDT 

Full source link: https://status.duo.com/incidents/s1j49frg03z0.</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>22:31:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  Incident resolved 

The issue causing authentication failures on all affected deployments is fully resolved and all services are now fully functional.

We will be posting a root-cause analysis (RCA) here once our engineering team has finished its thorough investigation of the issue. 

Time posted

May 13, 17:42 EDT.</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>20:14:05</var> GMT+0</small><br /><strong>Investigating</strong> -
  From DUO SOC:
Identified
The issue has been identified and a fix is being implemented.
Posted 1 minute ago. May 13, 2024 - 16:16 EDT.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301lui1pc61oo157o</id>
  <published>2024-05-07T17:49:00.000+00:00</published>
  <updated>2024-05-07T17:49:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301lui1pc61oo157o"/>
  <title>Keystone Voice main servers currently down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> FluentStream Voice</p>
    <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>17:49:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have been alerted to phones going offline and showing no service.

From our service provider:
There is an event occurring with phone registration in PHL. We are investigating and will provide more information as soon as possible..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>20:07:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  Customers, Our Service Provider has let us know the situation should be resolved. If you continue to encounter issues, please call us at 423.464.6424, or email us at service@keystone.solutions

From service provider:
&quot;Service in both data centers has now been fully restored. If you manually failed your devices over to PHX you can now fail them back to the primary server.&quot;.</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>18:39:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Customers.
Below is the latest update from our service provider:

&quot;There continue to be issues with calling services, including inbound and outbound calling, and registration. The PHL data center is impacted and the PHX data center is partially degraded. Since our last update, to allow for recovery of the PHL network, we purposefully prevented a portion of SIP traffic from entering the PHL Network. We’re now slowly reopening the network to prevent large bursts of traffic that could cause more issues.

We’re still investigating the root cause of this issue and will provide more information as soon as possible.&quot;.</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>18:37:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  Customers,
Our provider has let us know that they are also now seeing issues with customers in the PHX Datacenter. We will continue to monitor the status..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301lri1pcaay4gacv</id>
  <published>2024-05-03T14:49:00.000+00:00</published>
  <updated>2024-05-03T14:49:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301lri1pcaay4gacv"/>
  <title>Testing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> General Announcement</p>
    <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:49:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  test.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:54:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Maintenance/cmo0fx9v101nwi1pc8rcx0w3c</id>
  <published>2024-05-03T14:03:00.000+00:00</published>
  <updated>2024-05-03T14:03:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/maintenance/cmo0fx9v101nwi1pc8rcx0w3c"/>
  <title>Scheduled Maint Test</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> General Announcement</p>
    <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:03:00</var> GMT+0</small><br /><strong>Identified</strong> -
  This is a test.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:55:43</var> GMT+0</small><br /><strong>Identified</strong> -
  TThe maintenance has been completed.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301lki1pc1v6q96dm</id>
  <published>2024-05-02T15:35:00.000+00:00</published>
  <updated>2024-05-02T15:35:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301lki1pc1v6q96dm"/>
  <title>Intermittent KSvoice quality problems</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> FluentStream Voice</p>
    <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>15:35:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have been made aware of intermittent voice quality problems for users using KS Voice services

We have confirmed with the hosting provider that there is a problem that&#039;s being addressed. 

Last update from our provider:
We continue to address intermittent QoS issues affecting some customers built in the PHL datacenter. Our Engineers are diligently working on this issue. The data provided by our partners has been extremely helpful. We’ll send another update at Noon today, or earlier if we have new information to provide..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>14:50:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our provider has let us know that they believe this issue to be resolved.

Service Provider update:
&quot;Incident resolved
The elevated number of calls experiencing audio issues in the PHL data center has returned to normal, therefore we’re closing this incident. A Root Cause Analysis will be provided in the coming days.&quot;.</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:20:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our provider has been able to normalize quality within their Philadelphia DataCenter. If you have voice quality issues at this time, please let us know.

Please see the latest update from our service provider:
&quot;After making further adjustments over the weekend, and specifically since yesterday afternoon, our monitoring shows more normalized audio quality in the PHL datacenter. However, we’re acutely aware of how important it is that we fully resolve this issue for you and your customers, so our engineers continue to closely monitor the network.

If you are on the PHX data center, please stay there for now. If you are on the PHL data center, please continue to report any call quality issues your customers encounter. Your reporting has been, and will continue to be, an important part of this troubleshooting event.&quot;.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>15:23:50</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest update from our Service Provider:

&quot;While the platform metrics in the PHL data center stabilized after the load balancing performed on the platform last night, we continue to see QoS issues.
The stabilization efforts relieved part of the quality-related issues like garbled audio due to Jitter and we’re now addressing audio drop-out or gaps due to packet delay variation. Engineering is continuing to address the situation and will work 24/7, throughout the weekend, until this is fully resolved.&quot;.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>13:54:12</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest update from our provider:
&quot;Last night, the new servers were successfully stood up and put into production. This, among other things, should result in a more appropriate load balance across all servers. Engineering is continuing to monitor and work the situation.   

If you are on the PHL servers, your customers should feel a noticeable improvement today. However, please report any Call Quality issues in PHL to our support team.  We’ll send another update at 4pm ET today, or earlier if we have additional information to provide. &quot;

If you are continuing to have issues, please report them to Keystone..</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>20:41:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  If your business is being impacted - we may be able to help mitigate. Please call our help desk at 423.464.6424 and we will work with you.

Latest update from our provider:
&quot;We are still experiencing QoS issues affecting some customers built in the PHL datacenter. Our Engineers continue to investigate the issue and have introduced changes to balance the network environment. Our goal is to restore call audio quality for all customers as soon as possible.

In response to data provided by our partners we are focusing on load optimization improvements. We’ve identified several areas to increase performance and have started to implement changes that should have a direct impact on overall call quality. These changes will continue into the evening as we implement ten additional physical servers to further balance the load. We’ll continue to provide improvements until the issue is resolved.

We apologize for the inconvenience this is causing. We’ll send another update at 9am tomorrow morning, or earlier if we have additional information to provide.&quot;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301lci1pcfdc27407</id>
  <published>2024-02-26T14:06:00.000+00:00</published>
  <updated>2024-02-26T14:06:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301lci1pcfdc27407"/>
  <title>Various Workstation Performance issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:06:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are experiencing and are receiving reports of other experiencing various issue with various Workstations:
Slow performance, Black Screens, and weird glitchy behavior.

We are attempting to correlate reports with behavior to find a fix for the issue. 

At this time, we have no details on this issue and no ETA on a fix..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>20:43:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>18:22:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  The issues reported appear to have been largely resolved by the underlying vendors

This incident will go into a 24-hour hold and then close automatically. 

Current KeyStone Guidance:
If you are still having problems, shut down any impacted computers (not restart/reboot) and turn it back on after 10-15 seconds. This seems to kick-start the update process and allow things to clear out of memory fully. 

If after a full shutdown, you are still experiencing problems, please open a ticket with us (if not already) by emailing service@keystone.solutions. 
Simply mention that you are impacted by the global performance issue so we can be sure to confirm with you once we have and have pushed a fix..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>16:13:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  It appears that the underlying trouble vendors have pushed updates that have corrected the issues for most of the people who reported problems.

We now believe that Webroot manage AV pushed an update that was causing problems with an MS Office update from Saturday that required Webroot to push an emergency update this morning. 
We have pushed a polling update to all computers using Webroot to try to force the updated policy. This appears to be clearing the issue on most computers. 

Current KeyStone Guidance:
If you are still having problems, shut down any impacted computers (not restart/reboot) and turn it back on after 10-15 seconds. This seems to kick-start the update process and allow things to clear out of memory fully. 

If after a full shutdown, you are still experiencing problems, please open a ticket with us (if not already) by emailing service@keystone.solutions. 
Simply mention that you are impacted by the global performance issue so we can be sure to confirm with you once we have and have pushed a fix.

We are continuing to monitor the situation.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving reports that some users&#039; machines are self-resolving. We suspect the impacted vendor may have pushed an emergency update. 

Our current guidance:
Shutdown any impacted computers (not restart/reboot).
If after a full shutdown, you are still experiencing problems, please open a ticket with us (if not already) by emailing service@keystone.solutions. 
Simply mention that you are impacted by the global performance issue so we can be sure to confirm with you once we have and have pushed a fix..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:48:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have potentially isolated the issue and are testing workarounds..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:47:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are getting similar reports from other vendors as well as many of our partner companies that this is looking like a globally widespread problem. We will update every 2 hours until we have a resolution..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301l9i1pc4ili6846</id>
  <published>2024-02-22T16:13:00.000+00:00</published>
  <updated>2024-02-22T16:13:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301l9i1pc4ili6846"/>
  <title>Duo US deployments degraded service with telephony VoIP and SMS</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Duo</p>
    <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>16:13:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Duo Serivce Incident Page:
https://status.duo.com/incidents/b51gz4k7q9yq.</p>
<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>21:17:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301l5i1pc00kqa5v6</id>
  <published>2024-01-26T19:22:00.000+00:00</published>
  <updated>2024-01-26T19:22:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301l5i1pc00kqa5v6"/>
  <title>Teams Messaging Failed or Delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Microsoft 365</p>
    <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>19:22:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are getting reports of delayed or failing teams messages globally. We are monitoring the situation. Microsoft is aware and is providing sporadic updates as they come in..</p>
<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>16:09:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  Resolved Jan 27, 29024.</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>19:30:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  Title: Some users may experience multiple issues with their Microsoft Teams

User impact: Users may experience multiple issues with their Microsoft Teams.

More info: Affected scenarios include, but aren&#039;t limited to:
- Users performing a cold boot may not able to log into teams and will see an &quot;oops&quot; page
- Users logging in or unlocking their devices after some time may see missing messages
- Users may fail to load messages in channels and chats
- Users are unable to view or download their media (images, videos, audio, call recordings, code snippets)
- Some messages may experience delays being sent
- Call Recordings might take longer to appear in user&#039;s OneDrive for Business and SharePoint Online
- Users may be unable to load previous Copilot history, or new history is not written
- Bots may be unable to download attachments
- Sending and receiving read receipt notifications may be delayed
- Anonymous users may be unable to join meetings
- Teams connectors for Power Automate/Power Apps may experiencing errors

Current status: We’ve completed the failover in the Europe, Middle East, and Africa (EMEA) region and telemetry is showing improvement. We’re continuing with the failover processes in the Americas, and are monitoring whilst these processes complete.

Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section.

Start time: Friday, January 26, 2024 at 9:55 AM EST

Next update by: Friday, January 26, 2024 at 3:00 PM EST.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301l0i1pce2kk9yg8</id>
  <published>2023-08-17T17:44:00.000+00:00</published>
  <updated>2023-08-17T17:44:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301l0i1pce2kk9yg8"/>
  <title>Spectrum/TimeWarner/Verizon Business circuits out for a VERY wide service area</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Spectrum</p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>17:44:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving reports of a very wide service outage related to Spectrum/TimeWarner/Verizon Business and any underlying carriers that use their back-bone. 

We have not other information at this time, but have reached out to out reps for an outage ETA and more info. 

We will post regular updates until the outage has cleared..</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>12:42:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have seen the majority of Spectrum links come back online. If you are still experiencing issues, today, please reach out to our service desk or your account manager..</p>
<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>19:08:16</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing both cable and fiber circuits coming back up over most of our service area. 

We will continue monitoring through the remainder of the business day..</p>
<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>19:00:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have confirmed that Spectrum is aware of the outage. At this time, there is no ETA for a full recovery of services, though we have seen some of our customers&#039; circuits come back online. 

We will continue to update as we get information..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Incident/cmo0fx9s301kxi1pc5g6p267h</id>
  <published>2023-07-17T14:32:00.000+00:00</published>
  <updated>2023-07-17T14:32:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/incident/cmo0fx9s301kxi1pc5g6p267h"/>
  <title>Voice call from AT&amp;T number are not reaching 423 area codes intermittently.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> FluentStream Voice</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have had a number of customers report trouble receiving calls to 423 area code numbers when calling from AT&amp;T cellular phones. 

We have engaged our back-end vendor, and they are working with AT&amp;T actively on a fix. We have no ETA at this time. 

We appreciate your patience as we allow the responsible vendors to work on this outage. We will provide updates as we recieve them..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have had a number of customers report trouble receiving calls to 423 area code numbers when calling from AT&amp;T cellular phones. 

We have engaged our back-end vendor, and they are working with AT&amp;T actively on a fix. We have no ETA at this time. 

We appreciate your patience as we allow the responsible vendors to work on this outage. We will provide updates as we recieve them..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:keystone.instatus.com,2005:Maintenance/cmo0fx9v001nsi1pcb61a9gmn</id>
  <published>2021-12-03T21:00:00.000+00:00</published>
  <updated>2021-12-03T21:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://keystone.instatus.com/maintenance/cmo0fx9v001nsi1pcb61a9gmn"/>
  <title>KeyStone SMS System Conversion</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days, 16 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> SMS</p>
    <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are transitioning our SMS inbound service to a new provider. 
We expect things to be down for around 72 hours beginning 12/3 @5PM EST.</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>14:11:41</var> GMT+0</small><br /><strong>Identified</strong> -
  The maintenance has been completed.</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The maintenance has been started.</p>

        ]]>
  </content>
</entry>

</feed>