<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:mthn.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://mthn.instatus.com/history.atom"/>
  <title>MTH Networks Status - Incident history</title>
  <updated>2026-09-21T23:00:00.000+00:00</updated>
  <author>
    <name>MTH Networks</name>
  </author>
  
<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsofngnl07ua13lcyl82xy8r</id>
  <published>2026-09-21T23:00:00.000+00:00</published>
  <updated>2026-08-11T09:03:12.677+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsofngnl07ua13lcyl82xy8r"/>
  <title>OFNL Maintenance: Slough, SL1 and SL2</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>09:03:12</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Slough, SL1 and SL2

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsg0sm7l027q0kjsxczhk4vh</id>
  <published>2026-09-14T23:00:00.000+00:00</published>
  <updated>2026-08-05T11:45:09.503+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsg0sm7l027q0kjsxczhk4vh"/>
  <title>OFNL Maintenance: KENILWORTH, CV8</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:45:09</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; KENILWORTH, CV8

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsg0nuqb025l1ao3evex9fz3</id>
  <published>2026-09-14T23:00:00.000+00:00</published>
  <updated>2026-08-05T11:41:27.261+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsg0nuqb025l1ao3evex9fz3"/>
  <title>OFNL Maintenance: Newark, NG24</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:41:27</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Newark, NG24

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsn2ofij0kt00rrphntii5ct</id>
  <published>2026-08-26T23:00:00.000+00:00</published>
  <updated>2026-08-10T10:12:16.660+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsn2ofij0kt00rrphntii5ct"/>
  <title>OFNL Maintenance:  Ipswich, IP6</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>10:12:16</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Ipswich, IP6

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmrxkxo8701ne0sk0f1l2fk6k</id>
  <published>2026-08-25T22:00:00.000+00:00</published>
  <updated>2026-07-23T14:01:20.371+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmrxkxo8701ne0sk0f1l2fk6k"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>14:01:20</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; Brighton &amp; Hove

A 30 minute Service Outage will be expected during the maintenance window..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsiz6v270bxm0rpqd17r2z8k</id>
  <published>2026-08-20T23:00:00.000+00:00</published>
  <updated>2026-08-07T13:23:33.452+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsiz6v270bxm0rpqd17r2z8k"/>
  <title>OFNL Maintenance: Bexhill On Sea, TN39 TN40, Hastings, TN34 and St Leonards On Sea, TN37</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>13:23:33</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Bexhill On Sea, TN39 and TN40 - Hastings, TN34 - St Leonards On Sea, TN37

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cms642gnw02r21almcbubm6mg</id>
  <published>2026-08-20T23:00:00.000+00:00</published>
  <updated>2026-07-29T13:19:05.958+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cms642gnw02r21almcbubm6mg"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>13:19:05</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; Milton Keynes

A 6 hour Service Outage will be expected during the maintenance window..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsn439qj1anr0zpqhk7xzoyd</id>
  <published>2026-08-20T20:00:00.000+00:00</published>
  <updated>2026-08-10T10:51:48.631+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsn439qj1anr0zpqhk7xzoyd"/>
  <title>OFNL Maintenance: Blackwood, NPO12</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>10:51:48</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Blackwood, NPO12

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsnc6vdh1aea0kn3qvnvznk8</id>
  <published>2026-08-19T23:00:00.000+00:00</published>
  <updated>2026-08-10T14:38:33.566+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsnc6vdh1aea0kn3qvnvznk8"/>
  <title>OFNL Maintenance: Hartlepool, TS26 and TS27</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>14:38:33</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Hartlepool, TS26 and TS27

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsg2jiyz02l91ajsbrxli9fe</id>
  <published>2026-08-19T23:00:00.000+00:00</published>
  <updated>2026-08-05T12:34:04.632+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsg2jiyz02l91ajsbrxli9fe"/>
  <title>OFNL Maintenance: Ipswich, IP1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>12:34:04</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Ipswich, IP1

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmrxkukt501ch0lk0qs7bho27</id>
  <published>2026-08-19T22:00:00.000+00:00</published>
  <updated>2026-07-23T13:58:55.974+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmrxkukt501ch0lk0qs7bho27"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>13:58:55</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; North Tyneside

A 1 hour Service Outage will be expected during the maintenance window..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsq0lkor01nn20nze25s7awb</id>
  <published>2026-08-18T23:00:00.000+00:00</published>
  <updated>2026-08-12T11:37:22.694+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsq0lkor01nn20nze25s7awb"/>
  <title>OFNL Maintenance: Colchester, CO7 and CO5 - Manningtree, CO11</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>11:37:22</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Colchester, CO7 and CO5 - Manningtree, CO11

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsq0ir1w02a80rpceof9jyhv</id>
  <published>2026-08-18T23:00:00.000+00:00</published>
  <updated>2026-08-12T11:35:11.090+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsq0ir1w02a80rpceof9jyhv"/>
  <title>OFNL Maintenance: Bury St Edmunds, IP31</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>11:35:11</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Bury St Edmunds, IP31

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmrxkwpo801630rqvbyllios4</id>
  <published>2026-08-18T22:00:00.000+00:00</published>
  <updated>2026-07-23T14:00:35.585+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmrxkwpo801630rqvbyllios4"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>14:00:35</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; Norwich

A 30 minute Service Outage will be expected during the maintenance window..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsg2gsuq030t0ko3lim9h00y</id>
  <published>2026-08-17T23:30:00.000+00:00</published>
  <updated>2026-08-05T12:31:57.466+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsg2gsuq030t0ko3lim9h00y"/>
  <title>OFNL Maintenance: Ipswich, IP1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>12:31:57</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Ipswich, IP1

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsisunaa0a2v0rpqhwm6ra43</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:26:05.807+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsisunaa0a2v0rpqhwm6ra43"/>
  <title>OFNL Maintenance:  Clacton, CO16</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:26:05</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Clacton, CO16

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsitkte30bfl0yn398dpd56x</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:46:26.773+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsitkte30bfl0yn398dpd56x"/>
  <title>OFNL Maintenance:  Chelmsford, CM3 Braintree, CM77 and CM7 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:46:26</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Chelmsford, CM3 Braintree, CM77 and CM7 

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsito1qt0b8a0rpbneo8wgo7</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:48:57.566+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsito1qt0b8a0rpbneo8wgo7"/>
  <title>OFNL Maintenance: Colchester, CO5 and CO6</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:48:57</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Colchester, CO5 and CO6

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsitpw1t0bg80yn3r437x3xp</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:50:23.498+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsitpw1t0bg80yn3r437x3xp"/>
  <title>OFNL Maintenance: Colchester, CO7 and Clacton, CO16</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:50:23</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Colchester, CO7 and Clacton, CO16

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsittqn20bhb0yn357w1j6zm</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:53:23.111+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsittqn20bhb0yn357w1j6zm"/>
  <title>OFNL Maintenance: Colchester, CO5 and Maldon, CM9</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:53:23</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Colchester, CO5 and Maldon, CM9

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsitw0jc0ahf0rpqmyzd5rhm</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:55:09.252+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsitw0jc0ahf0rpqmyzd5rhm"/>
  <title>OFNL Maintenance: Walton on the Naze, CO14 and Frinton on Sea, CO13</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:55:09</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Walton on the Naze, CO14 and Frinton on Sea, CO13

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsitz6hx0ak41bn30cipzzqk</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:57:36.946+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsitz6hx0ak41bn30cipzzqk"/>
  <title>OFNL Maintenance:  Manningtree, CO11, Colchester and Essex, CO4</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:57:36</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Manningtree, CO11, Colchester and Essex, CO4

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsiu17qx0akn1bn3e7cxh6yp</id>
  <published>2026-08-17T22:00:00.000+00:00</published>
  <updated>2026-08-07T10:59:11.874+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsiu17qx0akn1bn3e7cxh6yp"/>
  <title>OFNL Maintenance: Chelmsford, CM2 and CM3 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>10:59:11</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Chelmsford, CM2 and CM3 

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmrxktebt01qn0kqviehc84m7</id>
  <published>2026-08-16T23:00:00.000+00:00</published>
  <updated>2026-07-23T13:58:00.914+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmrxktebt01qn0kqviehc84m7"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>13:58:00</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; Peterborough

A brief Service Outage will be expected during the maintenance window..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmsg3zu7i03dc0kpsr8n22d6d</id>
  <published>2026-08-14T23:00:00.000+00:00</published>
  <updated>2026-08-05T13:14:45.305+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmsg3zu7i03dc0kpsr8n22d6d"/>
  <title>OFNL Maintenance: Cardiff, CF5</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>13:14:45</var> GMT+0</small><br /><strong>Identified</strong> -
  The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s):

&gt; Cardiff, CF5

Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible.

The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 15</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsrl1das0cw40kqifietvj6c</id>
  <published>2026-08-13T13:57:19.070+00:00</published>
  <updated>2026-08-13T13:57:19.070+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsrl1das0cw40kqifietvj6c"/>
  <title>OFNL Incident: Derby DE24</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>13:57:19</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Derby DE24

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest Update below:

&gt; **Update (13 Aug 2026 15:15hrs)**  
&gt; We are currently investigating an intermittent issue at this site that is causing some of our equipment to unexpectedly reboot.  
&gt;  
&gt; An engineer is on their way to the site and is expected to arrive at approximately 17:00 to assist with our ongoing investigations.  
&gt;  
&gt; We apologise for the intermittent nature of this fault and understand the disruption this may cause. Our teams are working to identify the root cause and restore service stability as quickly as possible.  
&gt;  
&gt; Please do not reboot your equipment at this time, as this may impact our ability to investigate the issue.  
&gt;  
&gt; We will provide a further update as soon as more information becomes available..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>16:17:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (13 Aug 2026 17:17hrs)**  
&gt; Our engineer attended the site and carried out extensive troubleshooting on the on-site equipment.  
&gt;  
&gt; Unfortunately, the issue could not be resolved during this visit. However, we believe the fault has been isolated to a specific piece of equipment and have identified the component that requires replacement.  
&gt;  
&gt; As this part is not currently available on-site, arrangements are being made for another engineer to collect the replacement component and attend site to complete the swap-out..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>18:52:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (13 Aug 2026 19:52hrs)**  
&gt; We have successfully sourced the replacement part required to resolve the issue on site. Our engineer is currently collecting the part and will then travel to the site to carry out the necessary work.  
&gt;  
&gt; The current estimated time of arrival is 22:30.  
&gt;  
&gt; Thank you for your patience and understanding while we work to restore service as quickly as possible..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>23:10:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below:

&gt; **Update (14 Aug 2026 00:10hrs)**  
&gt; Following the successful replacement of the faulty hardware component by our engineers on site, all affected services have now fully recovered.  
&gt;  
&gt; We have continued to monitor service performance since the recovery and are confident that the issue has been fully resolved.  
&gt;  
&gt; Thank you for your patience and understanding throughout this incident..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>23:10:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please see the latest update below:

**Update (14 Aug 2026 00:10hrs)**  
This incident was closed on Friday, August 14th, 2026 at 00:10hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsriogix0b680rqivxe2dxpp</id>
  <published>2026-08-13T12:17:00.000+00:00</published>
  <updated>2026-08-13T12:17:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsriogix0b680rqivxe2dxpp"/>
  <title>OFNL Incident: Margate CT9</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>12:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* Margate CT9

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>14:14:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (13 Aug 2026 15:14hrs)**  
&gt; A key piece of equipment at our site is proving to be unstable, causing intermittent loss of phone and Internet service.  
&gt;  
&gt; Services have stabilised for the moment.  
&gt;  
&gt; We are arranging for the equipment to be replaced today, which will incur a further short interruption to services.  
&gt;  
&gt; We will provide a further update as soon as we have a clear ETA for the engineer and replacement equipment.  
&gt;  
&gt; Please do not reset your equipment..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>18:14:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below:

&gt; **Update (13 Aug 2026 19:54hrs)**  
&gt; The attending third-party engineer has now arrived on site and will be replacing the faulty equipment. During this work, customers may experience a brief interruption to services that have already been restored.  
&gt;  
&gt; Once the equipment replacement has been completed, we will carry out thorough testing and monitoring to ensure all services remain stable and operating as expected.  
&gt;  
&gt; Thank you for your patience and understanding while we complete this work..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>23:14:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below:

&gt; **Update (14 Aug 2026 00:20hrs)**  
&gt; Following the efforts of the attending third-party engineer, services have now been successfully restored to the site.  
&gt;  
&gt; Due to the intermittent nature of the fault when it was first identified, we will continue to closely monitor service stability to ensure there are no further issues.  
&gt;  
&gt; Thank you for your patience and understanding throughout this incident..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>23:14:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please see the latest update below:

**Update (14 Aug 2026 00:20hrs)**  
This incident was closed on Friday, August 14th, 2026 at 00:20hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsok13a207wj0zlo2o9vv8v1</id>
  <published>2026-08-11T11:05:47.323+00:00</published>
  <updated>2026-08-11T11:05:47.323+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsok13a207wj0zlo2o9vv8v1"/>
  <title>OFNL Incident: SG8 Royston </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 9 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>11:05:47</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* SG8 Royston

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>11:42:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update from OFNL:

&gt; **Update (11 Aug 2026 12:42hrs)**  
&gt; We have identified that the fault does not reside within the OFNL network and has been traced to a third-party provider responsible for service delivery in this area.  
&gt;  
&gt; The provider&#039;s engineering teams are actively investigating and working to restore service as quickly as possible.  
&gt;  
&gt; Further updates will be provided as soon as additional information becomes available..</p>
<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>12:15:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update from OFNL:

&gt; **Update (11 Aug 2026 13:15hrs)**  
&gt; Work to restore service was completed at 12:43 on 11/08/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>12:15:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please see the latest update from OFNL:

&gt; **Update (11 Aug 2026 13:15hrs)**  
&gt; This incident was closed on Tuesday, August 11th, 2026 at 13:15hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsn6axfr1aou0yn360qzo452</id>
  <published>2026-08-10T11:30:00.000+00:00</published>
  <updated>2026-08-10T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsn6axfr1aou0yn360qzo452"/>
  <title>Freedom Fibre Incident: WA16</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Freedom Fibre</p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s):

WA16

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>11:30:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsd4gh9109qx1asw9zo5bzmz</id>
  <published>2026-08-03T10:00:44.661+00:00</published>
  <updated>2026-08-03T10:00:44.661+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsd4gh9109qx1asw9zo5bzmz"/>
  <title>OFNL Incident: Ruddington NG11</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 59 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>10:00:44</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* Ruddington NG11

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update from OFNL:

&gt; **Update (03 Aug 2026 11:58hrs)**  
&gt; Work to restore service was completed at 11:55 on 03/08/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmsd25yb009r60zl8894t8nbq</id>
  <published>2026-08-03T09:56:00.000+00:00</published>
  <updated>2026-08-03T09:56:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmsd25yb009r60zl8894t8nbq"/>
  <title>OFNL Incident:  Pinhoe EX1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:56:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Pinhoe EX1

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:56:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest Update from OFNL Below:

&gt; **Update (03 Aug 2026 11:10hrs)**  
&gt; The outage at this site was caused by fibre works at an adjacent site that caused an unexpected fibre break. Our engineers on-site repaired the fault immediately.  
&gt;  
&gt; Work to restore service was completed at 10:58 on 03/08/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:58:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cms8m3yao01w81aql81freixi</id>
  <published>2026-07-31T07:19:39.712+00:00</published>
  <updated>2026-07-31T07:19:39.712+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cms8m3yao01w81aql81freixi"/>
  <title>OFNL Incident: GL7</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 3 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>07:19:39</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Cirencester GL7.

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:03:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cms4j53ps001p0kma3661q3pq</id>
  <published>2026-07-28T09:30:04.332+00:00</published>
  <updated>2026-07-28T09:30:04.332+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cms4j53ps001p0kma3661q3pq"/>
  <title>OFNL Incident: Royston SG8</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>09:30:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* Royston SG8

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>09:30:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cms31z1860s1x1amt65ykw06r</id>
  <published>2026-07-27T08:10:00.000+00:00</published>
  <updated>2026-07-27T09:57:52.306+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cms31z1860s1x1amt65ykw06r"/>
  <title>Freedom Fibre Incident: CW9 &amp; WA16</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days and 10 hours</p>
    <p><strong>Affected Components:</strong> Freedom Fibre</p>
    <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>09:57:52</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please find the latest update below:

&gt; We are expecting the engineer to arrive on site shortly. Further updates will be sent once we receive an update from the engineer..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>08:10:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s):

&gt; **CW9**

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>10:44:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Following the latest updates with Freedom Fibre, we are now aware that this incident is also affecting WA16.

We will now update the incident title to display CW9 and WA16, as these are the known affected areas at this time..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>11:14:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please find the latest update:

&gt; Engineer is onsite and has identified the outage is caused by damaged fibre. Engineer is locating the site and extent of the damaged fibre but work to restore service can take place..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please find the latest update below:

&gt; Engineering&#039;s Investigation into the precise location and extent of the damaged fibre is ongoing, further updates will be provided as they become available..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>14:20:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please find the latest update below:

&gt; Engineers have replaced the damaged fibres, and we can confirm we have seen service restoration..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrvyj6yh071s0rs6h5fz79tp</id>
  <published>2026-07-22T10:33:00.000+00:00</published>
  <updated>2026-07-22T10:33:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrvyj6yh071s0rs6h5fz79tp"/>
  <title>OFNL Incident: Doncaster S62 DN11 S63.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 4 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>10:33:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Doncaster S62 DN11 S63.

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>12:10:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (22 Jul 2026 13:10hrs)**  
&gt; Following extensive investigation into this service fault, we believe the issue is related to third-party vendor equipment. We have raised this with the vendor and are working closely with them to restore service as quickly as possible.  
&gt;  
&gt; We apologise for the disruption and appreciate your patience while we work towards a resolution..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>14:55:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrqnhg8e05ru0sn0k5of3e1e</id>
  <published>2026-07-18T14:00:00.000+00:00</published>
  <updated>2026-07-20T14:43:47.982+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrqnhg8e05ru0sn0k5of3e1e"/>
  <title>OFNL Incident: Woking GU24</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 44 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>14:43:47</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Woking GU24

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:36:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update:

&gt; **Update (18 Jul 2026 16:36hrs)**  
&gt; An OFNL engineering team has been dispatched to site and is working with our third-party provider to investigate the reported fault.  
&gt;  
&gt; We will provide further updates as soon as more information becomes available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrkepeeq02zq1aphj1i4iqyz</id>
  <published>2026-07-14T07:19:00.000+00:00</published>
  <updated>2026-07-14T07:19:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrkepeeq02zq1aphj1i4iqyz"/>
  <title>OFNL Incident: N1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>07:19:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Hoxton N1

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>08:28:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; We are continuing to work closely with the power company to restore services as quickly and safely as possible.  
&gt;  
&gt; The power company has confirmed that a generator has arrived on site.  
&gt;  
&gt; However, due to public safety requirements, it cannot be connected at this time.  
&gt;  
&gt; Additional equipment is currently on its way to the site to enable the generator to be installed safely.  
&gt;  
&gt; This equipment is expected to arrive by 12:00pm, after which engineers will begin work to restore power to our equipment and other affected services.  
&gt;  
&gt; Once power has been restored, phone and internet services are expected to return.  
&gt;  
&gt; Please do not switch off or restart your equipment at this time.  
&gt;  
&gt; We appreciate your patience and understanding while this work is completed, and we sincerely apologise for the prolonged disruption caused by this incident..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please find the latest update below:

&gt; Power to our equipment and parts of the building has been restored.  
&gt;  
&gt; A temporary generator is in place nearby and there may be disruption to power and services over the next week as the failed power equipment is replaced by the power provider.  
&gt;  
&gt; Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>11:49:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update from OFNL:

&gt; **Update (14 Jul 2026 12:49hrs)**  
&gt; The power company has not yet restored power to the building housing our network equipment and is continuing to work actively to resolve the issue.  
&gt;  
&gt; Once the wider power outage has been resolved and power is restored to the site, internet and telephone services are expected to return automatically.  
&gt;  
&gt; At this time, we do not have a revised estimated time for power restoration.  
&gt;  
&gt; We are working closely with the power provider and will keep you updated as further information becomes available..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:07:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; The power company is currently unable to provide temporary power to our equipment room. They are exploring options to resolve the issue; however, restoring temporary power will take some time. Based on the latest information, we anticipate a delay of multiple hours before temporary power can be established..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrhwno3r0uxi0zq65riorrbj</id>
  <published>2026-07-12T14:08:00.000+00:00</published>
  <updated>2026-07-12T21:10:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrhwno3r0uxi0zq65riorrbj"/>
  <title>OFNL Incident: Huntingdon PE28</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>21:10:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please find the latest update below:

&gt; Our third-party supplier has not found any faults in their network.  
&gt;  
&gt; Internet services as this site have remained stable.  
&gt;  
&gt; Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>14:08:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s): 

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrdb7cqx01cs0rlaqu6ub4yn</id>
  <published>2026-07-09T09:23:00.000+00:00</published>
  <updated>2026-07-09T09:23:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrdb7cqx01cs0rlaqu6ub4yn"/>
  <title>OFNL Incident: Greenwich SE10</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 31 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>09:23:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Greenwich SE10

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>10:54:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update from OFNL below:

&gt; **Update (09 Jul 2026 11:54hrs)**  
&gt; Work to restore service was completed at 11:50 on 09/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>10:54:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please see latest update below:

**Update (09 Jul 2026 11:54hrs)**  
This incident was closed on Thursday, July 9th, 2026 at 11:54hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmrc22x7a02hn0zqjr7is1nnk</id>
  <published>2026-07-08T12:00:00.000+00:00</published>
  <updated>2026-07-08T12:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmrc22x7a02hn0zqjr7is1nnk"/>
  <title>OFNL Incident: Maidenhead SL6.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Maidenhead SL6.

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmr7mp6u90y3e0kqfrve7n9bb</id>
  <published>2026-07-05T08:00:00.000+00:00</published>
  <updated>2026-07-05T08:27:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmr7mp6u90y3e0kqfrve7n9bb"/>
  <title>OFNL Incident: Pevensey BN23 BN24</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>08:27:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find OFNL&#039;s latest reply:

&gt; **Update (05 Jul 2026 09:27hrs)**  
&gt; Our engineer is on route to site and has a current ETA of 12:00.  
&gt;  
&gt; Once the engineer is on site, we will work to restore power to equipment as soon as possible to bring services online and continue to investigate main power supply issues..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Pevensey BN23 BN24

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>11:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest here:

&gt; **Update (05 Jul 2026 12:40hrs)**  
&gt; Our engineer is on site and completing testing of site equipment, we have identified we no mains power reaching the cabinet equipment and will require attendance of the electrical supplier.  
&gt;  
&gt; In the meantime our engineer is charging the on site batteries to restore back up power to the cab and ensure services restore to customers.  
&gt;  
&gt; We will continue to update you as we progress to resolving this fault..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>12:33:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update:

&gt; **Update (05 Jul 2026 13:33hrs)**  
&gt; Our on site engineer has managed to charge the cabinet battery back ups and we are no seeing restoration of key equipment.  
&gt;  
&gt; We are also observing customer services restoring across the site. We will continue to monitor this carefully to ensure equipment remains powered up via the battery back ups.  
&gt;  
&gt; We have also had confirmation of third party engineer attending site to look into mains power issue, current ETA is 17:00.  
&gt;  
&gt; Thank you for your patience while we work on this fault..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>14:44:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please find the latest:

&gt; **Update (05 Jul 2026 15:44hrs)**  
&gt; Third party engineers have completed works on site to restore mains power to our cabinet, there is still further works required so we may see this further disrupted.  
&gt;  
&gt; We still have battery back up power restored on site and this will prevent any further impact to customer services. Our engineer will also remain on standby on site for now..</p>
<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>14:55:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please find their resolving statement here:

&gt; **Update (05 Jul 2026 15:55hrs)**  
&gt; Work to restore service was completed at 13:25 on 05/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; We now have mains power and battery back up power to cope with any further mains disruption, we do not expect any further customer service impact.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmr0fmkwa06e00kphl22yeg8c</id>
  <published>2026-06-30T09:00:00.000+00:00</published>
  <updated>2026-06-30T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmr0fmkwa06e00kphl22yeg8c"/>
  <title>Freedom Fibre Incident: INC10000485 (TF6 &amp; SY4)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> Freedom Fibre</p>
    <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s):

&gt; TF6 &amp; SY4

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>13:57:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Freedom Fibre and their engineers are still on site working through this issue, and reconnecting the fibres at this time.

Next update is scheduled for or around 17:30 today..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>16:26:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Engineers are still on site working on this.

The next update should come from Freedom Fibre at around 19:30, 30/06/2026\. This is beyond our office opening times, though we will do our best to have these updates before we close and when we reopen.

Thank you for your patience..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>20:53:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Since 9:53 on 30/06/2026, the Freedom Fibre engineers confirmed that all services were restored following the repair of the fibre connection.

If you are still experiencing issues, please email us at Support@MTHNetworks.com, and we will provide support accordingly!

Thank you for your patience and understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmr0feaoa06i70zrrl2ko5s5v</id>
  <published>2026-06-30T08:30:00.000+00:00</published>
  <updated>2026-06-30T08:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmr0feaoa06i70zrrl2ko5s5v"/>
  <title>OFNL Incident: Derby DE3</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 5 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* Derby DE3

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:17:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmr0fdws9000f0zmqeexsn9u2</id>
  <published>2026-06-29T20:35:00.000+00:00</published>
  <updated>2026-06-29T20:35:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmr0fdws9000f0zmqeexsn9u2"/>
  <title>MS3 Incident: Grimsby </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> MS3</p>
    <p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>20:35:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Hi,

The MS3 Network has made us aware of an incident experienced in the Grimsby area. As of 21:35, on 29/06/2026, this incident was resolved. 

A long-term solution has been implemented, and so we are happy to close this incident.

We thank you for your patience and understanding.

Kind regards,

Your MTH Networks Team..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqumwfeh09122onxmpejartk</id>
  <published>2026-06-26T07:17:00.000+00:00</published>
  <updated>2026-06-26T07:17:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqumwfeh09122onxmpejartk"/>
  <title>OFNL Incident: Westoning MK45</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 7 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>07:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Westoning MK45

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>09:24:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see latest update from OFNL below:

&gt; **Update (26 Jun 2026 10:24hrs)**  
&gt; An OFNL engineering team has been dispatched to site, with an estimated time of arrival of 12:00 on 26/06/2026, to carry out fault investigation.  
&gt;  
&gt; This issue has also been raised with our third-party provider, who are currently investigating their equipment in parallel.  
&gt;  
&gt; Further updates will be provided as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:39:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see update from OFNL below:

&gt; **Update (26 Jun 2026 13:39hrs)**  
&gt; Engineering teams are currently on site investigating the fibre fault. We are also actively liaising with our third-party provider for further updates.  
&gt;  
&gt; Additional updates will be provided as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>16:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see latest update below:

&gt; **Update (26 Jun 2026 17:17hrs)**  
&gt; Our engineers have completed testing and cannot find fault within our purview.  
&gt;  
&gt; We have escalated the fault to a third-party supplier and are awaiting feedback from their testing.  
&gt;  
&gt; Our third-party supplier is unable to provide any timeframe for a response due to the heatwave that has caused major disruption across the UK telecommunications network, which in turn is influencing response times from engineering teams.  
&gt;  
&gt; Further updates will be provided as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>20:13:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see update below:

&gt; **Update (27 Jun 2026 21:13hrs)**  
&gt; The third-party supplier has arranged for an engineer to investigate the equipment outside of our network that supplies this area.  
&gt;  
&gt; We will continue to provide updates as soon as they become available..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>10:57:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see update below:

**Update (27 Jun 2026 11:57hrs)**  
We are continuing to work with our third-party supplier to implement a fix for this issue. At present, we are awaiting their engineers to attend site and carry out the required work on their equipment to restore services.  
  
We will provide further information as it becomes available to us..</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see update below:

&gt; **Update (28 Jun 2026 13:20hrs)**  
&gt; We are continuing to work closely with a third-party supplier to resolve this issue. Due to the complexity of the network, resolution is taking longer than initially anticipated.  
&gt;  
&gt; We sincerely apologise for any inconvenience caused and appreciate your patience while we work to restore services. Engineers are currently on-site and actively working to resolve the issue as quickly as possible.  
&gt;  
&gt; We will provide further updates as soon as more information becomes available later today..</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see update below:

&gt; **Update (28 Jun 2026 18:50hrs)**  
&gt; Due to the complexity of this fault, our engineers were unable to resolve the issue today. The matter has now been escalated through the appropriate channels to bring services back online asap.  
&gt; We will continue to monitor the situation closely and provide further updates as soon as new information becomes available..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:17:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqt7h1530b5g2jru1e3uy633</id>
  <published>2026-06-25T07:13:00.000+00:00</published>
  <updated>2026-06-25T07:13:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqt7h1530b5g2jru1e3uy633"/>
  <title>OFNL Incident: Barnsley S73</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 7 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:13:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Barnsley S73

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>10:17:44</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (25 Jun 2026 10:57hrs)**  
&gt; Following extensive remote diagnostics, we have deployed a field engineer to carry out further on-site investigations.  
&gt;  
&gt; Our engineer is currently on site and continuing to investigate the issue.  
&gt;  
&gt; We will provide a further update once this investigation is complete and we move forward with resolving the fault.  
&gt;  
&gt; Thank you for your patience while we work to resolve this for you..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>12:33:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below from OFNL:

&gt; **Update (25 Jun 2026 13:33hrs)**  
&gt; Our engineer has completed a comprehensive on-site investigation, and we believe the fault location has now been identified.  
&gt;  
&gt; Due to the nature and location of the issue, a specialist engineering team is required to carry out further investigation and complete the necessary repairs to restore service.  
&gt;  
&gt; We have arranged for their deployment and will provide an update as soon as we have confirmation of their arrival time.  
&gt;  
&gt; Thank you for your patience while we work to resolve this fault as quickly as possible..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:18:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqt7gcmz0q372ilnbpg9hphs</id>
  <published>2026-06-25T07:06:00.000+00:00</published>
  <updated>2026-06-25T08:21:41.657+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqt7gcmz0q372ilnbpg9hphs"/>
  <title>OFNL Incident:  London E14 and E3</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 7 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>08:21:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network have confirmed this incident is also impacting the **E3** region..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:06:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; London E14, E3

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>10:18:12</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (25 Jun 2026 10:45hrs)**  
&gt; We now see that the problem is not on our network, but the network of a third party that supports ours.  
&gt;  
&gt; We are talking to the third party, and they are working on a fix.  
&gt;  
&gt; We will update you again by 11:30..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>11:18:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below from OFNL:

&gt; **Update (25 Jun 2026 12:54hrs)**  
&gt; Our Third-Party Supplier has identified heat related issues at a local Openreach Exchange, which are being worked on.  
&gt;  
&gt; Work to restore service was completed by our Third-Party supplier at 11:30 on 25/06/2026.  
&gt;  
&gt; Customers should now find services to be working as expected.  
&gt;  
&gt; We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:18:13</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqs06gq5007f2iocpwpopq5x</id>
  <published>2026-06-24T11:38:00.000+00:00</published>
  <updated>2026-06-25T07:52:20.004+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqs06gq5007f2iocpwpopq5x"/>
  <title>OFNL Incident: BIrningham, B4</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:52:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>15:08:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find OFNL&#039;s latest update:

&gt; **Update (24 Jun 2026 16:08hrs)**  
&gt; We’ve identified that the issue is not within our systems, but originates from one of our third-party providers.  
&gt; Their team is actively working on a fix.  
&gt;  
&gt; We will update you again by 18:00..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>11:38:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

* BIrningham, B4

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqrw1lp406t62iqqkkkp8tqv</id>
  <published>2026-06-24T09:41:00.000+00:00</published>
  <updated>2026-06-24T12:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqrw1lp406t62iqqkkkp8tqv"/>
  <title>OFNL Incident: Curtis Fields DT4</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>12:07:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update from OFNL below:

&gt; **Update (24 Jun 2026 14:41hrs)**  
&gt; Work to restore service was completed at 14:07 on 24/06/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
&gt;  
&gt; Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
&gt;  
&gt; We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>10:27:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest update below from OFNL:

**Update (24 Jun 2026 11:27hrs)**  
We are continuing to investigate the problem and suspect there has been an equipment failure.  
  
An engineer is travelling to site with spare equipment. ETA 14:30.  
  
Will provide a further update by 13:30..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>13:41:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Update (24 Jun 2026 14:41hrs)**  
This incident was closed on Wednesday, June 24th, 2026 at 14:41hrs..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>09:41:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Curtis Fields DT4

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmqov9hat0ejk2onu8zq2p9q6</id>
  <published>2026-06-22T07:00:47.958+00:00</published>
  <updated>2026-06-22T08:53:38.097+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmqov9hat0ejk2onu8zq2p9q6"/>
  <title>OFNL Incident: PE7, SS4 TF4</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>08:53:38</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (22 Jun 2026 09:48hrs)**  
&gt; Our third-party vendor is actively working to resolve the issue from their side. We remain in close communication with them and are receiving regular updates on their progress.  
&gt;  
&gt; In the meantime, we will continue to monitor the situation on our end. Thank you for your patience..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>10:30:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

&gt; **Update (22 Jun 2026 11:11hrs)**  
&gt; Following ongoing work with our third-party vendor, services have now been restored across all sites, and we are seeing continued recovery for affected customers.  
&gt;  
&gt; We are continuing our investigation to determine the root cause of this incident and will closely monitor services to ensure stability.  
&gt;  
&gt; This incident notice will remain open while our investigation is ongoing, and we will provide further updates as required..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:00:47</var> GMT+0</small><br /><strong>Investigating</strong> -
  The OFNL Network has made us aware of an ongoing incident in the following location(s):

&gt; Peterborough PE7, Rochford SS4, Telford TF4.

**PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!**

We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible.

Thank you for your understanding..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:35:53</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (22 Jun 2026 08:30hrs)**  
&gt; We have identified that the issue currently resides with a third-party vendor. The matter has been escalated to their highest level of support, and we are awaiting their response.  
&gt;  
&gt; We are actively monitoring the situation and will provide an update as soon as we receive any meaningful information.  
&gt;  
&gt; Thank you for your patience while we work to resolve this incident..</p>

        ]]>
  </content>
</entry>

</feed>