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

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpqqgk8101ksqklnr963bxx2</id>
  <published>2026-06-21T23:00:00.000+00:00</published>
  <updated>2026-06-21T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpqqgk8101ksqklnr963bxx2"/>
  <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'> 21</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; Bolton

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpqqhld502j4qpmq6h4hyfnu</id>
  <published>2026-06-20T23:00:00.000+00:00</published>
  <updated>2026-06-20T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpqqhld502j4qpmq6h4hyfnu"/>
  <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'> 20</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; Bolton, Bath

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpqqegix04djqjcm5b4cfty4</id>
  <published>2026-06-18T22:00:00.000+00:00</published>
  <updated>2026-06-18T22:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpqqegix04djqjcm5b4cfty4"/>
  <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'> 18</var>, <var data-var='time'>22: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; Eastbourne

Customers will experience an outage between 18/06/2026 23:00:00 and 19/06/2026 06:00:00.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpmicxyh0cn6nrmmmeuz8xuh</id>
  <published>2026-06-16T19:00:00.000+00:00</published>
  <updated>2026-06-16T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpmicxyh0cn6nrmmmeuz8xuh"/>
  <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'> 16</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; Eastbourne

Customers will experience an outage between 16/06/2026 23:00:00 and 17/06/2026 06:00:00.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpduclwl01toqim7jzmk75z1</id>
  <published>2026-06-10T23:00:00.000+00:00</published>
  <updated>2026-06-10T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpduclwl01toqim7jzmk75z1"/>
  <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'> 10</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; Bracknell

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

        ]]>
  </content>
</entry>

<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/cmpdubeil01z9qimm96wi4woj</id>
  <published>2026-06-08T19:00:00.000+00:00</published>
  <updated>2026-06-08T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpdubeil01z9qimm96wi4woj"/>
  <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'> 8</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; Eastbourne

A brief 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/cmpmkqr2s00kypflt5qzdggdg</id>
  <published>2026-06-03T23:00:00.000+00:00</published>
  <updated>2026-06-03T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpmkqr2s00kypflt5qzdggdg"/>
  <title>OFNL Core Maintenance (id: 392150)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  OFNL are working to upgrade their Core Routers in one of their data centres on the night of 04/06/26 between the hours of 00:01 and 06:00\.   
  
During this period, some customers will experience a total loss of service during this period until OFNL has completed the planned works.  
  
Please do not reset your equipment during this period.  
  
We apologise for the inconvenience this may cause..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmpuxk25g06f0np2g9v1b4gh2</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxk25g06f0np2g9v1b4gh2"/>
  <title>OFNL Maintenance: Pontefract WF8</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Pontefract WF8

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/cmpuxjip9000nqqja94svpx2x</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxjip9000nqqja94svpx2x"/>
  <title>OFNL Maintenance: Cardiff CF71 Pontypool NP4 NP44 Blackwood NP12 Ebbw Vale NP2</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Cardiff CF71 Pontypool NP4 NP44 Blackwood NP12 Ebbw Vale NP2

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/cmpuxiy8l001fqqjzk5mnkd94</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxiy8l001fqqjzk5mnkd94"/>
  <title>OFNL Maintenance: Suffolk IP14 IP30</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Suffolk IP14 IP30

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/cmpuxigpf06emnp2gm0vto7k7</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxigpf06emnp2gm0vto7k7"/>
  <title>OFNL Maintenance: Alcester B49 Redditch B98</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Alcester B49 Redditch B98

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/cmpuxhvva06eenp2gs4qprezb</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxhvva06eenp2gs4qprezb"/>
  <title>OFNL Maintenance: Polegate BN24 BN23 BN26</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Polegate BN24 BN23 BN26

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/cmpuxhcre05yvnp29j97cstyb</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxhcre05yvnp29j97cstyb"/>
  <title>OFNL Maintenance: Harrogate HG4 HG3 HG1 HG5</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Harrogate HG4 HG3 HG1 HG5

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/cmpuxgscq03rynn9qoclpiokh</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxgscq03rynn9qoclpiokh"/>
  <title>OFNL Maintenance:  Hampshire PO15 SO15 SO30 SO31</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Hampshire PO15 SO15 SO30 SO31

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/cmpuxg7al000fqqjzboha8uji</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxg7al000fqqjzboha8uji"/>
  <title>OFNL Maintenance: Banbury OX15 OX16 Southam CV47 OX15 Middleton Cheney OX17</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; Banbury OX15 OX16 Southam CV47 OX15 Middleton Cheney OX17

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/cmpuxez4705ygnp29mfdxoxyr</id>
  <published>2026-06-01T23:00:00.000+00:00</published>
  <updated>2026-06-01T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmpuxez4705ygnp29mfdxoxyr"/>
  <title>OFNL Maintenance: AB51 AB32 AB31 AB15 AB22 AB23 AB13 AB21 NW10 B49 GU11 MK45 SP11 NG3 BN18 TN23 TN24 RM15 HP22 YO13.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>Jun <var data-var='date'> 1</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; AB51 AB32 AB31 AB15 AB22 AB23 AB13 AB21 
&gt; 
&gt; NW10 
&gt; 
&gt; B49 
&gt; 
&gt; GU11 
&gt; 
&gt; MK45 
&gt; 
&gt; SP11 
&gt; 
&gt; NG3 
&gt; 
&gt; BN18 
&gt; 
&gt; TN23 TN24 
&gt; 
&gt; RM15 
&gt; 
&gt; HP22 
&gt; 
&gt; YO13.

  
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:Incident/cmpqwk0ds03wjqpmqxf6zx5r5</id>
  <published>2026-05-29T12:32:48.774+00:00</published>
  <updated>2026-05-29T12:32:48.774+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpqwk0ds03wjqpmqxf6zx5r5"/>
  <title>OFNL Incident: NG11</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 days, 16 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>12:32:48</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; Rushcliffe 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>May <var data-var='date'> 29</var>, <var data-var='time'>18:54:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; We have received an update from our third-party vendor confirming that their on-site engineer is currently awaiting the arrival of a required part before they can proceed with resolving the fault.  
&gt;  
&gt; We will provide a further update as soon as we receive more information from the vendor.  
&gt;  
&gt; Thank you for your patience..</p>
<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>21:13:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Please find the latest update below:

&gt; We have received confirmation from our third-party vendor that the faulty equipment at the exchange has been successfully replaced, and service was restored at 21:30.  
&gt;  
&gt; We have also carried out further checks on our side and can confirm that all services are now operating as expected. At this time, we do not anticipate any further impact.  
&gt;  
&gt; Thank you for your patience while this issue was being resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Maintenance/cmppktmox07bap8m2u30z0ytc</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppktmox07bap8m2u30z0ytc"/>
  <title>OFNL Maintenance: EX39 Devon and Torbay</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'> 28</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; EX39 Devon and Torbay

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'> 28</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'> 29</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/cmppku9xd02pbqqmxg8i26xl6</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppku9xd02pbqqmxg8i26xl6"/>
  <title>OFNL Maintenance: LE17 Leicestershire</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'> 28</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; LE17 Leicestershire

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'> 28</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'> 29</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/cmppkus7v01qzqmm2gt3hre3e</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppkus7v01qzqmm2gt3hre3e"/>
  <title>OFNL Maintenance: RG7 Reading</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'> 28</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; RG7 Reading

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'> 28</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'> 29</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/cmppkvm9007f1p8moefq92uvb</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppkvm9007f1p8moefq92uvb"/>
  <title>OFNL Maintenance: S73 Barnsley</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'> 28</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; S73 Barnsley

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'> 28</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'> 29</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/cmppkw62a01jtqmmogulfhz43</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppkw62a01jtqmmogulfhz43"/>
  <title>OFNL Maintenance: WV11 West Midlands</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'> 28</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; WV11 West Midlands

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'> 28</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'> 29</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/cmppkwyb2079dp8m9ptafpuhd</id>
  <published>2026-05-28T23:00:00.000+00:00</published>
  <updated>2026-05-28T23:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/maintenance/cmppkwyb2079dp8m9ptafpuhd"/>
  <title>OFNL Maintenance: RH11 Crawley</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'> 28</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; RH11 Crawley

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'> 28</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'> 29</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/cmpo0jq7g01fkqnk3q5oa2xck</id>
  <published>2026-05-27T11:50:00.000+00:00</published>
  <updated>2026-05-27T11:50:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpo0jq7g01fkqnk3q5oa2xck"/>
  <title>OFNL Incident: Caldicot NP26, Magor NP26.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 40 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>11:50: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; Caldicot NP26, Magor NP26.

**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'> 27</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/cmpi6fqfa0er3qgni045ca0sy</id>
  <published>2026-05-23T09:59:32.137+00:00</published>
  <updated>2026-05-23T09:59:32.137+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpi6fqfa0er3qgni045ca0sy"/>
  <title>OFNL Incident: NN12</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>09:59:32</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; **NN12**

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

&gt; **Update (23 May 2026 10:34hrs)**  
&gt; Our engineer is on their way to site, once on site they will begin their investigation into the cause of the fault.  
&gt;  
&gt; We are now waiting for the engineer to arrive which should be around 11:00am.  
&gt;  
&gt; We will update you again by 14:00..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>14:41:37</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (23 May 2026 13:04hrs)**  
&gt; Our engineer is currently on site; however, we have encountered access issues to our equipment. We have engaged with the relevant third-party providers to resolve this and restore access as soon as possible, allowing us to proceed with troubleshooting and work towards resolving the outage.  
&gt; We will share further updates as soon as more information becomes available..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>18:08:21</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (23 May 2026 18:58hrs)**  
&gt; We have been unable to arrange access to the equipment as the third-party engineers are currently addressing other critical issues. We will continue to liaise with them and aim to secure access early tomorrow. We will keep you updated on the progress of this fault..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>11:04:19</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (24 May 2026 09:30hrs)**  
&gt; We are continuing to engage with the third party responsible for the current access issues to arrange a joint site visit and restore service.  
&gt; We will provide a further update by 12:00..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:27:15</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (24 May 2026 14:30hrs)**  
&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 by18:00..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:27:35</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (24 May 2026 18:07hrs)**  
&gt; The third-party provider has engaged their engineers to investigate the issue. They have identified the root cause and are currently working on a fix to restore the connection. Further updates will be shared as soon as they become available..</p>
<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>10:00: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/cmpgrv9oi03twp4naz2b3d4uv</id>
  <published>2026-05-22T10:00:00.000+00:00</published>
  <updated>2026-05-22T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpgrv9oi03twp4naz2b3d4uv"/>
  <title>OFNL Incident: Great Wakering SS3</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'> 22</var>, <var data-var='time'>10: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):

* Great Wakering SS3

**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'> 22</var>, <var data-var='time'>10:38:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please latest Update below:

**Update (22 May 2026 11:38hrs)**  
Work to restore service was completed at 11:30 am on 22/05/26\. 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'> 22</var>, <var data-var='time'>13:29:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmpgnyeph01j3pam5ymbyl0fz</id>
  <published>2026-05-21T18:30:00.000+00:00</published>
  <updated>2026-05-21T18:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpgnyeph01j3pam5ymbyl0fz"/>
  <title>OFNL Incident: Shefford SG17</title>

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

Shefford SG17

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

&gt; **Update (21 May 2026 21:57hrs)** 
&gt; **Engineers on site have identified an issue with the power supply. This has been reported to the local power provider, and we are currently awaiting their attendance. In the meantime, our equipment is being temporarily powered by an engineer’s vehicle. We apologise for any disruption this may cause and appreciate your patience while the issue is resolved. Our next update will be at midnight(00:00)**.</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>06:27:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see latest update below:

&gt; **Update (22 May 2026 07:27hrs)** 
&gt; **Work to restore service was completed at 07:10 on 22/05/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>May <var data-var='date'> 21</var>, <var data-var='time'>22:58:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (21 May 2026 23:58hrs)**  
&gt; Power company engineers have identified a fault with a power cable supplying our equipment. This will require specialist engineers to attend, which may not be until tomorrow morning. We will continue working to resolve the issue and will provide further updates as soon as new information becomes available, or by 09:00 at the latest..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>06:57: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/cmpfe49650044pd89t376owvc</id>
  <published>2026-05-21T10:53:00.000+00:00</published>
  <updated>2026-05-22T10:24:10.144+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpfe49650044pd89t376owvc"/>
  <title>OFNL Incident: Birmingham B31</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:24:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>10:53: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):

* Birmingham B31

**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'> 21</var>, <var data-var='time'>10:57:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest Update below:

&gt; **Update (21 May 2026 11:57hrs)**  
&gt; Following our initial remote checks, we have identified that this incident is currently affecting a small number of customers.  
&gt;  
&gt; We will continue to investigate the root cause and aim to resolve the issue remotely at this stage.  
&gt;  
&gt; We will provide a further update as soon as we have any significant information to share.  
&gt;  
&gt; Thank you for your patience and understanding..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>13:09:07</var> GMT+0</small><br /><strong>Identified</strong> -
  Please find the latest update below:

&gt; **Update (21 May 2026 13:32hrs)**  
&gt; We have completed our remote diagnostics and believe the issue has now been identified.  
&gt;  
&gt; To resolve this, an engineer will need to attend site to replace the affected equipment that is causing the fault.  
&gt;  
&gt; The engineer is currently scheduled to arrive at approximately 15:30..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmpcevjdv02vep9lvclkxeetv</id>
  <published>2026-05-19T08:55:00.000+00:00</published>
  <updated>2026-05-19T08:55:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpcevjdv02vep9lvclkxeetv"/>
  <title>OFNL Incident: B49 Stratford Upon Avon </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 3 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> OFNL</p>
    <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>08:55: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):

* B49 Stratford Upon Avon

**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'> 20</var>, <var data-var='time'>12:34:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest update below:

&gt; **Update (20 May 2026 13:33hrs)**  
&gt; Work to restore service was completed at 13:25 on 20/05/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>May <var data-var='date'> 20</var>, <var data-var='time'>12:34:01</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>09:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Please see the latest update below:

&gt; **Update (19 May 2026 10:42hrs)**  
&gt; Following extensive remote diagnostics, we have arranged for a field engineer to attend site to carry out further on-site checks and investigate the issue affecting your services.  
&gt;  
&gt; Once the root cause has been identified, we will work to implement a fix and restore services as quickly as possible.  
&gt;  
&gt; The engineer’s current estimated time of arrival is 13:45\. We will provide a further update by 14:00.  
&gt;  
&gt; Thank you for your patience and understanding..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>11:33:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (19 May 2026 12:33hrs)**  
&gt; Our engineer has now completed the on-site investigation and identified significant fire damage affecting the cabinet equipment, originating from a fault within the electrical components.  
&gt;  
&gt; Due to the severity of the damage, we are currently working with a third-party contractor to arrange the replacement of the affected equipment as quickly as possible. Given the extent of the repairs required, we anticipate that resolution may take some time.  
&gt;  
&gt; We will continue to provide updates as more information becomes available.  
&gt;  
&gt; Thank you for your patience and understanding while we work to restore service..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>14:28:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (19 May 2026 15:28hrs)**  
&gt; We are arranging for teams to work overnight to resolve this incident. We will provide a further update in the morning, at which point we expect to have a clearer understanding of the current status and any additional work required.  
&gt;  
&gt; Thank you for your patience while we work to resolve this issue..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>18:31:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (19 May 2026 19:31hrs)**  
&gt; Our engineers, along with a third-party contractor, are currently on site replacing the affected cables and equipment. We will provide further updates as more information becomes available..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>06:34:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Please see the latest update below:

&gt; **Update (20 May 2026 07:34hrs)**  
&gt; We are now seeing internet and phone services restore, however work is still ongoing and we expect further disruption throughout the day whilst repairs are completed. A further update will be provided by 12:00.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:mthn.instatus.com,2005:Incident/cmpb9dcjh0bdiqjk6o4ub6qfd</id>
  <published>2026-05-18T13:45:00.000+00:00</published>
  <updated>2026-05-18T13:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://mthn.instatus.com/incident/cmpb9dcjh0bdiqjk6o4ub6qfd"/>
  <title>OFNL Incident: Cambridge, CB25, CB5</title>

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

* **Cambridge, CB25, CB5**

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

&gt; **Update (18 May 2026 14:47hrs)** 
&gt; **An engineer is on route to the site and the ETA for this is 16:30.**.</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>15:56:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Please see the latest Update below:

&gt; **Update (18 May 2026 16:56hrs)**  
&gt; Engineer has identified the issue and a fix is now in place. Customer should now find services working as normal..</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>16:01:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Update (18 May 2026 17:01hrs)**  
This incident was closed on Monday, May 18th, 2026 at 17:01hrs..</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: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>Duration:</strong> 17 hours and 58 minutes</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>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Following maintenance completed by The OFNL Network, we observed that a number of connections struggled to reestablish internet connectivity. This is something that we have been investigating, both internally and with The OFNL Network, as a top priority. 

In the meantime, we have used methods to restore connectivity for those affected. 

As standard, your router will be configured under the PPPoE authentication method. Though this is the standard we have deployed across our connections for many years now, to resolve this matter as quickly as possible, we&#039;d suggest amending your router&#039;s settings to use the authentication type DHCP, often referred to as Dynamic IP. 

To do this, if you are using either an MTH HC220 or an MTH HX510 router, you can follow the steps below:

1. On your smartphone, connect to the MTH Networks Wi-Fi
2. Head to your app store (App Store for iPhone, Play Store for Android) and download the Aginet app
3. Once inside the Aginet app and on the Network tab, click into More down in the bottom right
4. Tap &quot;Internet Connection&quot;.
5. You will need to change the Internet Connection Type from PPPoE to Dynamic IP
6. Please save/apply this change

If you are using an older MTH Networks router, please reach out to our team at support@mthnetworks.com so we can provide the necessary steps.

And if you are using a router not supplied by MTH Networks, the required steps may differ. We would advise referring to your router&#039;s user manual. 

Our super helpful Customer Service team will be here and ready to help should you need any assistance completing the needed steps.

We thank you for your continued patience and 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>

</feed>