<?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-06-09T23:00:00.000+00:00</updated>
  <author>
    <name>MTH Networks</name>
  </author>
  
<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmotw0kg50bsql0b2neqb52km</id>
  <published>2026-06-09T23:00:00.000+00:00</published>
  <updated>2026-06-09T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmotw0kg50bsql0b2neqb52km"/>
  <title>CityFibre Maintenance</title>

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

&gt; Milton Keyenes

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmp3v17i902irqklrbvdfuth3</id>
  <published>2026-06-06T19:00:00.000+00:00</published>
  <updated>2026-06-06T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp3v17i902irqklrbvdfuth3"/>
  <title>CityFibre Maintenance</title>

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

&gt; Edinburgh

**Works will take place over the course of 2 nights; customers will experience an outage on 1 out of the 2 nights only. Outage will be for approx. 2 hours per service.**

Maintenance will commence at 20:00 then cease at 08:00 on each night. All services will be **At Risk** during the whole maintenance window.

**Schedule of Works**

| Night | Commence   |       | Cease |            |       |
| ----- | ---------- | ----- | ----- | ---------- | ----- |
| 1     | 06/06/2026 | 20:00 |       | 07/06/2026 | 08:00 |
| 2     | 07/06/2026 | 20:00 |       | 08/06/2026 | 08:00 |.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmoid4pp401ffkatd5ajfroaq</id>
  <published>2026-05-27T23:00:00.000+00:00</published>
  <updated>2026-05-27T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmoid4pp401ffkatd5ajfroaq"/>
  <title>CityFibre Maintenance</title>

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

&gt; Potters Bar, Chelmsford

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmob9tiqs0031ol4jsm2do24t</id>
  <published>2026-05-24T23:00:00.000+00:00</published>
  <updated>2026-05-24T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmob9tiqs0031ol4jsm2do24t"/>
  <title>CityFibre Maintenance</title>

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

&gt; Derby

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

        ]]>
  </content>
</entry>

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

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

&gt; Crawley, Dundee, Derby

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpayx4gu01lzpadakz935miq</id>
  <published>2026-05-19T19:00:00.000+00:00</published>
  <updated>2026-05-19T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpayx4gu01lzpadakz935miq"/>
  <title>OFNL Maintenance: CB23 CB1 CB2 CB25 CB5 CB3</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>19:00:00</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):

* CB23 CB1 CB2 CB25 CB5 CB3

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/cmpayw9wn01o0qmjsbx7u8ers</id>
  <published>2026-05-19T19:00:00.000+00:00</published>
  <updated>2026-05-19T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpayw9wn01o0qmjsbx7u8ers"/>
  <title>OFNL Maintenance: CB10 CB22</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>19:00:00</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):

* CB10 CB22

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/cmpayvobb021zqmjar878m4n0</id>
  <published>2026-05-19T19:00:00.000+00:00</published>
  <updated>2026-05-19T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpayvobb021zqmjar878m4n0"/>
  <title>OFNL Maintenance: CB10 CB11</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>19:00:00</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):

* CB10 CB11

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/cmpayxr7u0f5bpck86hgir6w6</id>
  <published>2026-05-19T07:00:00.000+00:00</published>
  <updated>2026-05-19T07:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpayxr7u0f5bpck86hgir6w6"/>
  <title>OFNL Maintenance: CM22 CM77 CM23</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>07:00:00</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):

* CM22 CM77 CM23

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/cmpay9m0500hqqkm2rdw6rxe1</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay9m0500hqqkm2rdw6rxe1"/>
  <title>OFNL Maintenance: B1 B18 B3 B5</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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; **B1 B18 B3 B5**

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/cmpay92n301atpada6mfnpgy5</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay92n301atpada6mfnpgy5"/>
  <title>OFNL Maintenance: ME13</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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; * ME13

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/cmpay8ie701rnqmjhhwupjiik</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay8ie701rnqmjhhwupjiik"/>
  <title>OFNL Maintenance: TF4</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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):

* TF4

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/cmpay7q690etdpcjb8xf1paqd</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay7q690etdpcjb8xf1paqd"/>
  <title>OFNL Maintenance: CW1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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):

* CW1

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/cmpay76b709h1qjjr1j3o3jib</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay76b709h1qjjr1j3o3jib"/>
  <title>OFNL Maintenance: G75</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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):

* G75

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/cmpay6n0m00g7qklor27yf5bq</id>
  <published>2026-05-18T23:00:00.000+00:00</published>
  <updated>2026-05-18T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpay6n0m00g7qklor27yf5bq"/>
  <title>OFNL Maintenance: SG14</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>23:00:00</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):

* SG14

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/cmp6um1xm019tpblzs7k7hkea</id>
  <published>2026-05-18T08:00:00.000+00:00</published>
  <updated>2026-05-18T08:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp6um1xm019tpblzs7k7hkea"/>
  <title>OFNL Maintenance: Bedford MK45</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>08:00:00</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; **Bedford MK45**

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>May <var data-var='date'> 18</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmp75g1u10535pclzydibpbfk</id>
  <published>2026-05-18T07:00:00.000+00:00</published>
  <updated>2026-05-18T07:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp75g1u10535pclzydibpbfk"/>
  <title>MS3 Maintenance: DN17</title>

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

* Poole Drive
* Parkin Road

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

The MS3 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>May <var data-var='date'> 18</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmp70r5dg0i63npmk6kxcfdd8</id>
  <published>2026-05-17T23:00:00.000+00:00</published>
  <updated>2026-05-17T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp70r5dg0i63npmk6kxcfdd8"/>
  <title>OFNL Maintenance: London NW6.</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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:00</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; **London NW6**

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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 18</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:Maintenance/cmp70qbqh08k6pa9tbxwdxfoz</id>
  <published>2026-05-17T23:00:00.000+00:00</published>
  <updated>2026-05-17T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp70qbqh08k6pa9tbxwdxfoz"/>
  <title>OFNL Maintenance: Peterborough PE6</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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:00</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; **Peterborough PE6**

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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 18</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:Maintenance/cmp70p8a20i4wnpmkeeuila80</id>
  <published>2026-05-17T23:00:00.000+00:00</published>
  <updated>2026-05-17T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp70p8a20i4wnpmkeeuila80"/>
  <title>OFNL Maintenance: Hook RG27</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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:00</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; **Hook RG27**

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>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 18</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:Maintenance/cmobi47b3005gzgds00zphbed</id>
  <published>2026-05-17T23:00:00.000+00:00</published>
  <updated>2026-05-17T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmobi47b3005gzgds00zphbed"/>
  <title>CityFibre Maintenance</title>

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

&gt; Bentley Heath, Solihull, Stratford-upon-Avon

A brief Service Outage will be expected during the maintenance window..</p>
<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 18</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/cmpauojg50e4fpcjt02m1rp5p</id>
  <published>2026-05-17T19:29:00.000+00:00</published>
  <updated>2026-05-17T19:29:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpauojg50e4fpcjt02m1rp5p"/>
  <title>OFNL Incident: Corby NN18</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>19:29: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):

* Corby NN18

**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>May <var data-var='date'> 17</var>, <var data-var='time'>19:29:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  **Update (18 May 2026 08:07hrs)**  
We identified that the problem originated within one of our third-party providers netwok in this area.  
  
Work to restore service was completed at 21:02 on 17/05/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
  
Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
  
We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>07:10:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Update (18 May 2026 08:07hrs)**  
This incident was closed on Monday, May 18th, 2026 at 08:07hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmobi31ib006gbk88vkln2vcr</id>
  <published>2026-05-15T23:00:00.000+00:00</published>
  <updated>2026-05-15T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmobi31ib006gbk88vkln2vcr"/>
  <title>CityFibre Maintenance</title>

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

&gt; Rotherham

A brief Service Outage will be expected during the maintenance window..</p>
<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 16</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:Maintenance/cmp70pqw9045jpcml6ph4ble1</id>
  <published>2026-05-15T23:00:00.000+00:00</published>
  <updated>2026-05-15T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmp70pqw9045jpcml6ph4ble1"/>
  <title>OFNL Maintenance: Peterborough PE7</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>May <var data-var='date'> 15</var>, <var data-var='time'>23:00:00</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; **Peterborough PE7**

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>May <var data-var='date'> 15</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 16</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:Maintenance/cmob91dn4004712ovo5u30z0b</id>
  <published>2026-05-15T19:00:00.000+00:00</published>
  <updated>2026-05-15T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmob91dn4004712ovo5u30z0b"/>
  <title>CityFibre Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day and 12 hours</p>
    <p><strong>Affected Components:</strong> CityFibre</p>
    <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas:

&gt; Barnsley

Customers will experience a **2-hour outage on Night 1 and Night 2** during the maintenance window.

**Schedule of Works**

| Night | Commence   |       | Cease |            |       |
| ----- | ---------- | ----- | ----- | ---------- | ----- |
| 1     | 15/05/2026 | 20:00 |       | 16/05/2026 | 08:00 |
| 2     | 16/05/2026 | 20:00 |       | 17/05/2026 | 08:00 |.</p>
<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

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

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

&gt; Reading

A brief Service Outage will be expected during the maintenance window..</p>
<p><small>May <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>May <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/cmp590r0c00gvp8jintvkjscz</id>
  <published>2026-05-14T08:30:00.000+00:00</published>
  <updated>2026-05-14T08:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmp590r0c00gvp8jintvkjscz"/>
  <title>OFNL Incident: BN24, BN26 Dittons Road </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 14</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):

* **BN24, BN26 Dittons Road**

**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>May <var data-var='date'> 14</var>, <var data-var='time'>09:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest update from OFNL below:

&gt; **Update (14 May 2026 10:17hrs)** 
&gt; **We are continuing to investigate the issue. A technician is currently en route to site and is expected to arrive by 12:00.** 
&gt; **At present, the service is intermittently dropping out; however, we can see that the site is currently up and running.** 
&gt; **We will provide further updates by 12:30 once the engineer is on-site and has completed initial checks.**.</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>11:09:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update from OFNL below:

&gt; **Update (14 May 2026 12:09hrs)** 
&gt; **The fault has been identified as being caused by third-party works on the network. We have engaged specialist engineers to implement a fix and restore the site to full service.** 
&gt; **Due to the ongoing third-party activity, we are required to coordinate closely with them to safely carry out the necessary remediation and bring the site back online.** 
&gt; **We will provide a further update by 14:00.**.</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>11:09: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/cmp2gn9xj01zh3asj6itb6m0x</id>
  <published>2026-05-12T10:01:00.160+00:00</published>
  <updated>2026-05-12T10:01:00.160+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmp2gn9xj01zh3asj6itb6m0x"/>
  <title>OFNL Incident: Toftwood NR19</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>10:01: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; **Toftwood NR19**

  
**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>May <var data-var='date'> 12</var>, <var data-var='time'>10:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Hello all, 

OFNL have returned with an update for us. Please find this below:

&gt; **Update (12 May 2026 11:20hrs)**  
&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 14:00.

Once we have a further update by or around 2PM today, we will be sure to update it as we did here.

Thank you all..</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>13:20:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest Update below:

&gt; **Update (12 May 2026 14:27hrs)** 
&gt; **Work to restore service was completed at 13:38 on 12/05/26\. 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>May <var data-var='date'> 12</var>, <var data-var='time'>13:30: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/cmp1g7f4400q3pyidcyj2my5r</id>
  <published>2026-05-11T17:02:25.333+00:00</published>
  <updated>2026-05-11T17:02:25.333+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmp1g7f4400q3pyidcyj2my5r"/>
  <title>Continuation from NN12 Maintenance (11/05/2026)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>17:02:25</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good Evening all,

We are aware of a number of customers being offline after the given time frame of the NN12 maintenance this afternoon.

If you are affected by this, please reach out to [support@mthnetworks.com](mailto:support@mthnetworks.com) via your registered email on your account and we can assist you as soon as possible.

Although this is not yet concluded officially from OFNL, we wanted to post this should it come to a close, but connections are still offline.

We do apologise for the inconvenience caused by this.

Thank you for your understanding.

Kind regards,

Your MTH Networks Team..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmp10054r01f8bsc1tsxdvqs9</id>
  <published>2026-05-11T09:27:20.117+00:00</published>
  <updated>2026-05-11T09:27:20.117+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmp10054r01f8bsc1tsxdvqs9"/>
  <title>OFNL Incident: DA11</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 8 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>09:27:20</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; Gravesend DA11

**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>May <var data-var='date'> 11</var>, <var data-var='time'>09:27:48</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; We are still waiting for further feedback from our third-party supplier at this site, who are investigating a fault within their network.  
&gt;  
&gt; We apologise for there being no new information.  
&gt;  
&gt; We will update you again by 11:00 11/05/2026..</p>
<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>10:04:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see latest update below:

&gt; **Update (11 May 2026 11:04hrs)** 
&gt; **We can confirm that a third-party network engineer is now on site at the affected exchange and is actively investigating the fault within their network.** 
&gt; **At this stage, services remain impacted while diagnostics and repair work continue. This issue has been confirmed as being outside of our own network.** 
&gt; **Please continue not to reset your equipment, as services will recover automatically once the fault is resolved.** 
&gt; **We will provide a further update as soon as progress or a resolution timeframe becomes available.**.</p>
<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>10:04:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below:

&gt; **Update (11 May 2026 11:32hrs)** 
&gt; **Work to restore service was completed at 10:44 on 11/05/2026\. Customers should now find that services are operating as expected. We will continue to monitor the platform closely to ensure ongoing stability.** 
&gt; **Any issues experienced after this time should be treated as individual cases and reported through the usual support channels.** 
&gt; **We sincerely apologise for the inconvenience caused and thank you for your patience throughout this incident.**.</p>
<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>10:34:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmou6mr0m00oogowix3l1erwc</id>
  <published>2026-05-06T14:58:31.771+00:00</published>
  <updated>2026-05-06T14:58:31.771+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmou6mr0m00oogowix3l1erwc"/>
  <title>MS3 Incident: Scunthorpe </title>

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

Scunthorpe - All Areas

**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>May <var data-var='date'> 6</var>, <var data-var='time'>15:24:38</var> GMT+0</small><br /><strong>Identified</strong> -
  MS3 have provided us with the following update:

&gt; Dear Customer,
&gt; 
&gt; We have identified an issue which is causing a loss of service to all customer&#039;s in the Scunthorpe area and are still investigating.
&gt; 
&gt; We will provide the next update in 30 mins at 16:50..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>07:04:42</var> GMT+0</small><br /><strong>Resolved</strong> -
  Good morning all,

Please find the latest update from MS3:

&gt; Our carrier has confirmed that repairs have been fully completed and all services should now be back online.

  
We have observed the mass restoration of service, and so are glad to mirror MS3&#039;s advice that this incident has been resolved.

  
If you are still experiencing trouble, please reboot your router and MS3 modem (ONT). If you are using an MTH Networks router and the aforementioned reboots have not been successful in restoring your service, please perform a router reset by pressing and holding the RESET button for 20 seconds.

If you would like to seek further assistance, please find the various avenues for attaining our support below:

* Phone: 01536 661050
* Email: support@mthnetworks.com
* LiveChat: Accessible via our website

Our typical operating hours are as follows:

* Monday-Friday: 08:00-18:00
* Saturday &amp; Sunday: 11:00-20:00

_These hours may vary during Public and Bank Holidays._

**_As a result of this impact, we are experiencing an influx of calls and support requests, so wait times may be slightly elevated._**

As always, we want to thank you for your patience, your understanding and your cooperation with us whislt we work through this incident.

Kind regards,

Your MTH Networks..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>22:20:41</var> GMT+0</small><br /><strong>Identified</strong> -
  MS3 Networks have advised us:   
Our upstream carrier has confirmed that the new fibre cable continues to be installed on site, and the fibre engineer will begin splicing activities as soon as the cabling works are complete. 

This is a complex repair and as such, an estimated time for resolution (ETR) is not yet confirmed. Further updates will be shared as soon as additional information becomes available, including any confirmed timelines.

We continue recognise the impact this is having on your services and customers, and we are maintaining close engagement with the supplier to ensure progress remains the highest priority. .</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>16:21:20</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the update from MS3 below:

&gt; Dear Customer,
&gt; 
&gt; We have identified an issue which is causing a loss of service to all customer&#039;s in the Scunthorpe area and are still investigating.
&gt; 
&gt; We have an engineer on site at the moment with an additional engineer on route to site and the ETA for them is 6pm.
&gt; 
&gt; We have also raised this fault with our Network Partner, Virgin Media Business.
&gt; 
&gt; We will provide the next update in 30 mins at 17:50..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmou3x3800095cfddqgnknuql</id>
  <published>2026-05-06T13:30:00.000+00:00</published>
  <updated>2026-05-07T09:50:16.033+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmou3x3800095cfddqgnknuql"/>
  <title>OFNL Incident: TN12 Tonbridge</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>09:50:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13: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):

**TN12 Tonbridge.**

**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/cmots3qgo05hgi7atu2meoz9a</id>
  <published>2026-05-06T08:11:43.660+00:00</published>
  <updated>2026-05-06T08:11:43.660+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmots3qgo05hgi7atu2meoz9a"/>
  <title>Network Incident: NR9</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>08:11:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good morning,

We have received numerous reports from some customers in the NR9 region, who have continued to experience a lack of connection following the maintenance completed by The OFNL Network in the region yesterday. As a result, we are conducting a thorough investigation. We can confirm that this is not impacting all connections in the NR9 region. 

We will be in touch with any further updates.

Thank you for your patience and understanding with us whilst we work through this matter.

Kind regards,

Your MTH Networks..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>08:11:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmoskewz104dl7oz0er569gvo</id>
  <published>2026-05-05T11:39:00.000+00:00</published>
  <updated>2026-05-05T11:39:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmoskewz104dl7oz0er569gvo"/>
  <title>OFNL Incident: Polegate BN24 , BN26</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 22 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>11:39: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; **Polegate BN24 , BN26**

**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>May <var data-var='date'> 5</var>, <var data-var='time'>13:36:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the update below from OFNL:

&gt; **Update (05 May 2026 14:36hrs)** 
&gt; **We now see this issue is on the network of a third party carrier who supports our services in this area, we are working with them and hope to have another update by 16:00**.</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>09:50:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmoiv3jbd00vod48tmlo7lmnk</id>
  <published>2026-04-28T16:50:09.874+00:00</published>
  <updated>2026-04-28T16:50:09.874+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmoiv3jbd00vod48tmlo7lmnk"/>
  <title>Continuation From CM6 Maintenance (28/04/2026)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>16:50:09</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good Evening all,

We are aware of a number of customers being offline after the conclusion of the CM6 maintenance this afternoon. 

If you are affected by this, please reach out to [support@mthnetworks.com](mailto:support@mthnetworks.com) via your registered email on your account and we can assist you as soon as possible.

We do apologise for the inconvenience caused by this. 

Thank you for your understanding. 

Kind regards, 

Your MTH Networks Team. .</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>16:50:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  &gt; Hi All
&gt; 
&gt; This incident has been resolved. We will continue to monitor this from our end.
&gt; 
&gt; Any customers that do find any issues, please contact us through your email attached to your account, by sending an email to support@mthnetworks.com.
&gt; 
&gt; Thank you for your patience and cooperation throughout..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmoh591ip1b5w11w5ctk02dsy</id>
  <published>2026-04-27T11:04:00.000+00:00</published>
  <updated>2026-04-27T15:12:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmoh591ip1b5w11w5ctk02dsy"/>
  <title>OFNL Incident: YO23, YO25, YO26</title>

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

&gt; * **Update (27 Apr 2026 16:12hrs)**  
&gt; Engineers from our third-party vendor have attended site and completed fault resolution on the equipment they supply.  
&gt;    
&gt; Service restoration was completed at 15:33 on 27/04/2026, and customers should now find services operating as expected.  
&gt;    
&gt; We will continue to monitor services to ensure ongoing stability.  
&gt; Any issues experienced after this time should be treated as individual cases and reported through the usual channels.  
&gt;    
&gt; We apologise for the inconvenience caused and thank you for your patience throughout this incident..</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>15:12:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please see the latest update below:

&gt; **Update (27 Apr 2026 16:12hrs)** 
&gt; **This incident was closed on Monday, April 27th, 2026 at 16:12hrs.**.</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>11:04: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):

* YO23, YO25, YO26

**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>Apr <var data-var='date'> 27</var>, <var data-var='time'>12:04:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

**Update (27 Apr 2026 13:39hrs)**  
We’ve identified that the issue is not within our systems, but originates from one of our third-party providers.  
Their team is actively working on a fix.  
  
We will update you again by 16:00..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmoct6y0y00emnv94b80uo17f</id>
  <published>2026-04-24T11:04:00.000+00:00</published>
  <updated>2026-04-24T11:04:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmoct6y0y00emnv94b80uo17f"/>
  <title>OFNL Incident: NN17, NN18 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 11 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>11:04: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):

NN17, NN18 

**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>Apr <var data-var='date'> 24</var>, <var data-var='time'>11:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update from OFNL below:

&gt; **Update (24 Apr 2026 12:20hrs)** 
&gt; **We have confirmed that 54 customers are currently affected by this issue.** 
&gt;  
&gt; **To restore service, we need to replace a full card. This work will temporarily impact around 300 customers.** 
&gt;  
&gt; **The card replacement is scheduled for just after 14:00 today and will result in approximately 20 minutes of downtime for the additional customers.** 
&gt;  
&gt; **We apologise for any inconvenience caused and appreciate your patience while we complete this work.**.</p>
<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>14:56:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  Hello All,

Please find OFNL&#039;s latest update here:

&gt; **Update (24 Apr 2026 15:51hrs)**  
&gt; This incident was closed on Friday, April 24th, 2026 at 15:51hrs.
&gt; 
&gt; **Update (24 Apr 2026 15:51hrs)**  
&gt; The planned on-site card replacement has now been completed.  
&gt;  
&gt; We are confident that this has resolved the ongoing issue.  
&gt;  
&gt; The service will continue to be monitored as a precaution, however no further impact is anticipated.  
&gt;  
&gt; Thank you for your patience while we worked to resolve this fault.

Thank you for your patience regarding this case.

Should you experience any further issues, please contact us via Support@mthnetworks.com, and we will take a further look as soon as we can.

Thank you again,

Your MTH Networks Team..</p>
<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>16:51:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  Hello All,

Due to a few reports, we are reopening this ticket post.

We are seeing the same report across a select few connections where the connection is still offline, unfortunately.

Given this, our teams are now investigating, and we will relay more information here when we have it.

At this time, we do not have a time frame, and we will do our best to provide one, should we be able to.

Thank you for your understanding and patience.

Kind Regards,

Tommy.</p>
<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>11:15:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good Afternoon all,

Thank you for your patience so far. We are just posting this update to let you know that our work and efforts will be continuing over the weekend to resolve this.

At this time, we do not have a time frame to share as we are still working towards gaining more information.

Your patience and understanding is most appreciated, and you have our deepest apologies regarding this downtime with the service, especially over the weekend.

Despite this, we all wish you a lovely weekend. We appreciate and are very thankful for your cooperation during this time.

Kind Regards,

Your MTH Networks Team.</p>
<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>11:15:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  &gt; Hi All
&gt; 
&gt; This incident has been resolved. We will continue to monitor this from our end.
&gt; 
&gt; Any customers that do find any issues, please contact us through your email attached to your account, by sending an email to support@mthnetworks.com.
&gt; 
&gt; Thank you for your patience and cooperation throughout..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmo9x1qgc004onf9agiv33dsb</id>
  <published>2026-04-22T08:21:00.000+00:00</published>
  <updated>2026-04-23T15:37:55.144+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo9x1qgc004onf9agiv33dsb"/>
  <title>OFNL Incident: Wimbourne, BH21 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 7 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>15:37:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>08:21: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):

* Wimbourne, BH21

**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/cmo6wm2o40mt7j5jpjuehsrfj</id>
  <published>2026-04-20T07:40:00.000+00:00</published>
  <updated>2026-04-20T07:40:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo6wm2o40mt7j5jpjuehsrfj"/>
  <title>OFNL Incident: NN17, NN18</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 7 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>07:40: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):

* **Corby: NN17, NN18**

**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>Apr <var data-var='date'> 20</var>, <var data-var='time'>07:55:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good morning everyone,

We can confirm that this is a continuation of the incident that took place on 17/04/2026 in this area.

OFNL has confirmed the engineer has been in the area all weekend and is continuing to stay there to ensure this is resolved once and for all, as soon as possible.

MTH Networks would like to apologise for the continued inconvenience this issue has caused and for the frustration it has caused.

As soon as we have more updates, we will post here. 

Thank you for your cooperation and understanding. .</p>
<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>15:38: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/cmo5ws3jl125dpwcxyc3jbf5s</id>
  <published>2026-04-19T15:16:14.666+00:00</published>
  <updated>2026-04-19T15:16:14.666+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo5ws3jl125dpwcxyc3jbf5s"/>
  <title>OFNL Incident: NR10, NR6</title>

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

* Old Catton: NR10, NR6

**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>Apr <var data-var='date'> 19</var>, <var data-var='time'>17:29:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

&gt; **Update (19 Apr 2026 17:13hrs)**  
&gt; Work to restore service was completed at 17:00 on 19/04/26 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmo2w7kcl0gog13nt1yerkjfj</id>
  <published>2026-04-17T12:38:05.677+00:00</published>
  <updated>2026-04-17T12:38:05.677+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo2w7kcl0gog13nt1yerkjfj"/>
  <title>OFNL Incident Following Maintenance: CM0 Area</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 23 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>12:38:05</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good Afternoon all,

We hope that you are all well.

Unfortunately, following the completion of the OFNL maintenance in the CM0 area yesterday, around 2PM, we are seeing a small number of connections that are unable to get back online.

Given this, we are raising this post to keep track of the ongoing case and update it as necessary.

We are deeply sorry for the extended impact, and we are investigating this from top to bottom to resolve it as soon as possible.

Thank you for your understanding and patience regarding this matter.

Kind Regards,

Tommy.</p>
<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>11:07:50</var> GMT+0</small><br /><strong>Investigating</strong> -
  Hello All,

Firstly, our apologies for the lack of communication here. Our investigations have been ongoing, but we have yet to come across anything to report here.

However, we are also aware that connections that were online are not back offline, unfortunately. As a response, we do have teams in the area to review the situation and to gather more data.

Once we are able to relay more updates, we will be sure to do so here.

Thank you for your patience so far, everyone.

Kind Regards,

MTH Networks Team.</p>
<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>11:50:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  Good Afternoon all,

Thank you for your patience so far. We are just posting this update to let you know that our work and efforts will be continuing over the weekend to resolve this.

At this time, we do not have a time frame to share as we are still working towards gaining more information.

Your patience and understanding is most appreciated, and you have our deepest apologies regarding this downtime with the service, especially over the weekend.

Despite this, we all wish you a lovely weekend. We appreciate and are very thankful for your cooperation during this time.

Kind Regards,

Your MTH Networks Team.</p>
<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>11:50:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmo2mbizt00c7ysrgkbicimal</id>
  <published>2026-04-17T08:00:05.883+00:00</published>
  <updated>2026-04-17T08:00:05.883+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo2mbizt00c7ysrgkbicimal"/>
  <title>OFNL Incident: NN17, NN18</title>

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

* Corby: NN17, NN18

**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>Apr <var data-var='date'> 18</var>, <var data-var='time'>17:17:38</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the update below:

&gt; **Update (18 Apr 2026 17:32hrs)**  
&gt; The engineer is continuing to visit customers on site. Only a small number of customers remain affected, and we expect to have this issue resolved soon.  
&gt; We will provide a further update by 20:00..</p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>10:24:51</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please find the update here:

&gt; **Update (18 Apr 2026 19:45hrs)**  
&gt; Work to restore service was completed at 19:42 on 18/04/26\. 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>Apr <var data-var='date'> 19</var>, <var data-var='time'>10:25:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

&gt; **Update (18 Apr 2026 19:45hrs)**  
&gt; This incident was closed on Saturday, April 18th, 2026 at 19:45hrs..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>08:37:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see update below:

* **Update (17 Apr 2026 09:37hrs)**  
**We have identified the fault affecting the site. To resolve this issue, we need to remotely reboot a key piece of network equipment.**  
**To minimise disruption to other customers, this work will be carried out as emergency maintenance from midnight tonight.**  
    
**Fewer than 1% of customers on the site are currently impacted, and completing the reboot earlier would risk affecting additional customers who are not experiencing any issues.**  
    
**We apologise that we are unable to restore service for affected customers immediately and appreciate your patience while we complete this work as quickly and safely as possible.**.</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>11:38:07</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the update below:

**Update (18 Apr 2026 11:28hrs)**

  
Our engineer has identified a fibre issue affecting a small number of customers.  
We are currently awaiting the engineer to trace the fault and carry out the necessary repairs.  
We will provide a further update by 14:00\. An engineer is on route to the site and the ETA for this is 12:45pm.</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>12:33:11</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the update below:

&gt; Our engineer remains on site and is continuing work to resolve the fault. Due to the size and complexity of the site, resolution is taking longer than initially anticipated.  
&gt; We apologise for any inconvenience caused and will provide a further update at 16:00..</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>17:16:48</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the update below:

&gt; **Update (18 Apr 2026 14:25hrs)**  
&gt; Our on-site engineer will now be door-knocking affected customers to troubleshoot from the customer end and gather additional information.  
&gt; Further updates will follow at 16:00..</p>
<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>17:17:14</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the update below:

&gt; **Update (18 Apr 2026 16:03hrs)**  
&gt; The on-site engineer is rebooting network equipment, which has allowed us to restore service for customers who were previously offline.  
&gt; Where this does not resolve the issue, the engineer is replacing equipment within the property, which has been effective in restoring service.  
&gt; We are continuing to visit affected properties. If you are still offline, please try rebooting your equipment.  
&gt;  
&gt; We will update you again at 18:00..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmo1ojc47009alcec5ub61079</id>
  <published>2026-04-16T16:14:23.927+00:00</published>
  <updated>2026-04-16T16:14:23.927+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmo1ojc47009alcec5ub61079"/>
  <title>OFNL Incident: B1 Birmingham </title>

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

* B1 Birmingham

**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>Apr <var data-var='date'> 16</var>, <var data-var='time'>16:43:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; Work to restore service was completed at 17:43 on 16/04/26\. 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>Apr <var data-var='date'> 16</var>, <var data-var='time'>16:43: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/cmnzxili405d5yul2ulu3atgg</id>
  <published>2026-04-15T10:25:00.000+00:00</published>
  <updated>2026-04-15T10:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnzxili405d5yul2ulu3atgg"/>
  <title>OFNL Incident: Peterborough PE26 PE28</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>10:25: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):

Peterborough PE26 PE28

**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>Apr <var data-var='date'> 15</var>, <var data-var='time'>10:59:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest Update below:

**Update (15 Apr 2026 11:57hrs)**  
We have arranged for an engineering team to attend the site.  
  
Their current estimated time of arrival is 13:20.  
  
Once on site, the engineers will begin a thorough investigation to identify the issue and will work to resolve it as soon as the fault is confirmed.  
  
We will continue to provide updates as we receive important information from the on-site team.  
  
Thank you for your patience while we work to restore your services..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>12:09:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see latest update below:

**Update (15 Apr 2026 13:08hrs)**  
Our engineer has attended the site and confirmed that the fault is on a third-party fibre connection that provides backhaul to the site.  
  
As this is a third-party service, we have contacted the vendor and requested that they arrange for an engineer to attend the site &amp; fault location to resolve the issue.  
  
We will provide further updates as soon as we receive meaningful information..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>15:49:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see latest update below:

**Update (15 Apr 2026 17:44hrs)**  
The third-party engineering team has completed repair works to the affected fibre joint, and services were successfully restored at 16:49 on 15/04/2026..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see latest update below:

**Update (15 Apr 2026 16:30hrs)**  
A third-party engineering team has identified damage to a fibre joint on their network and is currently carrying out repair works.  
  
Further updates will be shared as soon as new information becomes available..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Update (15 Apr 2026 17:44hrs)**  
This incident was closed on Wednesday, April 15th, 2026 at 17:44hrs..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmnylqp7b01k0y4z32y4fqq49</id>
  <published>2026-04-14T12:07:00.000+00:00</published>
  <updated>2026-04-14T12:07:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnylqp7b01k0y4z32y4fqq49"/>
  <title>OFNL Incident: NG31 Belton Lane </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:07:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:07: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):

* **NG31 Belton Lane**

**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/cmnvys6ja0aldndq3vz0bddyl</id>
  <published>2026-04-12T12:37:00.000+00:00</published>
  <updated>2026-04-12T12:37:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnvys6ja0aldndq3vz0bddyl"/>
  <title>OFNL Incident: NR9</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 23 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>12:37: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; Easton, NR9

**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>Apr <var data-var='date'> 12</var>, <var data-var='time'>16:04:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; The OFNL engineering team is now on site and is actively investigating the fibre fault. We will share further updates as soon as more information becomes available..</p>
<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:30:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmnt1fnmk0c90onaqho285qil</id>
  <published>2026-04-10T15:05:29.122+00:00</published>
  <updated>2026-04-10T15:05:29.122+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnt1fnmk0c90onaqho285qil"/>
  <title>Freedom Fibre Incident: CW9</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days</p>
    <p><strong>Affected Components:</strong> Freedom Fibre</p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>15:05:29</var> GMT+0</small><br /><strong>Identified</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!**

Freedom Fibre have advised that the **next update is expected by 12:00 on 13/04/2026.**

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>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:05: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/cmnpyxva000rdn6w12cdyuc8e</id>
  <published>2026-04-08T10:54:00.000+00:00</published>
  <updated>2026-04-08T10:54:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnpyxva000rdn6w12cdyuc8e"/>
  <title>OFNL Incident Affecting Phone Services: Multiple Locations</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:54: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) affecting phone services specifically inbound calls:

Multiple Locations

**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>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:54: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/cmnohpq3d01odhibn8awlkq4p</id>
  <published>2026-04-07T10:23:00.000+00:00</published>
  <updated>2026-04-07T10:23:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmnohpq3d01odhibn8awlkq4p"/>
  <title>OFNL Incident: B1, B18</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>10: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; **_Birmingham , B1, B18_**

**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. They will look to provide an update by 14:00.

Thank you for your understanding..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:41:01</var> GMT+0</small><br /><strong>Investigating</strong> -
  An engineering team has been dispatched to investigate a fibre cable issue currently impacting services. They are en-route to site and will begin diagnostics upon arrival.  
  
We will provide further updates as soon as more information becomes available. Thank you for your patience while we work to resolve this as quickly as possible..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:56:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  **Update (07 Apr 2026 14:13hrs)**  
Work to restore service was completed at 13:56 on 07/04/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
  
Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
  
We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:21:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmng433tt00sca0vgq7l8t9la</id>
  <published>2026-04-01T13:03:00.000+00:00</published>
  <updated>2026-04-01T13:03:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmng433tt00sca0vgq7l8t9la"/>
  <title>OFNL Incident: Snettisham PE31</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 45 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>13:03: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; **Snettisham PE31**

**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>Apr <var data-var='date'> 1</var>, <var data-var='time'>14:48:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Update (01 Apr 2026 15:49hrs)**  
Work to restore service was completed. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable.  
  
Any issues being experienced after this time should be treated as individual cases and reported in the usual manner.  
  
We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p>

        ]]>
  </content>
</entry>

</feed>