<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.nesparc.com/"/>
    <title>Ox_dia on NESPARC Operational Status</title>
    <link>https://status.nesparc.com/affected/ox_dia/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-08-10T11:59:59+00:00</lastBuildDate>
    <updated>2026-08-10T11:59:59+00:00</updated>
    
    
    
      <atom:link href="https://status.nesparc.com/affected/ox_dia/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>PLANNED MAINTENANCE</title>
        <link>https://status.nesparc.com/issues/2026-08-11-router-maintenance/</link>
        <pubDate>Mon, 10 Aug 2026 11:59:59 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2026-08-11-router-maintenance/</guid>
        <category>2026-07-02 18:23:00</category>
        <description>&lt;p&gt;&lt;strong&gt;MON AUG 10 11:59PM&lt;/strong&gt; &lt;code&gt;SCHEDULED MAINTENANCE&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Beginning at 11:59PM on Monday August 10, engineers will perform firmware upgrades on a series of our core routers. There could be periods during these upgrades where subscriber services are interrupted while hardware restarts. Redundnant paths will take over, but there could be intermittent blips in service during that process. The maintenance period will continue until 6:00am, but service impacts will be brief and intermittent and will not span the entire timeframe.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;MON AUG 10 11:59PM&lt;/strong&gt; &lt;code&gt;SCHEDULED MAINTENANCE&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Beginning at 11:59PM on Monday August 10, engineers will perform firmware upgrades on a series of our core routers. There could be periods during these upgrades where subscriber services are interrupted while hardware restarts. Redundnant paths will take over, but there could be intermittent blips in service during that process. The maintenance period will continue until 6:00am, but service impacts will be brief and intermittent and will not span the entire timeframe.&lt;/p&gt;
&lt;p&gt;Thanks for your patience as we work to improve our infrastructure.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;NE Fiber / NE Sparc / North East MS EPA&lt;/p&gt;
&lt;/blockquote&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Core Network Maintenance</title>
        <link>https://status.nesparc.com/issues/2025-07-16-core-net-maint/</link>
        <pubDate>Wed, 16 Jul 2025 23:59:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2025-07-16-core-net-maint/</guid>
        <category>2025-07-17 05:15:29</category>
        <description>&lt;p&gt;&lt;strong&gt;Thursday July 17 2025 05:00am :&lt;/strong&gt; &lt;code&gt;Complete&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This maintenance has been completed.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Wednesday July 16 2025 11:59pm :&lt;/strong&gt; &lt;code&gt;Core Network Maintenance&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;On Wednesday July 16 2025 beginning at 11:59 PM, NE Fiber will perform scheduled maintenance on some core network equipment in Oxford and Enterprise. Subscriber traffic should not be affected but certain services could be intermittent while equipment is rebooted.&lt;/p&gt;
&lt;p&gt;We appreciate your patience while we work to continually improve the resiliency of our network. Thanks for using NESPARC.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;Thursday July 17 2025 05:00am :&lt;/strong&gt; &lt;code&gt;Complete&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This maintenance has been completed.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Wednesday July 16 2025 11:59pm :&lt;/strong&gt; &lt;code&gt;Core Network Maintenance&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;On Wednesday July 16 2025 beginning at 11:59 PM, NE Fiber will perform scheduled maintenance on some core network equipment in Oxford and Enterprise. Subscriber traffic should not be affected but certain services could be intermittent while equipment is rebooted.&lt;/p&gt;
&lt;p&gt;We appreciate your patience while we work to continually improve the resiliency of our network. Thanks for using NESPARC.&lt;/p&gt;
&lt;/blockquote&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Core Network Maintenance</title>
        <link>https://status.nesparc.com/issues/2025-03-19-core-network-maint/</link>
        <pubDate>Tue, 18 Mar 2025 23:50:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2025-03-19-core-network-maint/</guid>
        <category>2025-03-19 05:05:29</category>
        <description>&lt;p&gt;&lt;strong&gt;Tues March 18 2025 // MIDNIGHT:&lt;/strong&gt; &lt;code&gt;Completed&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Maintenance has been completed&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Tues March 18 2025 // MIDNIGHT:&lt;/strong&gt; &lt;code&gt;Maintenance&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;NE Fiber will perform scheduled maintenance beginning Tuesday Mar. 18 2025 at 11:50PM involving routers on the core backbone. The maintenance window will last until 6:00 am, although service interruptions should be brief, if any as core routers are rebooted.&lt;/p&gt;
&lt;p&gt;If you experience service issues after 06:00 am Wednesday morning, please first power cycle your equipment (router and ONT/Modem) and if not resolved contact our Helpdesk.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;Tues March 18 2025 // MIDNIGHT:&lt;/strong&gt; &lt;code&gt;Completed&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Maintenance has been completed&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Tues March 18 2025 // MIDNIGHT:&lt;/strong&gt; &lt;code&gt;Maintenance&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;NE Fiber will perform scheduled maintenance beginning Tuesday Mar. 18 2025 at 11:50PM involving routers on the core backbone. The maintenance window will last until 6:00 am, although service interruptions should be brief, if any as core routers are rebooted.&lt;/p&gt;
&lt;p&gt;If you experience service issues after 06:00 am Wednesday morning, please first power cycle your equipment (router and ONT/Modem) and if not resolved contact our Helpdesk.&lt;/p&gt;
&lt;p&gt;We appreciate your patience while we work to continually improve the resiliency of our network. Thanks for using NESPARC.&lt;/p&gt;
&lt;/blockquote&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] DIA Down</title>
        <link>https://status.nesparc.com/issues/2024-05-15-hqdia-down/</link>
        <pubDate>Wed, 15 May 2024 17:16:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2024-05-15-hqdia-down/</guid>
        <category>2024-05-16 01:23:00</category>
        <description>&lt;p&gt;&lt;strong&gt;DIA Down : 1:23am 5/16&lt;/strong&gt;  &lt;code&gt;RESOLVED&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Splicing and cable replacement for the upstrem provider near Jackson is complete. Servivces are restoring to all affected subscribers.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;DIA Down : 9:03pm&lt;/strong&gt;  &lt;code&gt;Mitigating&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Crews have located the damaged fiber on one of our circuits and multiple repair crews are working as quickly as possible to clear the damage. Repairs also continue on the other circuits. While we have not been given an offical ETR on any of the damaged circuits, we do expect progress to be made throughout the evening. Traffic control, splicing, and cable repair preparations are being done as rapidly as possible. We will provide more specific updates as we have them.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;DIA Down : 1:23am 5/16&lt;/strong&gt;  &lt;code&gt;RESOLVED&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Splicing and cable replacement for the upstrem provider near Jackson is complete. Servivces are restoring to all affected subscribers.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;DIA Down : 9:03pm&lt;/strong&gt;  &lt;code&gt;Mitigating&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Crews have located the damaged fiber on one of our circuits and multiple repair crews are working as quickly as possible to clear the damage. Repairs also continue on the other circuits. While we have not been given an offical ETR on any of the damaged circuits, we do expect progress to be made throughout the evening. Traffic control, splicing, and cable repair preparations are being done as rapidly as possible. We will provide more specific updates as we have them.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;DIA Down : 8:13pm&lt;/strong&gt;  &lt;code&gt;Mitigating&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;To clarify NESPARC has multiple transports to the internet.  Today, an unprecedented event occured: our main DIA experienced an outage as well as multiple backup circuits.  C-levels at all providers are engaged and the issues have and are being escalated.  Crews are working to repair the damages in multiple areas.  We do not currently have an ETR, but are taking all measures possible to mitigate the issue while repairs are being made.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;DIA Down : 5:15pm&lt;/strong&gt;  &lt;code&gt;Investigating&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The primary circuit for NE SPARC went offline at 5:16pm and the cause is unknown. We know that the issue is outside of the NE SPARC network. We continue to work with our upstream provider to isolate the issue and resolve it.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;Prior to this event, our redundant circuit was damaged in Tennessee. Repairs are underway on this circuit and we continue to monitor their progress.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
</content>
      </item>
    
  </channel>
</rss>
