<?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>JSI Peering Network Status - Incident history</title>
    <link>https://jsipeeringstatus.jsinoc.com</link>
    <description>JSI Peering Network</description>
    <pubDate>Thu, 30 Oct 2025 17:19:27 +0000</pubDate>
    
<item>
  <title>5 Star - Amarillo to Hereford possible Fiber cut</title>
  <description>
    Type: Incident
    Duration: 20 hours and 54 minutes

    Affected Components: Fiber Network
    Oct 31, 14:13:04 GMT+0 - Resolved - Traffic has restored and stayed stable over night. This incident is resolved Oct 30, 21:26:22 GMT+0 - Monitoring - Crew is hands off. Connection showing back up and passing traffic again. We will continue to monitor and reach back out if further issues persist.  Oct 30, 19:50:32 GMT+0 - Identified - Crew has started splicing one side of the fiber. They expect to have services restored between 3:30 pm and 4:00 pm today. Oct 30, 19:25:06 GMT+0 - Identified - Crews are actively digging and working to get to the fiber to begin repairs.  Oct 30, 17:43:47 GMT+0 - Identified - Fiber cut has been identified 5 miles East of Hereford. Atmos Energy was attempting to remove rocks from the area and cut the fiber. Crews have been dispatched and on the way to begin assestment and repair. No ETR given at the moment. Oct 30, 17:19:27 GMT+0 - Investigating - JSI is investigating a potential fiber cut in the network. Traffic is flowing on redundant links and all services are operational. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>14:13:04</var> GMT+0</small><br><strong>Resolved</strong> -
  Traffic has restored and stayed stable over night. This incident is resolved.</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>21:26:22</var> GMT+0</small><br><strong>Monitoring</strong> -
  Crew is hands off. Connection showing back up and passing traffic again. We will continue to monitor and reach back out if further issues persist. .</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>19:50:32</var> GMT+0</small><br><strong>Identified</strong> -
  Crew has started splicing one side of the fiber. They expect to have services restored between 3:30 pm and 4:00 pm today..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>19:25:06</var> GMT+0</small><br><strong>Identified</strong> -
  Crews are actively digging and working to get to the fiber to begin repairs. .</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>17:43:47</var> GMT+0</small><br><strong>Identified</strong> -
  Fiber cut has been identified 5 miles East of Hereford. Atmos Energy was attempting to remove rocks from the area and cut the fiber. Crews have been dispatched and on the way to begin assestment and repair. No ETR given at the moment..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>17:19:27</var> GMT+0</small><br><strong>Investigating</strong> -
  JSI is investigating a potential fiber cut in the network. Traffic is flowing on redundant links and all services are operational..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Oct 2025 17:19:27 +0000</pubDate>
  <link>https://jsipeeringstatus.jsinoc.com/incident/cmhdovuth010qifymc5ycixi8</link>
  <guid>https://jsipeeringstatus.jsinoc.com/incident/cmhdovuth010qifymc5ycixi8</guid>
</item>

<item>
  <title>Core Capacity Upgrades</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Fiber Network, Network Equipment, Wave Services
    May 2, 06:31:00 GMT+0 - Completed - Maintenance has completed successfully May 2, 05:01:01 GMT+0 - Identified - Maintenance is now in progress May 2, 05:01:00 GMT+0 - Identified - A maintenance is planned for 12:01 AM to increase network capacity on some links. The maintenance will be performed in steps so that IP transit services remain available during the changes.

This maintenance will take approximately 1 hour and cause some BGP sessions to go down and come back up.

This maintenance has been expedited to improve the capacity of the network. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>06:31:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>05:01:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>05:01:00</var> GMT+0</small><br><strong>Identified</strong> -
  A maintenance is planned for 12:01 AM to increase network capacity on some links. The maintenance will be performed in steps so that IP transit services remain available during the changes.

This maintenance will take approximately 1 hour and cause some BGP sessions to go down and come back up.

This maintenance has been expedited to improve the capacity of the network..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 2 May 2025 05:01:00 +0000</pubDate>
  <link>https://jsipeeringstatus.jsinoc.com/maintenance/cma638kdm008hcs7ncy0x1ina</link>
  <guid>https://jsipeeringstatus.jsinoc.com/maintenance/cma638kdm008hcs7ncy0x1ina</guid>
</item>

<item>
  <title>Wave Service Down</title>
  <description>
    Type: Incident
    Duration: 4 hours and 45 minutes

    Affected Components: Wave Services
    May 1, 05:00:00 GMT+0 - Resolved - The provider confirmed that there was an optic failure on their network. 

The optic was been replaced and the alarms have now cleared. Traffic has returned to normal paths. May 1, 00:15:00 GMT+0 - Identified - JSI has identified an issue with a wave service. Traffic has re-routed to alternate paths and our team is closely monitoring for issues. A ticket with the circuit provider has been opened. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The provider confirmed that there was an optic failure on their network. 

The optic was been replaced and the alarms have now cleared. Traffic has returned to normal paths..</p>
<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>00:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  JSI has identified an issue with a wave service. Traffic has re-routed to alternate paths and our team is closely monitoring for issues. A ticket with the circuit provider has been opened..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 1 May 2025 00:15:00 +0000</pubDate>
  <link>https://jsipeeringstatus.jsinoc.com/incident/cma4s441b006ip3f2arqiax13</link>
  <guid>https://jsipeeringstatus.jsinoc.com/incident/cma4s441b006ip3f2arqiax13</guid>
</item>

<item>
  <title>Google Peering Issues</title>
  <description>
    Type: Incident
    Duration: 3 days, 22 hours and 11 minutes

    Affected Components: Peering Connections
    Apr 21, 20:26:00 GMT+0 - Resolved - Google replaced their failed hardware and these connections are restored Apr 17, 22:15:00 GMT+0 - Identified - JSI has identified issues with Google direct Peering with the root cause being identified as a hardware issue on Google&#039;s side. ETR is not yet available. At this time, Google traffic is flowing on IP Transit Connections and Caching servers normally. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 22 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>20:26:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Google replaced their failed hardware and these connections are restored.</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>22:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  JSI has identified issues with Google direct Peering with the root cause being identified as a hardware issue on Google&#039;s side. ETR is not yet available. At this time, Google traffic is flowing on IP Transit Connections and Caching servers normally..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 17 Apr 2025 22:15:00 +0000</pubDate>
  <link>https://jsipeeringstatus.jsinoc.com/incident/cma19zdbt0001y3fjn97fmox2</link>
  <guid>https://jsipeeringstatus.jsinoc.com/incident/cma19zdbt0001y3fjn97fmox2</guid>
</item>

  </channel>
  </rss>