<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>Martintown on NESPARC Operational Status</title>
    <link>https://status.nesparc.com/affected/martintown/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-01-22T15:01:59+00:00</lastBuildDate>
    <updated>2026-01-22T15:01:59+00:00</updated>
    
    
    
      <atom:link href="https://status.nesparc.com/affected/martintown/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] CR 61 / Hwy 30 - Enterprise</title>
        <link>https://status.nesparc.com/issues/2026-01-22-cr61-hwy30/</link>
        <pubDate>Thu, 22 Jan 2026 15:01:59 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2026-01-22-cr61-hwy30/</guid>
        <category>2026-01-23 15:12:59</category>
        <description>&lt;p&gt;&lt;strong&gt;FRI Jan 23 2026 3:27 PM:&lt;/strong&gt; &lt;code&gt;Completed&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Repairs have been completed and subscriber services are restored.&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;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;FRI Jan 23 2026 1:27 PM:&lt;/strong&gt; &lt;code&gt;In Progress&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The new cable is in progress of being spliced. Any subscribers affeced in the Martintown substation should have services restored.  The rest of the subscribers in the area of the damage should be restored shortly as crews continue splicing.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;FRI Jan 23 2026 3:27 PM:&lt;/strong&gt; &lt;code&gt;Completed&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Repairs have been completed and subscriber services are restored.&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;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;FRI Jan 23 2026 1:27 PM:&lt;/strong&gt; &lt;code&gt;In Progress&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The new cable is in progress of being spliced. Any subscribers affeced in the Martintown substation should have services restored.  The rest of the subscribers in the area of the damage should be restored shortly as crews continue splicing.&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;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Thu Jan 22 2026 11:20 PM :&lt;/strong&gt; &lt;code&gt;In Progress&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Crews have made all possible repairs on the mainline cables and prepped the new cables for installation in the morning.  Less than 10 subscribers remain impacted this evening. Crews will be on-site at first light to complete the permanent repair and restore the remaining services.
When the new cable is being spliced, there will be service interruptions but they should be brief. More info will be posted here as it is available.&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;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Thu Jan 22 2026 7:36 PM :&lt;/strong&gt; &lt;code&gt;In Progress&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The poles have been replaced and crews are working to rebuild lines. However there is some extensive damage to a large count cable carrying transport between sites for NE Fiber. Crews are prepping for the cutover and repair to this cable, which is complex.&lt;/p&gt;
&lt;p&gt;Crews are working to repair the existing cable in an attempt to restore service to all subscribers this evening. However due to the complexity of the repair, it is possible that some subscribers&amp;rsquo; services will not be restored until the new cable is introduced tomorrow morning.&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;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Thu Jan 22 2026 3:01 PM :&lt;/strong&gt; &lt;code&gt;Investigating&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Subscribers in the following areas are experiencing an outage due to an overloaded truck tearing down power and fiber main lines in Union County near the intersection of CR 61 and Hwy 30 West:&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;CR 64 N&lt;/li&gt;
&lt;li&gt;Hwy 30 West (West of CR 61)&lt;/li&gt;
&lt;li&gt;CR 61&lt;/li&gt;
&lt;li&gt;CR 59&lt;/li&gt;
&lt;li&gt;CR 65&lt;/li&gt;
&lt;li&gt;CR 281&lt;/li&gt;
&lt;li&gt;Other areas near the above&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;We do not have an ETR at this time, and are awaiting electric crews to repair and secure a safe work area.&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] Enterprise DIA</title>
        <link>https://status.nesparc.com/issues/2024-10-26-enterprise-dia/</link>
        <pubDate>Sat, 26 Oct 2024 20:03:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2024-10-26-enterprise-dia/</guid>
        <category>2024-10-26 21:05:00</category>
        <description>&lt;p&gt;&lt;strong&gt;UPSTREAM ROUTING ISSUES&lt;/strong&gt; &lt;code&gt;Resolved : 9:05pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;One of our upstream DIA providers that services the east side of our system experienced a loss of routes inside their facility. This caused subsets of our subscribers to to lose access to some of the internet. The routing issue has been resolved by the upstream provider and traffic is flowing normally.  Our NOC and engineers are monitoring the network actively. Thanks for your patience and thanks for using NESPARC.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;UPSTREAM ROUTING ISSUES&lt;/strong&gt; &lt;code&gt;Resolved : 9:05pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;One of our upstream DIA providers that services the east side of our system experienced a loss of routes inside their facility. This caused subsets of our subscribers to to lose access to some of the internet. The routing issue has been resolved by the upstream provider and traffic is flowing normally.  Our NOC and engineers are monitoring the network actively. Thanks for your patience and thanks for using NESPARC.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;UPSTREAM ROUTING ISSUES&lt;/strong&gt; &lt;code&gt;Investigating : 8:23pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We are experiencing upstream routing issues into one of our major DIA providers. This is causing intermittent interruptions or some parts of the internet to be inaccessible. Automatic failover processes are not triggered since circuits are still up. Engineers are investigating.&lt;/p&gt;
&lt;/blockquote&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Enterprise DIA Emergency Maintenance</title>
        <link>https://status.nesparc.com/issues/2024-10-08-enterprise-dia/</link>
        <pubDate>Tue, 08 Oct 2024 18:03:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2024-10-08-enterprise-dia/</guid>
        <category>2024-10-08 18:23:00</category>
        <description>&lt;p&gt;&lt;strong&gt;Emergency Maintenance&lt;/strong&gt; &lt;code&gt;Complete : 6:23pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This maintenance is complete. We were able to perform the maintenance without impacting subscriber services. Thank you for your patience.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Emergency Maintenance&lt;/strong&gt; &lt;code&gt;In Progress : 6:03pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Due to a major core routing issue with one of our upstream providers, NESPARC is performing emergency maintenance to ensure subscribers continue to have the best service possible. During the maintenance, we will move some connections in one of our core routers.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;Emergency Maintenance&lt;/strong&gt; &lt;code&gt;Complete : 6:23pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This maintenance is complete. We were able to perform the maintenance without impacting subscriber services. Thank you for your patience.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Emergency Maintenance&lt;/strong&gt; &lt;code&gt;In Progress : 6:03pm&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Due to a major core routing issue with one of our upstream providers, NESPARC is performing emergency maintenance to ensure subscribers continue to have the best service possible. During the maintenance, we will move some connections in one of our core routers.&lt;/p&gt;
&lt;p&gt;This will cause a brief blip in services while the new link becomes active.. Service interruption should not last more that 3-5 seconds.&lt;/p&gt;
&lt;p&gt;Thank you for your patience and understanding while we continue to improve your network.&lt;/p&gt;
&lt;/blockquote&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] SPARC Network Upgrades</title>
        <link>https://status.nesparc.com/issues/2024-01-10-enterprise-upgrades/</link>
        <pubDate>Wed, 10 Jan 2024 00:00:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2024-01-10-enterprise-upgrades/</guid>
        <category>2024-01-10 02:47:00</category>
        <description>&lt;p&gt;&lt;strong&gt;Wednesday Jan 10 2024 // 02:47am:&lt;/strong&gt;  &lt;code&gt;Upgrades Complete&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Upgrades are complete.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Tuesday Jan 9 2024 // MIDNIGHT:&lt;/strong&gt;  &lt;code&gt;Network Upgrades&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;On Tuesday Jan. 9th 2024, starting at MIDNIGHT (01-10-2024 00:00:00&lt;/strong&gt;) NESPARC will perform upgrades to core routers in the Enterprise substation.&lt;/p&gt;
&lt;p&gt;Susbscribers should fail over to backup circuits, but there is the possibility that short interruptions will occur in the areas serviced on these core routers (Enterprise, Martintown, Ingomar, Cornersville and Waterford) as the updates are applied and routers are restarted.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;Wednesday Jan 10 2024 // 02:47am:&lt;/strong&gt;  &lt;code&gt;Upgrades Complete&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Upgrades are complete.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Tuesday Jan 9 2024 // MIDNIGHT:&lt;/strong&gt;  &lt;code&gt;Network Upgrades&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;On Tuesday Jan. 9th 2024, starting at MIDNIGHT (01-10-2024 00:00:00&lt;/strong&gt;) NESPARC will perform upgrades to core routers in the Enterprise substation.&lt;/p&gt;
&lt;p&gt;Susbscribers should fail over to backup circuits, but there is the possibility that short interruptions will occur in the areas serviced on these core routers (Enterprise, Martintown, Ingomar, Cornersville and Waterford) as the updates are applied and routers are restarted.&lt;/p&gt;
&lt;p&gt;The maintenance is expected to require 1-2 hours to complete.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Enterprise Router Circuit Issue</title>
        <link>https://status.nesparc.com/issues/2023-01-19-enterprise-rtr/</link>
        <pubDate>Thu, 19 Jan 2023 10:45:00 +0000</pubDate>
        <guid>https://status.nesparc.com/issues/2023-01-19-enterprise-rtr/</guid>
        <category>2023-01-19 13:30:00</category>
        <description>&lt;p&gt;&lt;strong&gt;Enterprise transit to HQ - update 1:29pm:&lt;/strong&gt;  &lt;code&gt;Monitoring&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The damaged portion of fiber has been bypassed pending additional repairs. At this time, services should be restored to the affected circuits. If customers are continuing to have issues, please contact our Helpdesk at (833) 637-7272.
&lt;strong&gt;Enterprise transit to HQ - update 11:35am:&lt;/strong&gt;  &lt;code&gt;Investigating&lt;/code&gt;
Testing from several locations, we have found some damage on the transit line connecting the Enterprise hut to Headquarters. Crews are en route to the area of damage to isolate the damage and begin repairs.
&lt;strong&gt;Enterprise Circuit Down :&lt;/strong&gt;  &lt;code&gt;Investigating&lt;/code&gt;
We began receiving alerts around 10:45 am that various circuits were reporting offline, specifically the Enterprise, Waterford, Martintown, Cornersville, and Ingomar. We are currently investigating the issue and the cause.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;strong&gt;Enterprise transit to HQ - update 1:29pm:&lt;/strong&gt;  &lt;code&gt;Monitoring&lt;/code&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The damaged portion of fiber has been bypassed pending additional repairs. At this time, services should be restored to the affected circuits. If customers are continuing to have issues, please contact our Helpdesk at (833) 637-7272.
&lt;strong&gt;Enterprise transit to HQ - update 11:35am:&lt;/strong&gt;  &lt;code&gt;Investigating&lt;/code&gt;
Testing from several locations, we have found some damage on the transit line connecting the Enterprise hut to Headquarters. Crews are en route to the area of damage to isolate the damage and begin repairs.
&lt;strong&gt;Enterprise Circuit Down :&lt;/strong&gt;  &lt;code&gt;Investigating&lt;/code&gt;
We began receiving alerts around 10:45 am that various circuits were reporting offline, specifically the Enterprise, Waterford, Martintown, Cornersville, and Ingomar. We are currently investigating the issue and the cause.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
</content>
      </item>
    
  </channel>
</rss>
