<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Sprint Online Status - Incident history</title>
    <link>https://sprint-online.instatus.com</link>
    <description>Sprint Online</description>
    <pubDate>Thu, 26 Feb 2026 15:45:39 +0000</pubDate>
    
<item>
  <title>Network issues</title>
  <description>
    Type: Incident
    

    Affected Components: UC Integration, Dialer, Outbound Calls, Busy Lamps, MobeX Softphone, Inbound Calls, Wallboards, Handset Provisioning, Web Interface, , Disaster Recovery, MobeX Mobile, Bria Enterprise Mobile, Bria Enterprise Desktop, 
Telecoms →
    Feb 26, 16:48:54 GMT+0 - Identified - Whilst we do have failover mechanisms in place, these only apply when the primary connection is hard down.  
As it currently flapping, this prevents the system moving into failover as the connection is not hard down.  
Unfortunately, this has put the system in a state where we will have to manually disconnect the link in order to utilise the other links. Our engineers are at site at the datacentre and working on the servers. Feb 26, 16:56:33 GMT+0 - Monitoring - We now have a restricted service back-up and running, but services such as BLF will not be fully operational for a while as we concentrate on getting things running back as normal. Feb 26, 15:45:39 GMT+0 - Investigating - We are currently investigating this incident at our datacentres, which is affecting our network and the abilility to make and receive calls.We are currently investigating this incident. Feb 26, 15:51:02 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 26, 16:24:43 GMT+0 - Identified - Engineers have been dispatched to one of the datacentres to work on the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:48:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Whilst we do have failover mechanisms in place, these only apply when the primary connection is hard down.  
As it currently flapping, this prevents the system moving into failover as the connection is not hard down.  
Unfortunately, this has put the system in a state where we will have to manually disconnect the link in order to utilise the other links. Our engineers are at site at the datacentre and working on the servers..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:56:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We now have a restricted service back-up and running, but services such as BLF will not be fully operational for a while as we concentrate on getting things running back as normal..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:45:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident at our datacentres, which is affecting our network and the abilility to make and receive calls.We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:51:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:24:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Engineers have been dispatched to one of the datacentres to work on the issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Feb 2026 15:45:39 +0000</pubDate>
  <link>https://sprint-online.instatus.com/incident/cmm3mxlnl01gtab5q7svedsog</link>
  <guid>https://sprint-online.instatus.com/incident/cmm3mxlnl01gtab5q7svedsog</guid>
</item>

<item>
  <title>Broadband Issues</title>
  <description>
    Type: Incident
    Duration: 1 day, 5 hours and 46 minutes

    Affected Components: Wireless Internet
    Jul 24, 12:37:00 GMT+0 - Investigating - One of our upstream broadband suppliers is having issues affecting some of customers. We are currently investigating this incident. Jul 24, 13:37:00 GMT+0 - Identified - The supplier is still working on a resolution to the issue and hopes to have it resolved as soon as possible Jul 24, 16:10:00 GMT+0 - Monitoring - We are aware that some broadbands are still offline. If possible can you please power down the router for 20 minutes to try and kill any stale sessions it may have which was caused by the outage. Jul 25, 18:23:00 GMT+0 - Resolved - Whilst the incident is now resolved we are waiting for a Reason For Outage from the supplier. As soon as we have this we will update this page Jul 26, 12:31:08 GMT+0 - Resolved - Reason For Outage on 24.07.24

The supplier has informed us that they had a power issue on a bank of servers at one of their data centres. This caused stale sessions on the broadband connections. If you still do not have any service, please power down the router for 30 minutes. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 5 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:37:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of our upstream broadband suppliers is having issues affecting some of customers. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:37:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The supplier is still working on a resolution to the issue and hopes to have it resolved as soon as possible.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are aware that some broadbands are still offline. If possible can you please power down the router for 20 minutes to try and kill any stale sessions it may have which was caused by the outage..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:23:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Whilst the incident is now resolved we are waiting for a Reason For Outage from the supplier. As soon as we have this we will update this page.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:31:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Reason For Outage on 24.07.24

The supplier has informed us that they had a power issue on a bank of servers at one of their data centres. This caused stale sessions on the broadband connections. If you still do not have any service, please power down the router for 30 minutes..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 24 Jul 2024 12:37:00 +0000</pubDate>
  <link>https://sprint-online.instatus.com/incident/clz2ofkrh291347hqoeulzf2p38</link>
  <guid>https://sprint-online.instatus.com/incident/clz2ofkrh291347hqoeulzf2p38</guid>
</item>

  </channel>
  </rss>