MTH Networks Status - Incident history https://mthn.instatus.com MTH Networks Tue, 5 May 2026 21:00:00 +0000 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre May 5, 21:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Milton Keynes, Bletchley A 4-hour Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Milton Keynes, Bletchley A 4-hour Service Outage will be expected during the maintenance window..</p> ]]> Tue, 5 May 2026 21:00:00 +0000 https://mthn.instatus.com/maintenance/cmnps3myc006rxipzbipynull https://mthn.instatus.com/maintenance/cmnps3myc006rxipzbipynull CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 27, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > York, Stratford-upon-Avon A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <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: > York, Stratford-upon-Avon A brief Service Outage will be expected during the maintenance window..</p> ]]> Mon, 27 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmxay7yd0038euyghu8acd6r https://mthn.instatus.com/maintenance/cmmxay7yd0038euyghu8acd6r CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 26, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Swindon A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 26</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: > Swindon A brief Service Outage will be expected during the maintenance window..</p> ]]> Sun, 26 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmxaz5h502ak790nid4zyje4 https://mthn.instatus.com/maintenance/cmmxaz5h502ak790nid4zyje4 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 25, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Stratford-upon-Avon, Solihull, Bentley Heath, Slough, Sheffield A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 25</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: > Stratford-upon-Avon, Solihull, Bentley Heath, Slough, Sheffield A brief Service Outage will be expected during the maintenance window..</p> ]]> Sat, 25 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmxauhb5045g1l80fdozjk42 https://mthn.instatus.com/maintenance/cmmxauhb5045g1l80fdozjk42 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 24, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Portsmouth, Potters Bar, Reading, Rotherham, Glasgow A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Portsmouth, Potters Bar, Reading, Rotherham, Glasgow A brief Service Outage will be expected during the maintenance window..</p> ]]> Fri, 24 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmxax71w003bwu6eta08rqg0 https://mthn.instatus.com/maintenance/cmmxax71w003bwu6eta08rqg0 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 23, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > North Tyneside, Peterborough, Plymouth A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > North Tyneside, Peterborough, Plymouth A brief Service Outage will be expected during the maintenance window..</p> ]]> Thu, 23 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmxaw6zk02f6uorj6oapbh1d https://mthn.instatus.com/maintenance/cmmxaw6zk02f6uorj6oapbh1d CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 22, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Maidenhead, Milton Keynes, Brixworth, Northampton A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 22</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: > Maidenhead, Milton Keynes, Brixworth, Northampton A brief Service Outage will be expected during the maintenance window..</p> ]]> Wed, 22 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmw140at07onx0oli0ruch88 https://mthn.instatus.com/maintenance/cmmw140at07onx0oli0ruch88 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 22, 01:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > St. Albans, Potters Bar A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > St. Albans, Potters Bar A brief Service Outage will be expected during the maintenance window..</p> ]]> Wed, 22 Apr 2026 01:00:00 +0000 https://mthn.instatus.com/maintenance/cmnfsafml00az9h7awfe51y5z https://mthn.instatus.com/maintenance/cmnfsafml00az9h7awfe51y5z CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 18, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Leeds, Leicester A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 18</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: > Leeds, Leicester A brief Service Outage will be expected during the maintenance window..</p> ]]> Sat, 18 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvwh3ce087rqlazjc3adhua https://mthn.instatus.com/maintenance/cmmvwh3ce087rqlazjc3adhua CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 17, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Hartlepool, Ipswich, Kettering, Rothwell, Lincoln A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Hartlepool, Ipswich, Kettering, Rothwell, Lincoln A brief Service Outage will be expected during the maintenance window..</p> ]]> Fri, 17 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvwg8x106oy9tjvu2jfkgh9 https://mthn.instatus.com/maintenance/cmmvwg8x106oy9tjvu2jfkgh9 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Apr 16, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Glasgow A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 16</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: > Glasgow A brief Service Outage will be expected during the maintenance window..</p> ]]> Thu, 16 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvwekup06sjx0olecrn58uc https://mthn.instatus.com/maintenance/cmmvwekup06sjx0olecrn58uc OFNL Incident: Peterborough PE26 PE28 Type: Incident Affected Components: OFNL Apr 15, 10:25:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): Peterborough PE26 PE28 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Apr 15, 10:59:15 GMT+0 - Investigating - Please see the latest Update below: **Update (15 Apr 2026 11:57hrs)** We have arranged for an engineering team to attend the site. Their current estimated time of arrival is 13:20. Once on site, the engineers will begin a thorough investigation to identify the issue and will work to resolve it as soon as the fault is confirmed. We will continue to provide updates as we receive important information from the on-site team. Thank you for your patience while we work to restore your services. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>10:25:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): Peterborough PE26 PE28 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>10:59:15</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest Update below: **Update (15 Apr 2026 11:57hrs)** We have arranged for an engineering team to attend the site. Their current estimated time of arrival is 13:20. Once on site, the engineers will begin a thorough investigation to identify the issue and will work to resolve it as soon as the fault is confirmed. We will continue to provide updates as we receive important information from the on-site team. Thank you for your patience while we work to restore your services..</p> ]]> Wed, 15 Apr 2026 10:25:00 +0000 https://mthn.instatus.com/incident/cmnzxili405d5yul2ulu3atgg https://mthn.instatus.com/incident/cmnzxili405d5yul2ulu3atgg MS3 Maintenance: HU9 Type: Maintenance Duration: 8 hours Affected Components: MS3 Apr 15, 09:00:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): * **Annandale Road** * **Bexhill Avenue** * **Milford Grove** * **Bradford Avenue** Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 15, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 15, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 8 hours

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): * **Annandale Road** * **Bexhill Avenue** * **Milford Grove** * **Bradford Avenue** Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 15 Apr 2026 09:00:00 +0000 https://mthn.instatus.com/maintenance/cmnzs99eb03nyp74ewqrvjc1l https://mthn.instatus.com/maintenance/cmnzs99eb03nyp74ewqrvjc1l OFNL Incident: NG31 Belton Lane Type: Incident Affected Components: OFNL Apr 14, 12:07:01 GMT+0 - Resolved - This incident has been resolved. Apr 14, 12:07:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): * **NG31 Belton Lane** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:07:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:07:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): * **NG31 Belton Lane** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> ]]> Tue, 14 Apr 2026 12:07:00 +0000 https://mthn.instatus.com/incident/cmnylqp7b01k0y4z32y4fqq49 https://mthn.instatus.com/incident/cmnylqp7b01k0y4z32y4fqq49 MS3 Maintenance: HU5 Type: Maintenance Duration: 6 hours Affected Components: MS3 Apr 13, 11:00:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): Avondale Crescent Shirley Avenue Perth Street West Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 13, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 13, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): Avondale Crescent Shirley Avenue Perth Street West Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 13 Apr 2026 11:00:00 +0000 https://mthn.instatus.com/maintenance/cmnx3pwz800koh1873yyixl71 https://mthn.instatus.com/maintenance/cmnx3pwz800koh1873yyixl71 MS3 Maintenance: DN34 Type: Maintenance Duration: 10 hours Affected Components: MS3 Apr 13, 07:00:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > CONINGSBY DRIVE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 13, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 13, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 10 hours

Affected Components:

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > CONINGSBY DRIVE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 13 Apr 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmnt0puz803r1109rztcjpsre https://mthn.instatus.com/maintenance/cmnt0puz803r1109rztcjpsre CityFibre Maintenance Type: Maintenance Duration: 6 hours Affected Components: CityFibre Apr 12, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 13, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 12, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Doncaster, Eastbourne, Edinburgh, Erdington A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 12</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: > Doncaster, Eastbourne, Edinburgh, Erdington A brief Service Outage will be expected during the maintenance window..</p> ]]> Sun, 12 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvwc4ym06oi9tjvak8b660g https://mthn.instatus.com/maintenance/cmmvwc4ym06oi9tjvak8b660g OFNL Incident: NR9 Type: Incident Duration: 1 day, 23 hours and 54 minutes Affected Components: OFNL Apr 12, 12:37:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Easton, NR9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Apr 12, 16:04:00 GMT+0 - Identified - Please find the latest update below: > The OFNL engineering team is now on site and is actively investigating the fibre fault. We will share further updates as soon as more information becomes available. Apr 14, 12:30:52 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 23 hours and 54 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>12:37:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Easton, NR9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>16:04:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > The OFNL engineering team is now on site and is actively investigating the fibre fault. We will share further updates as soon as more information becomes available..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:30:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 12 Apr 2026 12:37:00 +0000 https://mthn.instatus.com/incident/cmnvys6ja0aldndq3vz0bddyl https://mthn.instatus.com/incident/cmnvys6ja0aldndq3vz0bddyl CityFibre Maintenance Type: Maintenance Duration: 6 hours Affected Components: CityFibre Apr 11, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 12, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 11, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Crawley, Dundee, Derby, Dewsbury A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 11</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: > Crawley, Dundee, Derby, Dewsbury A brief Service Outage will be expected during the maintenance window..</p> ]]> Sat, 11 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvw95pg011eu1pms5x871qp https://mthn.instatus.com/maintenance/cmmvw95pg011eu1pms5x871qp MS3 Maintenance: HU5 Type: Maintenance Duration: 10 hours Affected Components: MS3 Apr 11, 07:00:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > MARNE STREET Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 11, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 11, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 10 hours

Affected Components:

<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > MARNE STREET Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 11 Apr 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmnt0djtv03wfwz9prctwl760 https://mthn.instatus.com/maintenance/cmnt0djtv03wfwz9prctwl760 CityFibre Maintenance Type: Maintenance Duration: 6 hours Affected Components: CityFibre Apr 10, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 11, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 10, 23:00:00 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Coventry A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <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: > Coventry A brief Service Outage will be expected during the maintenance window..</p> ]]> Fri, 10 Apr 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmmvw7sx7001hc1v8ywblhtkc https://mthn.instatus.com/maintenance/cmmvw7sx7001hc1v8ywblhtkc MS3 Maintenance: HU4 Type: Maintenance Duration: 3 hours Affected Components: MS3 Apr 10, 15:15:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > BETHUNE AVENUE > > LYNTON AVENUE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 15:15:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 18:15:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > BETHUNE AVENUE > > LYNTON AVENUE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>15:15:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 15:15:00 +0000 https://mthn.instatus.com/maintenance/cmnt0w37s00nr8cavopthtb18 https://mthn.instatus.com/maintenance/cmnt0w37s00nr8cavopthtb18 Freedom Fibre Incident: CW9 Type: Incident Duration: 3 days Affected Components: Freedom Fibre Apr 10, 15:05:29 GMT+0 - Identified - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > CW9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** Freedom Fibre have advised that the **next update is expected by 12:00 on 13/04/2026.** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Apr 13, 15:05:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 days

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>15:05:29</var> GMT+0</small><br><strong>Identified</strong> - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > CW9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** Freedom Fibre have advised that the **next update is expected by 12:00 on 13/04/2026.** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:05:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 10 Apr 2026 15:05:29 +0000 https://mthn.instatus.com/incident/cmnt1fnmk0c90onaqho285qil https://mthn.instatus.com/incident/cmnt1fnmk0c90onaqho285qil MS3 Maintenance: HU9 Type: Maintenance Duration: 3 days, 6 hours and 15 minutes Affected Components: MS3 Apr 10, 10:45:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 10:45:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > BRADFORD AVENUE > > ANNANDALE ROAD > > BEXHILL AVENUE > > TUXFORD GROVE > > MILFORD GROVE > > LINGDALE ROAD > > CASTLEFORD GROVE > > HOPEWELL ROAD > > WINGFIELD ROAD > > THE CHILTERNS > > TWYFORD CLOSE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 13, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 days, 6 hours and 15 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>10:45:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > BRADFORD AVENUE > > ANNANDALE ROAD > > BEXHILL AVENUE > > TUXFORD GROVE > > MILFORD GROVE > > LINGDALE ROAD > > CASTLEFORD GROVE > > HOPEWELL ROAD > > WINGFIELD ROAD > > THE CHILTERNS > > TWYFORD CLOSE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 10:45:00 +0000 https://mthn.instatus.com/maintenance/cmnt0osyf03zhwz9p4ltykznc https://mthn.instatus.com/maintenance/cmnt0osyf03zhwz9p4ltykznc MS3 Maintenance: HU9 Type: Maintenance Duration: 7 hours Affected Components: MS3 Apr 10, 10:30:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HEMSWELL AVENUE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 10:30:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 17:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 7 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HEMSWELL AVENUE Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>10:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 10:30:00 +0000 https://mthn.instatus.com/maintenance/cmnt0lmlq0c2bonaqsp47bgah https://mthn.instatus.com/maintenance/cmnt0lmlq0c2bonaqsp47bgah MS3 Maintenance: DN40 Type: Maintenance Duration: 8 hours Affected Components: MS3 Apr 10, 09:30:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HIGHLAND TARN Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 09:30:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 17:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 8 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>09:30:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HIGHLAND TARN Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>09:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 09:30:00 +0000 https://mthn.instatus.com/maintenance/cmnt0kj2m0brarzdf4o6k1aub https://mthn.instatus.com/maintenance/cmnt0kj2m0brarzdf4o6k1aub MS3 Maintenance: HU4 Type: Maintenance Duration: 9 hours Affected Components: MS3 Apr 10, 08:30:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 08:30:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > SULLIVAN ROAD Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 17:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 9 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > SULLIVAN ROAD Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 08:30:00 +0000 https://mthn.instatus.com/maintenance/cmnt0glnq0bzzonaqe4r493o9 https://mthn.instatus.com/maintenance/cmnt0glnq0bzzonaqe4r493o9 MS3 Maintenance: HU12 Type: Maintenance Duration: 9 hours Affected Components: MS3 Apr 10, 08:30:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HOLCROFT GARTH > > ALURED GARTH Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 08:30:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 17:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 9 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > HOLCROFT GARTH > > ALURED GARTH Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 08:30:00 +0000 https://mthn.instatus.com/maintenance/cmnt0hkha00g6swkfdu0huu5y https://mthn.instatus.com/maintenance/cmnt0hkha00g6swkfdu0huu5y MS3 Maintenance: HU9 Type: Maintenance Duration: 9 hours Affected Components: MS3 Apr 10, 08:10:00 GMT+0 - Identified - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > ABERDEEN STREET Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Apr 10, 08:10:01 GMT+0 - Identified - Maintenance is now in progress Apr 10, 17:10:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 9 hours

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:10:00</var> GMT+0</small><br><strong>Identified</strong> - The MS3 Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > ABERDEEN STREET Addresses located in this region may experience service interruptions. We and the MS3 Network will always endeavour to minimise the impact wherever possible. The MS3 Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:10:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Apr 2026 08:10:00 +0000 https://mthn.instatus.com/maintenance/cmnt0epxw00ekswkfzgrezr15 https://mthn.instatus.com/maintenance/cmnt0epxw00ekswkfzgrezr15 OFNL Incident Affecting Phone Services: Multiple Locations Type: Incident Affected Components: OFNL Apr 8, 10:54:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s) affecting phone services specifically inbound calls: Multiple Locations **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Apr 8, 10:54:01 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:54:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s) affecting phone services specifically inbound calls: Multiple Locations **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:54:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 8 Apr 2026 10:54:00 +0000 https://mthn.instatus.com/incident/cmnpyxva000rdn6w12cdyuc8e https://mthn.instatus.com/incident/cmnpyxva000rdn6w12cdyuc8e OFNL Incident: B1, B18 Type: Incident Duration: 23 hours and 58 minutes Affected Components: OFNL Apr 7, 10:23:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **_Birmingham , B1, B18_** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. They will look to provide an update by 14:00. Thank you for your understanding. Apr 7, 12:41:01 GMT+0 - Investigating - An engineering team has been dispatched to investigate a fibre cable issue currently impacting services. They are en-route to site and will begin diagnostics upon arrival. We will provide further updates as soon as more information becomes available. Thank you for your patience while we work to resolve this as quickly as possible. Apr 7, 12:56:00 GMT+0 - Monitoring - **Update (07 Apr 2026 14:13hrs)** Work to restore service was completed at 13:56 on 07/04/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue. Apr 8, 10:21:24 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 hours and 58 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>10:23:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **_Birmingham , B1, B18_** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. They will look to provide an update by 14:00. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:41:01</var> GMT+0</small><br><strong>Investigating</strong> - An engineering team has been dispatched to investigate a fibre cable issue currently impacting services. They are en-route to site and will begin diagnostics upon arrival. We will provide further updates as soon as more information becomes available. Thank you for your patience while we work to resolve this as quickly as possible..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:56:00</var> GMT+0</small><br><strong>Monitoring</strong> - **Update (07 Apr 2026 14:13hrs)** Work to restore service was completed at 13:56 on 07/04/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:21:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 7 Apr 2026 10:23:00 +0000 https://mthn.instatus.com/incident/cmnohpq3d01odhibn8awlkq4p https://mthn.instatus.com/incident/cmnohpq3d01odhibn8awlkq4p OFNL Incident: Snettisham PE31 Type: Incident Duration: 1 hour and 45 minutes Affected Components: OFNL Apr 1, 13:03:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **Snettisham PE31** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Apr 1, 14:48:00 GMT+0 - Resolved - **Update (01 Apr 2026 15:49hrs)** Work to restore service was completed. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue. Type: Incident

Duration: 1 hour and 45 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>13:03:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **Snettisham PE31** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>14:48:00</var> GMT+0</small><br><strong>Resolved</strong> - **Update (01 Apr 2026 15:49hrs)** Work to restore service was completed. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p> ]]> Wed, 1 Apr 2026 13:03:00 +0000 https://mthn.instatus.com/incident/cmng433tt00sca0vgq7l8t9la https://mthn.instatus.com/incident/cmng433tt00sca0vgq7l8t9la OFNL Incident: Continued Impact Following Maintenance in NP44 Type: Incident Affected Components: OFNL Mar 31, 07:00:00 GMT+0 - Investigating - Good morning, **This matter has been converted into an incident.** We have received several reports outlining a lack of service in the NP44 region, following yesterday's maintenance. You can find more about this maintenance here: <https://mthn.instatus.com/cmn8uoznd00syeqrc8jmd8h1q> Our Network Operations Team are currently investigating and working with The OFNL Network to identify the root cause and restore service as quickly as possible. We will continue to provide updates as more information becomes available. At this time, **please do not reset or reboot your network equipment** unless specifically instructed to do so by our support team, as this may delay service restoration or troubleshooting efforts. If you require further assistance, please contact our support team using our typical support channels. **Given the volume of outreach, response times may be slightly delayed.** We apologise for any inconvenience this may cause. Thank you for your patience and understanding as we work towards a resolution. Kind regards, Your MTH Networks Team. Apr 2, 11:49:29 GMT+0 - Investigating - Good Afternoon all, We would like to first apologise for the lack of updates regarding this case. Currently, we are reviewing all possible steps with The OFNL Network, as initial investigations into potential root causes have not yet yielded a clear resolution at this time. As a result, we have escalated this matter further with the relevant teams at OFNL to determine what additional steps can be taken to address this more effectively. We will aim to have a further update on this matter as a whole as soon as possible, and we will be sure to have it posted here accordingly. We sincerely apologise for the continued downtime, but we thank you all for being patient, despite the frustrating circumstances. We are aware of the impact that this is having, and we are doing all that we can to see this resolved soon. Kind Regards, Your MTH Networks Team Apr 3, 18:46:51 GMT+0 - Investigating - Good evening all, As always, thank you for your patience and understanding with us throughout this frustrating time. While there has not been a significant change in status since our last communication, we want to reassure you that work has been continuously ongoing behind the scenes since the incident was first raised. Our teams have remained committed to this investigation, conducting additional checks and system analyses to better understand the root cause. Through our continued investigations, we have further strengthened our confidence that the issue resides within the OFNL network and its supporting systems. We have shared all of our findings and conclusions with them and are currently awaiting their feedback and next steps. In the meantime, I must ask you to refrain from contacting The OFNL Network directly. We - MTH Networks - are your ISP, and so correspondence on the matter needs to come from and to us. Although we are confident that the fault lies in the hands of OFNL, we take full responsibility and ownership of the issue, and are working around the clock to resolve the much-anticipated remediation. We fully appreciate how frustrating and disruptive this prolonged downtime has been. Please be assured that we share your frustration and are actively pushing for answers and resolution from the responsible parties. While we are doing everything within our control to assist, the nature of this issue means the final resolution unfortunately lies outside our direct control; if we could have resolved this already, we absolutely would have done so. We would also like to sincerely apologise for the lack of frequent updates. We understand how important communication is during incidents like this. The truth of the matter is that as soon as we receive any meaningful developments or confirmed information, we make sure to immediately share these. At present, the challenge has been that there have been limited substantial updates to provide while investigations remain ongoing and conclusions are still being determined. Moving forward, we will ensure to be more forthcoming and transparent, providing more frequent communication, regardless of the information (or lack thereof) we can share at the time. We absolutely agree that the length of this investigation has been unacceptable, and is not the standard that we aim for here at MTH Networks. For this, we are truly sorry. Alongside our apologies, we will make sure you receive apologies from those responsible as well. Over the long bank holiday weekend, you can reach our Customer Service team via our usual channels between 11:00 and 20:00\. Our Technical Teams will continue their investigations beyond these hours, too. Thank you so much for your patience. Once again, we really are sorry for this. Kind Regards, Your MTH Networks Team. Apr 6, 15:51:05 GMT+0 - Investigating - Good Afternoon All, Considering the ongoing issue, we hope everyone is having a lovely Bank Holiday weekend. Despite our best efforts, the connection in the NP44 area is still down, for which we deeply apologise. We are aware of the impact this has had since the start, and over the Bank Holiday weekend, and with that in mind, we are still working to resolve this as soon as possible. We hope to provide better news soon, along with a time frame for when this can be resolved. Until then, you all have our thanks for your continued patience and understanding regarding this matter. From the entire MTH Networks Team, thank you. Apr 1, 09:28:35 GMT+0 - Investigating - Good Morning all, Firstly, we would like to apologise for the ongoing case here and for any inconvenience caused due to the lack of a connection. We are still working closely with the OFNL Network and their relevant teams to identify the possible causes. As we are comparing information for their side and ours, this will naturally take some time to complete. We appreciate that this is highly frustrating, but please note that our teams are working as fast as possible to have this resolved accordingly. Thank you for your understanding and patience. Apr 4, 18:55:48 GMT+0 - Investigating - Good evening everyone, Earlier today, we requested that all affected customers perform a full shutdown of their routers and OFNL modems (ONT), leaving them powered off for at least two hours. Several of our customers have acted as requested. But, unfortunately, this has not restored connections. Whilst this is certainly disappointing, given that we would have loved for this to have resolved the matter, it has not been a wasted effort; this is still an excellent step in our investigation, and has enabled us to rule out additional factors. These conclusions are being communicated as part of our cooperative investigation with The OFNL Network. Once again, thank you so much for your patience, understanding and cooperation with us. We are very sorry for how long this incident has been ongoing. We can assure you that we are closer than ever to a resolution. Kind regards, Your MTH Networks Team. Apr 7, 10:38:42 GMT+0 - Investigating - Good Morning All, We just would like to put out a notice that we are still pressing for a resolution since this matter started, and over the Bank Holiday weekend, too. We still have specialist teams meticulously reviewing the entire connection process to locate the root cause, but at this time, we do not have anything to share, unfortunately. Once we have more information, we will be aiming to notify you as soon as possible. Again, you all have our deepest thanks for the patience demonstrated so far. We understand that this is a rather tedious and frustrating matter, and we are doing all that we can to see this completed soon. Kind Regards, Your MTH Networks Team Apr 9, 15:27:32 GMT+0 - Investigating - Good Afternoon all, We hope that you are doing well, despite the ongoing case in the NP44 area. Firstly, we would like to apologise for the lack of constant updates for this. Rest assured, our efforts have not paused, and all teams responsible and related are still actively pursuing a resolution. There is nothing we would want more than to see this case resolved so that the service is restored to those affected, but at this time, the case continues to be worked on behind the scenes. Our aim is to deliver some form of substantial news soon, but we are unable to provide a time frame as to when this will be resolved due to the information that we have so far. Again, you have our deepest apologies for this. We hope to come back with further news and details about this soon. Kind Regards, The MTH Networks Team Apr 10, 12:57:55 GMT+0 - Investigating - Good afternoon all, Firstly, thank you for your patience and understanding. We know this hasn't been easy, and so we are really thankful. At MTH Networks, we want to be as transparent and forthcoming as possible. This is why we want to let you know that, despite our continuous and meticulous investigation, we haven't quite yet reached a conclusion as to why we have witnessed a high volume of impact, restricted to OFNL connections, specifically in the NP44 region, since the maintenance was completed in the NP44 region last week. I am sure that this is as frustrating to you as it is to us, and so we really are sorry. However, we have made progress and are able to bring some good news. During our tests, we have observed the restoration of service following a change in service type. Whilst this is not a "fix", given that this does not directly address or resolve the core issue that is evidently at play, we want to get services back up and running as soon as possible, and so are now working to complete this amendment across the board as quickly as possible. Given that this amendment relies on The OFNL Network's system, I cannot confidently provide an ETA for when it will take effect. However, we, alongside The OFNL Network, are doing all that we can to make this happen today, ahead of the weekend. As soon as we have more information, we will let you know. **For those services that have been scheduled for termination, we will be unable to proceed with this fix. This is simply because, when a termination has been scheduled, it is not possible to make further service adjustments. If you would like to revert your cancellation request, please let us know as soon as possible so that we can work towards this. It may, however, be too late for those who requested immediate termination.** Once more, thank you so much for your continued patience and understanding; we really do greatly appreciate this. Kind regards, Your MTH Networks Team. Type: Incident

Affected Components:

<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Good morning, **This matter has been converted into an incident.** We have received several reports outlining a lack of service in the NP44 region, following yesterday's maintenance. You can find more about this maintenance here: <https://mthn.instatus.com/cmn8uoznd00syeqrc8jmd8h1q> Our Network Operations Team are currently investigating and working with The OFNL Network to identify the root cause and restore service as quickly as possible. We will continue to provide updates as more information becomes available. At this time, **please do not reset or reboot your network equipment** unless specifically instructed to do so by our support team, as this may delay service restoration or troubleshooting efforts. If you require further assistance, please contact our support team using our typical support channels. **Given the volume of outreach, response times may be slightly delayed.** We apologise for any inconvenience this may cause. Thank you for your patience and understanding as we work towards a resolution. Kind regards, Your MTH Networks Team..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>11:49:29</var> GMT+0</small><br><strong>Investigating</strong> - Good Afternoon all, We would like to first apologise for the lack of updates regarding this case. Currently, we are reviewing all possible steps with The OFNL Network, as initial investigations into potential root causes have not yet yielded a clear resolution at this time. As a result, we have escalated this matter further with the relevant teams at OFNL to determine what additional steps can be taken to address this more effectively. We will aim to have a further update on this matter as a whole as soon as possible, and we will be sure to have it posted here accordingly. We sincerely apologise for the continued downtime, but we thank you all for being patient, despite the frustrating circumstances. We are aware of the impact that this is having, and we are doing all that we can to see this resolved soon. Kind Regards, Your MTH Networks Team.</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>18:46:51</var> GMT+0</small><br><strong>Investigating</strong> - Good evening all, As always, thank you for your patience and understanding with us throughout this frustrating time. While there has not been a significant change in status since our last communication, we want to reassure you that work has been continuously ongoing behind the scenes since the incident was first raised. Our teams have remained committed to this investigation, conducting additional checks and system analyses to better understand the root cause. Through our continued investigations, we have further strengthened our confidence that the issue resides within the OFNL network and its supporting systems. We have shared all of our findings and conclusions with them and are currently awaiting their feedback and next steps. In the meantime, I must ask you to refrain from contacting The OFNL Network directly. We - MTH Networks - are your ISP, and so correspondence on the matter needs to come from and to us. Although we are confident that the fault lies in the hands of OFNL, we take full responsibility and ownership of the issue, and are working around the clock to resolve the much-anticipated remediation. We fully appreciate how frustrating and disruptive this prolonged downtime has been. Please be assured that we share your frustration and are actively pushing for answers and resolution from the responsible parties. While we are doing everything within our control to assist, the nature of this issue means the final resolution unfortunately lies outside our direct control; if we could have resolved this already, we absolutely would have done so. We would also like to sincerely apologise for the lack of frequent updates. We understand how important communication is during incidents like this. The truth of the matter is that as soon as we receive any meaningful developments or confirmed information, we make sure to immediately share these. At present, the challenge has been that there have been limited substantial updates to provide while investigations remain ongoing and conclusions are still being determined. Moving forward, we will ensure to be more forthcoming and transparent, providing more frequent communication, regardless of the information (or lack thereof) we can share at the time. We absolutely agree that the length of this investigation has been unacceptable, and is not the standard that we aim for here at MTH Networks. For this, we are truly sorry. Alongside our apologies, we will make sure you receive apologies from those responsible as well. Over the long bank holiday weekend, you can reach our Customer Service team via our usual channels between 11:00 and 20:00\. Our Technical Teams will continue their investigations beyond these hours, too. Thank you so much for your patience. Once again, we really are sorry for this. Kind Regards, Your MTH Networks Team..</p> <p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>15:51:05</var> GMT+0</small><br><strong>Investigating</strong> - Good Afternoon All, Considering the ongoing issue, we hope everyone is having a lovely Bank Holiday weekend. Despite our best efforts, the connection in the NP44 area is still down, for which we deeply apologise. We are aware of the impact this has had since the start, and over the Bank Holiday weekend, and with that in mind, we are still working to resolve this as soon as possible. We hope to provide better news soon, along with a time frame for when this can be resolved. Until then, you all have our thanks for your continued patience and understanding regarding this matter. From the entire MTH Networks Team, thank you..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>09:28:35</var> GMT+0</small><br><strong>Investigating</strong> - Good Morning all, Firstly, we would like to apologise for the ongoing case here and for any inconvenience caused due to the lack of a connection. We are still working closely with the OFNL Network and their relevant teams to identify the possible causes. As we are comparing information for their side and ours, this will naturally take some time to complete. We appreciate that this is highly frustrating, but please note that our teams are working as fast as possible to have this resolved accordingly. Thank you for your understanding and patience..</p> <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>18:55:48</var> GMT+0</small><br><strong>Investigating</strong> - Good evening everyone, Earlier today, we requested that all affected customers perform a full shutdown of their routers and OFNL modems (ONT), leaving them powered off for at least two hours. Several of our customers have acted as requested. But, unfortunately, this has not restored connections. Whilst this is certainly disappointing, given that we would have loved for this to have resolved the matter, it has not been a wasted effort; this is still an excellent step in our investigation, and has enabled us to rule out additional factors. These conclusions are being communicated as part of our cooperative investigation with The OFNL Network. Once again, thank you so much for your patience, understanding and cooperation with us. We are very sorry for how long this incident has been ongoing. We can assure you that we are closer than ever to a resolution. Kind regards, Your MTH Networks Team. .</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>10:38:42</var> GMT+0</small><br><strong>Investigating</strong> - Good Morning All, We just would like to put out a notice that we are still pressing for a resolution since this matter started, and over the Bank Holiday weekend, too. We still have specialist teams meticulously reviewing the entire connection process to locate the root cause, but at this time, we do not have anything to share, unfortunately. Once we have more information, we will be aiming to notify you as soon as possible. Again, you all have our deepest thanks for the patience demonstrated so far. We understand that this is a rather tedious and frustrating matter, and we are doing all that we can to see this completed soon. Kind Regards, Your MTH Networks Team.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>15:27:32</var> GMT+0</small><br><strong>Investigating</strong> - Good Afternoon all, We hope that you are doing well, despite the ongoing case in the NP44 area. Firstly, we would like to apologise for the lack of constant updates for this. Rest assured, our efforts have not paused, and all teams responsible and related are still actively pursuing a resolution. There is nothing we would want more than to see this case resolved so that the service is restored to those affected, but at this time, the case continues to be worked on behind the scenes. Our aim is to deliver some form of substantial news soon, but we are unable to provide a time frame as to when this will be resolved due to the information that we have so far. Again, you have our deepest apologies for this. We hope to come back with further news and details about this soon. Kind Regards, The MTH Networks Team.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>12:57:55</var> GMT+0</small><br><strong>Investigating</strong> - Good afternoon all, Firstly, thank you for your patience and understanding. We know this hasn't been easy, and so we are really thankful. At MTH Networks, we want to be as transparent and forthcoming as possible. This is why we want to let you know that, despite our continuous and meticulous investigation, we haven't quite yet reached a conclusion as to why we have witnessed a high volume of impact, restricted to OFNL connections, specifically in the NP44 region, since the maintenance was completed in the NP44 region last week. I am sure that this is as frustrating to you as it is to us, and so we really are sorry. However, we have made progress and are able to bring some good news. During our tests, we have observed the restoration of service following a change in service type. Whilst this is not a "fix", given that this does not directly address or resolve the core issue that is evidently at play, we want to get services back up and running as soon as possible, and so are now working to complete this amendment across the board as quickly as possible. Given that this amendment relies on The OFNL Network's system, I cannot confidently provide an ETA for when it will take effect. However, we, alongside The OFNL Network, are doing all that we can to make this happen today, ahead of the weekend. As soon as we have more information, we will let you know. **For those services that have been scheduled for termination, we will be unable to proceed with this fix. This is simply because, when a termination has been scheduled, it is not possible to make further service adjustments. If you would like to revert your cancellation request, please let us know as soon as possible so that we can work towards this. It may, however, be too late for those who requested immediate termination.** Once more, thank you so much for your continued patience and understanding; we really do greatly appreciate this. Kind regards, Your MTH Networks Team. .</p> ]]> Tue, 31 Mar 2026 07:00:00 +0000 https://mthn.instatus.com/incident/cmnee3s8x0covqldd7x85fort https://mthn.instatus.com/incident/cmnee3s8x0covqldd7x85fort OFNL Incident: SN6 Type: Incident Duration: 20 hours and 24 minutes Affected Components: OFNL Mar 30, 13:49:39 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Shrivenham, SN6 **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. Mar 30, 14:04:00 GMT+0 - Investigating - Please see the latest update below: > **Update (30 Mar 2026 15:05hrs)** > **Our field engineers have been dispatched and are currently on the way to the affected site.** > > **In the meantime, we are continuing our investigations remotely while we await their arrival to begin on-site diagnostics and physical troubleshooting.** > > **We will provide the next update by 19:00.** Mar 30, 18:15:00 GMT+0 - Investigating - **Update (30 Mar 2026 19:15hrs)** Our field engineers have attended site and confirmed our equipment is operating correctly. Our third-party provider who provides fibre connectivity to this area, has advised that they have a network issue that they are working on resolving. We will provide an update as soon as further information is available or by 21:00. Mar 30, 20:01:00 GMT+0 - Identified - > **Update (30 Mar 2026 21:01hrs)** > **Our third-party provider has advised that they have a suspect fibre fault and are arranging engineers to investigate.** > > **We will provide an update as soon as further information is available or by 23:00.** Mar 30, 20:40:00 GMT+0 - Identified - **Update (30 Mar 2026 23:44hrs)** Our third-party provider is continuing to investigate the fibre fault. Unless their is significant progress or updates available overnight, we will provide the next update at 07:00 tomorrow. Mar 31, 06:05:00 GMT+0 - Monitoring - **Update (31 Mar 2026 07:06hrs)** Work to restore service was completed by our third-party supplier at 04:00 on 31/03/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. Mar 31, 10:13:49 GMT+0 - Resolved - **Update (31 Mar 2026 07:06hrs)** This incident was closed on Tuesday, March 31st, 2026 at 07:06hrs. Type: Incident

Duration: 20 hours and 24 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>13:49:39</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Shrivenham, SN6 **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>Mar <var data-var='date'> 30</var>, <var data-var='time'>14:04:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest update below: > **Update (30 Mar 2026 15:05hrs)** > **Our field engineers have been dispatched and are currently on the way to the affected site.** > > **In the meantime, we are continuing our investigations remotely while we await their arrival to begin on-site diagnostics and physical troubleshooting.** > > **We will provide the next update by 19:00.**.</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br><strong>Investigating</strong> - **Update (30 Mar 2026 19:15hrs)** Our field engineers have attended site and confirmed our equipment is operating correctly. Our third-party provider who provides fibre connectivity to this area, has advised that they have a network issue that they are working on resolving. We will provide an update as soon as further information is available or by 21:00..</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>20:01:00</var> GMT+0</small><br><strong>Identified</strong> - > **Update (30 Mar 2026 21:01hrs)** > **Our third-party provider has advised that they have a suspect fibre fault and are arranging engineers to investigate.** > > **We will provide an update as soon as further information is available or by 23:00.**.</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>20:40:00</var> GMT+0</small><br><strong>Identified</strong> - **Update (30 Mar 2026 23:44hrs)** Our third-party provider is continuing to investigate the fibre fault. Unless their is significant progress or updates available overnight, we will provide the next update at 07:00 tomorrow..</p> <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>06:05:00</var> GMT+0</small><br><strong>Monitoring</strong> - **Update (31 Mar 2026 07:06hrs)** Work to restore service was completed by our third-party supplier at 04:00 on 31/03/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>Mar <var data-var='date'> 31</var>, <var data-var='time'>10:13:49</var> GMT+0</small><br><strong>Resolved</strong> - **Update (31 Mar 2026 07:06hrs)** This incident was closed on Tuesday, March 31st, 2026 at 07:06hrs..</p> ]]> Mon, 30 Mar 2026 13:49:39 +0000 https://mthn.instatus.com/incident/cmnd8vqg104sczmjxs4j7hrmh https://mthn.instatus.com/incident/cmnd8vqg104sczmjxs4j7hrmh OFNL Incident: Ely, CB6 Type: Incident Duration: 4 hours and 26 minutes Affected Components: OFNL Mar 24, 12:20:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): Ely, CB6 **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. Mar 24, 13:41:00 GMT+0 - Identified - Please see latest update below: > **Update (24 Mar 2026 13:41hrs)** > **We have identified the issue and are directing an engineer to site to fix this issue, we will provide an update with an estimated time of arrival in due course.** Mar 24, 14:41:00 GMT+0 - Identified - Please see the latest update below: > **Update (24 Mar 2026 14:13hrs)** > **We have a confirmed ETA of 16:30pm for the engineer to arrive onsite. We will provide a further update once repairs are underway.** Mar 24, 16:41:00 GMT+0 - Monitoring - Please see the latest update below: > **Update (24 Mar 2026 16:45hrs)** > **Our engineer was able to resolve the issue and customers should see their services coming back. We will close this incident. Thank you for your patience.** Mar 24, 16:46:00 GMT+0 - Resolved - Please see latest update below: > **Update (24 Mar 2026 16:46hrs)** > **This incident was closed on Tuesday, March 24th, 2026 at 16:46hrs.** Type: Incident

Duration: 4 hours and 26 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>12:20: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): Ely, CB6 **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>Mar <var data-var='date'> 24</var>, <var data-var='time'>13:41:00</var> GMT+0</small><br><strong>Identified</strong> - Please see latest update below: > **Update (24 Mar 2026 13:41hrs)** > **We have identified the issue and are directing an engineer to site to fix this issue, we will provide an update with an estimated time of arrival in due course.**.</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>14:41:00</var> GMT+0</small><br><strong>Identified</strong> - Please see the latest update below: > **Update (24 Mar 2026 14:13hrs)** > **We have a confirmed ETA of 16:30pm for the engineer to arrive onsite. We will provide a further update once repairs are underway.**.</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>16:41:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update below: > **Update (24 Mar 2026 16:45hrs)** > **Our engineer was able to resolve the issue and customers should see their services coming back. We will close this incident. Thank you for your patience.**.</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>16:46:00</var> GMT+0</small><br><strong>Resolved</strong> - Please see latest update below: > **Update (24 Mar 2026 16:46hrs)** > **This incident was closed on Tuesday, March 24th, 2026 at 16:46hrs.**.</p> ]]> Tue, 24 Mar 2026 12:20:00 +0000 https://mthn.instatus.com/incident/cmn4lifd501zt9nyzzm92vxyl https://mthn.instatus.com/incident/cmn4lifd501zt9nyzzm92vxyl Major Freedom Fibre Incident Type: Incident Duration: 5 hours and 53 minutes Affected Components: Freedom Fibre Mar 24, 02:28:00 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing major incident, experienced across all connections and ISPs. **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. Mar 24, 08:21:15 GMT+0 - Resolved - Good morning, In the early hours of this morning, a mass drop in Freedom Fibre connections was detected. This was swiftly picked up by Freedom Fibre's investigative teams, who identified that a 3rd party was conducting maintenance that resulted in an unexpected knock-on effect. As above, it was not planned for this 3rd-party maintenance to have any negative impact on connections, which is why we were not notified in advance. We will continue to raise our joint frustrations with Freedom Fibre and said 3rd party, ensuring that this does not happen again. We are glad to report that this incident has been confirmed resolved, where we have seen the mass restoration of services since \~05:00am this morning. If your connection hasn't yet been restored, please perform a reboot of your network equipment and reach out to our super-helpful team if that proves unfruitful. Please find the various avenues for attaining our support below: * Phone: 01536 661050 * Email: support@mthnetworks.com * LiveChat: Accessible via our website As always, thank you for your patience, understanding, and for being an MTH Networks customer. Kind regards, Your MTH Networks Team. Type: Incident

Duration: 5 hours and 53 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>02:28:00</var> GMT+0</small><br><strong>Investigating</strong> - The Freedom Fibre Network has made us aware of an ongoing major incident, experienced across all connections and ISPs. **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>Mar <var data-var='date'> 24</var>, <var data-var='time'>08:21:15</var> GMT+0</small><br><strong>Resolved</strong> - Good morning, In the early hours of this morning, a mass drop in Freedom Fibre connections was detected. This was swiftly picked up by Freedom Fibre's investigative teams, who identified that a 3rd party was conducting maintenance that resulted in an unexpected knock-on effect. As above, it was not planned for this 3rd-party maintenance to have any negative impact on connections, which is why we were not notified in advance. We will continue to raise our joint frustrations with Freedom Fibre and said 3rd party, ensuring that this does not happen again. We are glad to report that this incident has been confirmed resolved, where we have seen the mass restoration of services since \~05:00am this morning. If your connection hasn't yet been restored, please perform a reboot of your network equipment and reach out to our super-helpful team if that proves unfruitful. Please find the various avenues for attaining our support below: * Phone: 01536 661050 * Email: support@mthnetworks.com * LiveChat: Accessible via our website As always, thank you for your patience, understanding, and for being an MTH Networks customer. Kind regards, Your MTH Networks Team. .</p> ]]> Tue, 24 Mar 2026 02:28:00 +0000 https://mthn.instatus.com/incident/cmn4c62n907hkbuemxzopckdi https://mthn.instatus.com/incident/cmn4c62n907hkbuemxzopckdi OFNL Incident: All locations Type: Incident Duration: 23 hours and 41 minutes Affected Components: OFNL Mar 21, 09:00:00 GMT+0 - Resolved - This incident has been resolved. Mar 20, 09:19:00 GMT+0 - Investigating - The OFNL Network have made us aware of an incident on the network, affecting incoming and outgoing calls. This is impacting all locations on the OFNL Network. We do apologise for any inconvenience caused here. Mar 20, 12:25:00 GMT+0 - Identified - Please see the latest update below: > **Update (20 Mar 2026 12:25hrs)** > Good afternoon, > A temporary workaround has been applied to restore the ability to make and receive calls following the issues experienced this morning. We are continuing to work closely with our third-party vendor to implement a permanent fix and minimise any future disruption. > If you encounter any phone issues that you believe are unrelated, please continue to report them through the usual channels. Type: Incident

Duration: 23 hours and 41 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>09:19:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network have made us aware of an incident on the network, affecting incoming and outgoing calls. This is impacting all locations on the OFNL Network. We do apologise for any inconvenience caused here. .</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>12:25:00</var> GMT+0</small><br><strong>Identified</strong> - Please see the latest update below: > **Update (20 Mar 2026 12:25hrs)** > Good afternoon, > A temporary workaround has been applied to restore the ability to make and receive calls following the issues experienced this morning. We are continuing to work closely with our third-party vendor to implement a permanent fix and minimise any future disruption. > If you encounter any phone issues that you believe are unrelated, please continue to report them through the usual channels..</p> ]]> Fri, 20 Mar 2026 09:19:00 +0000 https://mthn.instatus.com/incident/cmmywi9nk007rsxckmfcmciif https://mthn.instatus.com/incident/cmmywi9nk007rsxckmfcmciif OFNL Incident: CM3 Type: Incident Duration: 5 days and 1 hour Affected Components: OFNL Mar 18, 20:06:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > CM3 **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. Mar 18, 22:07:00 GMT+0 - Resolved - Please find the latest update below: > Work to restore service was completed at 21:43:33 on 18/03/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. Type: Incident

Duration: 5 days and 1 hour

Affected Components:

<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>20:06:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > CM3 **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>Mar <var data-var='date'> 18</var>, <var data-var='time'>22:07:00</var> GMT+0</small><br><strong>Resolved</strong> - Please find the latest update below: > Work to restore service was completed at 21:43:33 on 18/03/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> ]]> Wed, 18 Mar 2026 20:06:00 +0000 https://mthn.instatus.com/incident/cmmx5q6qx00yioy35flvd66ug https://mthn.instatus.com/incident/cmmx5q6qx00yioy35flvd66ug MTH Networks - National Network Incident Type: Incident Duration: 2 hours and 20 minutes Affected Components: CityFibre, Freedom Fibre, MS3, OFNL Mar 14, 11:40:58 GMT+0 - Investigating - Good Morning all, I hope you are all well this weekend. Unfortunately, we are receiving a large volume of reports that connections started to drop around 9PM to 11PM on 13/03/2026. We are currently investigating this, so once we have more information, we will be sure to let you all know accordingly. We do apologise for this, as it is the weekend, but we appreciate your patience as we look to investigate and work the issue on our side. Thank you! Mar 14, 13:23:51 GMT+0 - Monitoring - Good Afternoon All, Thank you for your patience. We have been able to investigate this and we are seeing connections be restored across the board. At this time, we are still reviewing the cause of the case in the first place, but for now, we are expecting all services to be restored over the next hour or so. We will keep this open for a while longer as we monitor this and ensure stability. Thank you for your patience so far. It is most appreciated. Mar 14, 14:01:02 GMT+0 - Resolved - Hello All, We will now close down this incident post, as we believe the overall case to be resolved. Should you have any further issues with your service, feel free to contact us. Thank you for your patience and understanding throughout this case. Type: Incident

Duration: 2 hours and 20 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>11:40:58</var> GMT+0</small><br><strong>Investigating</strong> - Good Morning all, I hope you are all well this weekend. Unfortunately, we are receiving a large volume of reports that connections started to drop around 9PM to 11PM on 13/03/2026. We are currently investigating this, so once we have more information, we will be sure to let you all know accordingly. We do apologise for this, as it is the weekend, but we appreciate your patience as we look to investigate and work the issue on our side. Thank you!.</p> <p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>13:23:51</var> GMT+0</small><br><strong>Monitoring</strong> - Good Afternoon All, Thank you for your patience. We have been able to investigate this and we are seeing connections be restored across the board. At this time, we are still reviewing the cause of the case in the first place, but for now, we are expecting all services to be restored over the next hour or so. We will keep this open for a while longer as we monitor this and ensure stability. Thank you for your patience so far. It is most appreciated..</p> <p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>14:01:02</var> GMT+0</small><br><strong>Resolved</strong> - Hello All, We will now close down this incident post, as we believe the overall case to be resolved. Should you have any further issues with your service, feel free to contact us. Thank you for your patience and understanding throughout this case..</p> ]]> Sat, 14 Mar 2026 11:40:58 +0000 https://mthn.instatus.com/incident/cmmq97wyy03s8rbtul4y75pt1 https://mthn.instatus.com/incident/cmmq97wyy03s8rbtul4y75pt1 Freedom Fibre Incident: M44 Type: Incident Duration: 1 hour and 26 minutes Affected Components: Freedom Fibre Mar 11, 14:56:00 GMT+0 - Resolved - This incident has been resolved. The teams were able to resolve this after completing works. Mar 11, 13:30:00 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > **M44 - Irlam** **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. Type: Incident

Duration: 1 hour and 26 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>14:56:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. The teams were able to resolve this after completing works..</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Investigating</strong> - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > **M44 - Irlam** **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> ]]> Wed, 11 Mar 2026 13:30:00 +0000 https://mthn.instatus.com/incident/cmmm411iu017ig0z7zf506bci https://mthn.instatus.com/incident/cmmm411iu017ig0z7zf506bci OFNL Incident: Multiple locations Type: Incident Duration: 7 minutes Affected Components: OFNL Mar 9, 15:34:46 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **Multiple locations** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Mar 9, 15:41:45 GMT+0 - Monitoring - Please see the latest Update below: > **Update (09 Mar 2026 15:40hrs)** > **We are now seeing services recover and are confident that the issue has been resolved.** > > **Our teams will continue to investigate the root cause and closely monitor performance as services fully stabilise.** > > **Thank you for your patience and understanding.** Mar 9, 15:41:46 GMT+0 - Resolved - Please find the latest update below: > **Update (09 Mar 2026 16:21hrs)** > Work to restore service was completed at 15:03 on 09/03/2026\. Customers should now find all services operating as expected. We will continue to monitor performance to ensure stability. > > If you experience any issues after this time, please report them through the usual channels so they can be investigated as individual cases. > > We apologise once again for any inconvenience caused and thank you for your patience throughout this incident. Type: Incident

Duration: 7 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>15:34:46</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **Multiple locations** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>15:41:45</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest Update below: > **Update (09 Mar 2026 15:40hrs)** > **We are now seeing services recover and are confident that the issue has been resolved.** > > **Our teams will continue to investigate the root cause and closely monitor performance as services fully stabilise.** > > **Thank you for your patience and understanding.**.</p> <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>15:41:46</var> GMT+0</small><br><strong>Resolved</strong> - Please find the latest update below: > **Update (09 Mar 2026 16:21hrs)** > Work to restore service was completed at 15:03 on 09/03/2026\. Customers should now find all services operating as expected. We will continue to monitor performance to ensure stability. > > If you experience any issues after this time, please report them through the usual channels so they can be investigated as individual cases. > > We apologise once again for any inconvenience caused and thank you for your patience throughout this incident..</p> ]]> Mon, 9 Mar 2026 15:34:46 +0000 https://mthn.instatus.com/incident/cmmjcdyz2001odlrvruw5qk38 https://mthn.instatus.com/incident/cmmjcdyz2001odlrvruw5qk38 OFNL Incident: NN17, and Possibly NN18 Type: Incident Duration: 4 hours and 44 minutes Affected Components: OFNL Mar 8, 15:39:51 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **CORBY** **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. Mar 8, 15:54:00 GMT+0 - Identified - Please find the latest update below: > An engineer is currently on the way with replacement equipment to restore services. The issue is only affecting around 3 percent of customers in the Corby NN17 area. Further updates will be provided once the engineer is on location and work progresses. > Customers should continue to avoid resetting their equipment. Mar 8, 18:16:59 GMT+0 - Monitoring - We are still chasing the next update from The OFNL Network. However, we are posting this update because we have reason to believe this incident is also impacting a small number of services in the **NN18** region. This has yet to be confirmed by The OFNL Network, but we are investigating accordingly. As always, thank you for your patience and understanding with us. Kind regards, Your MTH Networks Team. Mar 8, 18:48:00 GMT+0 - Identified - Please find the latest update below: > Please be advised an engineer is expected to arrive at approximately 19:30 and is carrying replacement equipment. > > We anticipate a brief outage for all customers served by the affected equipment while the replacement is completed. > > Further updates will be provided once work begins. Mar 8, 19:34:00 GMT+0 - Identified - Please see the latest update below: **Update (08 Mar 2026 19:34hrs)** An engineer is due to arrive shortly with replacement equipment. To carry out the repair, the engineer will need to remove and reinstall hardware, which will briefly interrupt service for some additional customers while the work is taking place. This short interruption is expected as part of the restoration process, and service will return once the replacement is complete. Further updates will follow as the work progresses. Mar 8, 20:23:00 GMT+0 - Monitoring - Please see the latest update below: **Update (08 Mar 2026 20:23hrs)** Work to restore service was completed at 20:05 on 08/03/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. Mar 8, 20:24:00 GMT+0 - Resolved - Please see latest update below: > **_Update (08 Mar 2026 20:24hrs)_** > **_This incident was closed on Sunday, March 8th, 2026 at 20:24hrs._** Type: Incident

Duration: 4 hours and 44 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>15:39:51</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** **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>Mar <var data-var='date'> 8</var>, <var data-var='time'>15:54:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > An engineer is currently on the way with replacement equipment to restore services. The issue is only affecting around 3 percent of customers in the Corby NN17 area. Further updates will be provided once the engineer is on location and work progresses. > Customers should continue to avoid resetting their equipment..</p> <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>18:16:59</var> GMT+0</small><br><strong>Monitoring</strong> - We are still chasing the next update from The OFNL Network. However, we are posting this update because we have reason to believe this incident is also impacting a small number of services in the **NN18** region. This has yet to be confirmed by The OFNL Network, but we are investigating accordingly. As always, thank you for your patience and understanding with us. Kind regards, Your MTH Networks Team..</p> <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>18:48:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > Please be advised an engineer is expected to arrive at approximately 19:30 and is carrying replacement equipment. > > We anticipate a brief outage for all customers served by the affected equipment while the replacement is completed. > > Further updates will be provided once work begins..</p> <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>19:34:00</var> GMT+0</small><br><strong>Identified</strong> - Please see the latest update below: **Update (08 Mar 2026 19:34hrs)** An engineer is due to arrive shortly with replacement equipment. To carry out the repair, the engineer will need to remove and reinstall hardware, which will briefly interrupt service for some additional customers while the work is taking place. This short interruption is expected as part of the restoration process, and service will return once the replacement is complete. Further updates will follow as the work progresses..</p> <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>20:23:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update below: **Update (08 Mar 2026 20:23hrs)** Work to restore service was completed at 20:05 on 08/03/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>Mar <var data-var='date'> 8</var>, <var data-var='time'>20:24:00</var> GMT+0</small><br><strong>Resolved</strong> - Please see latest update below: > **_Update (08 Mar 2026 20:24hrs)_** > **_This incident was closed on Sunday, March 8th, 2026 at 20:24hrs._**.</p> ]]> Sun, 8 Mar 2026 15:39:51 +0000 https://mthn.instatus.com/incident/cmmhx4p6j06jw5u7yadj7asqf https://mthn.instatus.com/incident/cmmhx4p6j06jw5u7yadj7asqf Potential Incident: WA12 & WA5 Type: Incident Duration: 9 hours and 25 minutes Affected Components: Freedom Fibre Mar 5, 07:46:58 GMT+0 - Investigating - We are aware of reports from customers experiencing network outages in **WA12 & WA5**. Our teams are currently investigating and working with our core network teams to understand the cause and implement appropriate countermeasures. We are seeing many connections already restored. We will provide further updates as soon as more information is available. Your patience and understanding with us are much appreciated. Kind regards, Your MTH Networks Team. Mar 5, 10:54:20 GMT+0 - Resolved - Hello all, FreedomFibre and their teams have now deemed this to be resolved, as services are now restored after works were finished. They will continue to monitor to ensure stability. Mar 5, 11:41:49 GMT+0 - Monitoring - Hello All, Just as reassurance, we are aware that some users are still unable to get online after this resolution update. We are aware of this, and are now working with FreedomFibre to ascertain more information. Thank you for your patience. Mar 5, 12:53:29 GMT+0 - Identified - Hello All, The teams at FreedomFibre have now confirmed that this issue is active again, as they have seen reports of users still unable to connect. Thank you to those who reported this to help make us aware of the situation. Kindly bear with us for now as we await for further information. Mar 5, 17:11:54 GMT+0 - Monitoring - Hello All, Our latest update from FreedomFibre states that the issue seems to be coming from external works, which have been causing the impact we are seeing today. It would seem that the external works are now completed. Therefore, they are expecting services to be restored across the board. However, the teams are keeping a close eye on this to ensure that stability is maintained. Therefore, we will keep this open for now and monitor this alongside them. Thank you for your patience. Mar 5, 17:11:55 GMT+0 - Resolved - This incident has been resolved. Mar 5, 14:52:00 GMT+0 - Identified - Hello all! According to reports, some services are now restored and are resuming as normal. However, further works are being done to ensure all connections are working without fault. We expect another update around 5PM today. Thank you for your patience and understanding. Type: Incident

Duration: 9 hours and 25 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>07:46:58</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of reports from customers experiencing network outages in **WA12 & WA5**. Our teams are currently investigating and working with our core network teams to understand the cause and implement appropriate countermeasures. We are seeing many connections already restored. We will provide further updates as soon as more information is available. Your patience and understanding with us are much appreciated. Kind regards, Your MTH Networks Team..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>10:54:20</var> GMT+0</small><br><strong>Resolved</strong> - Hello all, FreedomFibre and their teams have now deemed this to be resolved, as services are now restored after works were finished. They will continue to monitor to ensure stability..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>11:41:49</var> GMT+0</small><br><strong>Monitoring</strong> - Hello All, Just as reassurance, we are aware that some users are still unable to get online after this resolution update. We are aware of this, and are now working with FreedomFibre to ascertain more information. Thank you for your patience..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>12:53:29</var> GMT+0</small><br><strong>Identified</strong> - Hello All, The teams at FreedomFibre have now confirmed that this issue is active again, as they have seen reports of users still unable to connect. Thank you to those who reported this to help make us aware of the situation. Kindly bear with us for now as we await for further information..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>17:11:54</var> GMT+0</small><br><strong>Monitoring</strong> - Hello All, Our latest update from FreedomFibre states that the issue seems to be coming from external works, which have been causing the impact we are seeing today. It would seem that the external works are now completed. Therefore, they are expecting services to be restored across the board. However, the teams are keeping a close eye on this to ensure that stability is maintained. Therefore, we will keep this open for now and monitor this alongside them. Thank you for your patience..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>17:11:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:52:00</var> GMT+0</small><br><strong>Identified</strong> - Hello all! According to reports, some services are now restored and are resuming as normal. However, further works are being done to ensure all connections are working without fault. We expect another update around 5PM today. Thank you for your patience and understanding..</p> ]]> Thu, 5 Mar 2026 07:46:58 +0000 https://mthn.instatus.com/incident/cmmd5wz1k00tjfsr5gv9rfx00 https://mthn.instatus.com/incident/cmmd5wz1k00tjfsr5gv9rfx00 OFNL Incident: London - SE10 Type: Incident Duration: 23 hours and 13 minutes Affected Components: OFNL Mar 2, 11:10:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **London - SE10** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Mar 2, 12:28:00 GMT+0 - Monitoring - Please see the latest update below: > **Update (02 Mar 2026 12:28hrs)** > **Following comprehensive checks of the on-site equipment, we have identified that a brief power fluctuation caused temporary disruption to a number of customer ONTs.** > > **Most services have now recovered; however, any ONTs that remain offline will require a pin-hole reset to restore connectivity.** > > **Our team will continue to monitor the network to ensure services remain stable.** > > **Thank you for your patience.** Mar 2, 17:32:00 GMT+0 - Monitoring - Please see latest Update: > **Update (02 Mar 2026 17:23hrs)** > **We have completed a thorough investigation into the issue impacting a small number of services. The root cause has been identified, and a fix has now been successfully implemented.** > > **All affected services are back online and operating as expected.** > > **Thank you for your patience and understanding while we worked to resolve this incident.** Mar 3, 10:22:43 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 hours and 13 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>11:10: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): > **London - SE10** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>12:28:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update below: > **Update (02 Mar 2026 12:28hrs)** > **Following comprehensive checks of the on-site equipment, we have identified that a brief power fluctuation caused temporary disruption to a number of customer ONTs.** > > **Most services have now recovered; however, any ONTs that remain offline will require a pin-hole reset to restore connectivity.** > > **Our team will continue to monitor the network to ensure services remain stable.** > > **Thank you for your patience.**.</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>17:32:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see latest Update: > **Update (02 Mar 2026 17:23hrs)** > **We have completed a thorough investigation into the issue impacting a small number of services. The root cause has been identified, and a fix has now been successfully implemented.** > > **All affected services are back online and operating as expected.** > > **Thank you for your patience and understanding while we worked to resolve this incident.**.</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:22:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 2 Mar 2026 11:10:00 +0000 https://mthn.instatus.com/incident/cmm966rlo08749r148nt5n22r https://mthn.instatus.com/incident/cmm966rlo08749r148nt5n22r OFNL Incident: NP44 Type: Incident Duration: 3 hours and 2 minutes Affected Components: OFNL Mar 2, 10:30:00 GMT+0 - Investigating - Please see the latest update below: > **Update (02 Mar 2026 10:30hrs)** > **Our engineer has arrived on-site and is investigating the problem.** > > **We will provide further updates when we have any significant news or by 12:30.** Mar 2, 12:35:00 GMT+0 - Identified - Please see latest update below: > **Update (02 Mar 2026 12:35hrs)** > **Our engineers are continuing to investigate the route of the suspect faulty fibre optic cable.** > > **We will provide further updates when we have any significant news or by 14:30.** Mar 2, 13:07:00 GMT+0 - Monitoring - Please see latest update below: > **Update (02 Mar 2026 13:07hrs)** > **Our engineers located and re-spliced a broken fibre.** > > **Work to restore service was completed at 13:05 on 02/03/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.** Mar 2, 13:07:01 GMT+0 - Resolved - This incident has been resolved. Mar 2, 10:04:50 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Cwmbran **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. Type: Incident

Duration: 3 hours and 2 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest update below: > **Update (02 Mar 2026 10:30hrs)** > **Our engineer has arrived on-site and is investigating the problem.** > > **We will provide further updates when we have any significant news or by 12:30.**.</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>12:35:00</var> GMT+0</small><br><strong>Identified</strong> - Please see latest update below: > **Update (02 Mar 2026 12:35hrs)** > **Our engineers are continuing to investigate the route of the suspect faulty fibre optic cable.** > > **We will provide further updates when we have any significant news or by 14:30.**.</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>13:07:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see latest update below: > **Update (02 Mar 2026 13:07hrs)** > **Our engineers located and re-spliced a broken fibre.** > > **Work to restore service was completed at 13:05 on 02/03/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>Mar <var data-var='date'> 2</var>, <var data-var='time'>13:07:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>10:04:50</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Cwmbran **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> ]]> Mon, 2 Mar 2026 10:04:50 +0000 https://mthn.instatus.com/incident/cmm90iq0w06afj5z9e9i474fu https://mthn.instatus.com/incident/cmm90iq0w06afj5z9e9i474fu Potential OFNL Incident: YO7 Type: Incident Duration: 1 day, 21 hours and 34 minutes Affected Components: OFNL Feb 28, 12:54:50 GMT+0 - Investigating - Hello all, Due to the volume of reports in the YO7 area, we suspect that there is an ongoing incident. However, we are yet to receive any official confirmation. Kindly bear with us for now, and apologies for any inconvenience. Feb 28, 19:50:40 GMT+0 - Investigating - Hello All, Unfortunately, we still have not had any official confirmation about a YO7 incident from OFNL. Therefore, there is little we can advise at this time. Once we have more information, we will be sure to relay this immediately. Mar 1, 16:23:09 GMT+0 - Investigating - Good Afternoon all, Unfortunately, we are still yet to receive an official confirmation to the current case that we are seeing in the YO7 area. We have chased for more information, but once we have something, we will be sure to share it right away. Thank you for your continued patience and understanding. Mar 2, 10:29:11 GMT+0 - Investigating - Good Morning all, As you are aware, services in the YO7 area are still down at this time. MTH Networks are currently pushing and chasing for official confirmation, but at this time, we do not have anything to share, sadly. We hope to provide an update later today once we have it. We do apologise for any inconvenience caused, as we are very aware of the ongoing length of this case. Thank you for your understanding. We really appreciate it. Mar 4, 10:29:00 GMT+0 - Resolved - Good morning, Thank you so much for your patience with us. We are glad to confirm that, following our efforts and investigations with The OFNL Network, their senior engineers performed a system switchover at 16:30 yesterday, which has allowed us to observe reconnection within the YO7 region. We have been monitoring the situation, and are both happy and confident that we can confirm this incident has been resolved. If you are still experiencing hardship, your case will need to be reviewed as an individual case. Please find the various avenues for attaining our support below: \- Phone: 01536 661050 \- Email: support@mthnetworks.com \- LiveChat: Accessible via our website Thank you so much for your patience and understanding with us during this time. We will continue our review of this case to ensure that it is not repeated. Kind regards, Your MTH Networks Team. Type: Incident

Duration: 1 day, 21 hours and 34 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>12:54:50</var> GMT+0</small><br><strong>Investigating</strong> - Hello all, Due to the volume of reports in the YO7 area, we suspect that there is an ongoing incident. However, we are yet to receive any official confirmation. Kindly bear with us for now, and apologies for any inconvenience. .</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>19:50:40</var> GMT+0</small><br><strong>Investigating</strong> - Hello All, Unfortunately, we still have not had any official confirmation about a YO7 incident from OFNL. Therefore, there is little we can advise at this time. Once we have more information, we will be sure to relay this immediately..</p> <p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>16:23:09</var> GMT+0</small><br><strong>Investigating</strong> - Good Afternoon all, Unfortunately, we are still yet to receive an official confirmation to the current case that we are seeing in the YO7 area. We have chased for more information, but once we have something, we will be sure to share it right away. Thank you for your continued patience and understanding..</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>10:29:11</var> GMT+0</small><br><strong>Investigating</strong> - Good Morning all, As you are aware, services in the YO7 area are still down at this time. MTH Networks are currently pushing and chasing for official confirmation, but at this time, we do not have anything to share, sadly. We hope to provide an update later today once we have it. We do apologise for any inconvenience caused, as we are very aware of the ongoing length of this case. Thank you for your understanding. We really appreciate it..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:29:00</var> GMT+0</small><br><strong>Resolved</strong> - Good morning, Thank you so much for your patience with us. We are glad to confirm that, following our efforts and investigations with The OFNL Network, their senior engineers performed a system switchover at 16:30 yesterday, which has allowed us to observe reconnection within the YO7 region. We have been monitoring the situation, and are both happy and confident that we can confirm this incident has been resolved. If you are still experiencing hardship, your case will need to be reviewed as an individual case. Please find the various avenues for attaining our support below: \- Phone: 01536 661050 \- Email: support@mthnetworks.com \- LiveChat: Accessible via our website Thank you so much for your patience and understanding with us during this time. We will continue our review of this case to ensure that it is not repeated. Kind regards, Your MTH Networks Team..</p> ]]> Sat, 28 Feb 2026 12:54:50 +0000 https://mthn.instatus.com/incident/cmm6bp9hu08gs868by37n53gu https://mthn.instatus.com/incident/cmm6bp9hu08gs868by37n53gu OFNL Incident: Multiple Locations (TBC) Type: Incident Duration: 2 hours and 38 minutes Affected Components: OFNL Feb 25, 14:58:00 GMT+0 - Investigating - Please see the latest update below: > **Update (25 Feb 2026 14:58hrs)** > **We have escalated this incident internally and assembled an incident response team that is actively investigating the issue.** > > **We will provide further updates as soon as additional information becomes available.** Feb 25, 13:13:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): Multiple Locations (TBC) **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. Feb 25, 15:50:50 GMT+0 - Resolved - Please see the latest update below: **Update (25 Feb 2026 15:37hrs)** We are aware of a network incident that occurred between 13:00 and 14:00 on 25/02/2026\. Our incident response team is working alongside our specialist third party network support partners to investigate the issue and determine the root cause. We are actively monitoring the network for any further issues. Thank you for your patience, and we apologise for any inconvenience this may have caused. Type: Incident

Duration: 2 hours and 38 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>14:58:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest update below: > **Update (25 Feb 2026 14:58hrs)** > **We have escalated this incident internally and assembled an incident response team that is actively investigating the issue.** > > **We will provide further updates as soon as additional information becomes available.**.</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>13:13:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): Multiple Locations (TBC) **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>Feb <var data-var='date'> 25</var>, <var data-var='time'>15:50:50</var> GMT+0</small><br><strong>Resolved</strong> - Please see the latest update below: **Update (25 Feb 2026 15:37hrs)** We are aware of a network incident that occurred between 13:00 and 14:00 on 25/02/2026\. Our incident response team is working alongside our specialist third party network support partners to investigate the issue and determine the root cause. We are actively monitoring the network for any further issues. Thank you for your patience, and we apologise for any inconvenience this may have caused..</p> ]]> Wed, 25 Feb 2026 13:13:00 +0000 https://mthn.instatus.com/incident/cmm24e54p0bclhrimldlfri84 https://mthn.instatus.com/incident/cmm24e54p0bclhrimldlfri84 Freedom Fibre Incident: Northwich & Hartford Type: Incident Duration: 23 hours and 44 minutes Affected Components: Freedom Fibre Feb 24, 14:30:00 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): CW9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Feb 25, 08:18:30 GMT+0 - Investigating - Good morning. We are receiving a high Volume of calls in CW9 area regarding customers being offline. As per the last update, this incident looked to have been resolved, however this doesn't look to be the case. We are currently looking into this with Freedom Fibre as we speak, as soon as we have any updates, we will be in touch. Thank you for your understanding and patience. Feb 24, 14:33:00 GMT+0 - Resolved - Please see below update: **_FF field engineering attended site and found damaged fibres inside a local splitter. Fibres were replaced and the splitter was rebuilt restoring service to all impacted customers. FF NOC will monitor the services for the next 24 hours to ensure stability. Incident resovled._** Feb 25, 08:54:01 GMT+0 - Investigating - Good Morning. We have had confirmation that there is an incident in the CW8/CW9 areas. Please see the latest Update from Freedom Fibre below: > **_FF network engineering have been informed and will begin investigations. Further updates to follow._** Feb 25, 10:24:27 GMT+0 - Identified - Please see latest update below: > **_Link flap was attempted in efforts to restore service however this did not work and services remain down. Network engineering are now in the process of rebuilding bridges between the OLT and AGN to try and restore. Further updates will be provided._** Feb 25, 11:23:00 GMT+0 - Identified - Hello All, The FreedomFibre teams have been able to rebuild the link between the services, but did not successfully restore the connection for affected users. Investigations are still proceeding at this time with the next update due around 12:30PM Feb 25, 11:23:01 GMT+0 - Identified - Hello All, The engineering teams on site have reported that they have been able to reboot the network node in the area, but this has not made any changes. Their next step is to deliver a specialist team to the site to perform further work to restore the service. Next update is due for 13:30 today. Thank you for your patience. Feb 25, 14:14:00 GMT+0 - Resolved - Hello all, The network engineers that arrived on site recently have been able to apply their fix. They are reporting that connections are resuming and have been restored. The teams will closely monitor this in the meantime to ensure the network is stable. We apologise on their behalf for the downtime, but we thank you for your patience. Type: Incident

Duration: 23 hours and 44 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): CW9 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>08:18:30</var> GMT+0</small><br><strong>Investigating</strong> - Good morning. We are receiving a high Volume of calls in CW9 area regarding customers being offline. As per the last update, this incident looked to have been resolved, however this doesn't look to be the case. We are currently looking into this with Freedom Fibre as we speak, as soon as we have any updates, we will be in touch. Thank you for your understanding and patience. .</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:33:00</var> GMT+0</small><br><strong>Resolved</strong> - Please see below update: **_FF field engineering attended site and found damaged fibres inside a local splitter. Fibres were replaced and the splitter was rebuilt restoring service to all impacted customers. FF NOC will monitor the services for the next 24 hours to ensure stability. Incident resovled._**.</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>08:54:01</var> GMT+0</small><br><strong>Investigating</strong> - Good Morning. We have had confirmation that there is an incident in the CW8/CW9 areas. Please see the latest Update from Freedom Fibre below: > **_FF network engineering have been informed and will begin investigations. Further updates to follow._**.</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>10:24:27</var> GMT+0</small><br><strong>Identified</strong> - Please see latest update below: > **_Link flap was attempted in efforts to restore service however this did not work and services remain down. Network engineering are now in the process of rebuilding bridges between the OLT and AGN to try and restore. Further updates will be provided._**.</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>11:23:00</var> GMT+0</small><br><strong>Identified</strong> - Hello All, The FreedomFibre teams have been able to rebuild the link between the services, but did not successfully restore the connection for affected users. Investigations are still proceeding at this time with the next update due around 12:30PM.</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>11:23:01</var> GMT+0</small><br><strong>Identified</strong> - Hello All, The engineering teams on site have reported that they have been able to reboot the network node in the area, but this has not made any changes. Their next step is to deliver a specialist team to the site to perform further work to restore the service. Next update is due for 13:30 today. Thank you for your patience..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>14:14:00</var> GMT+0</small><br><strong>Resolved</strong> - Hello all, The network engineers that arrived on site recently have been able to apply their fix. They are reporting that connections are resuming and have been restored. The teams will closely monitor this in the meantime to ensure the network is stable. We apologise on their behalf for the downtime, but we thank you for your patience..</p> ]]> Tue, 24 Feb 2026 14:30:00 +0000 https://mthn.instatus.com/incident/cmm1r1gx808tbqwjbusa0fg7z https://mthn.instatus.com/incident/cmm1r1gx808tbqwjbusa0fg7z Freedom Fibre Incident: INC10000421 (ST1) Type: Incident Duration: 1 hour and 25 minutes Affected Components: Freedom Fibre Feb 19, 15:48:20 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): * ST1 - Stoke Hanley **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. Feb 19, 17:13:31 GMT+0 - Resolved - Hello all, This has now been resolved: > **Latest update:** _FF field engineering identified an issue with damaged fibres in one of the shelters. The fibres were replaced and respliced restoring full service to impacted customers. After a short monitoring period it is now confirmed that the services are back online and have remained stable since._ Type: Incident

Duration: 1 hour and 25 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>15:48:20</var> GMT+0</small><br><strong>Investigating</strong> - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): * ST1 - Stoke Hanley **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>Feb <var data-var='date'> 19</var>, <var data-var='time'>17:13:31</var> GMT+0</small><br><strong>Resolved</strong> - Hello all, This has now been resolved: > **Latest update:** _FF field engineering identified an issue with damaged fibres in one of the shelters. The fibres were replaced and respliced restoring full service to impacted customers. After a short monitoring period it is now confirmed that the services are back online and have remained stable since._.</p> ]]> Thu, 19 Feb 2026 15:48:20 +0000 https://mthn.instatus.com/incident/cmltmxx5s0dvwmk9etm6j18u3 https://mthn.instatus.com/incident/cmltmxx5s0dvwmk9etm6j18u3 OFNL Incident: Matlock, DE4 Type: Incident Duration: 4 hours and 34 minutes Affected Components: OFNL Feb 18, 12:06:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): Matlock, DE4 **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. Feb 18, 14:56:00 GMT+0 - Monitoring - Please see the latest update: **Update (18 Feb 2026 14:56hrs)** Our third party service provider has confirmed that their equipment has remained stable for the past two hours. Their engineers are continuing to perform further checks to ensure ongoing service stability. We will share additional updates as soon as new information becomes available. Feb 18, 16:40:00 GMT+0 - Resolved - Please see latest update below: > **Update (18 Feb 2026 16:40hrs)** > **Services have remained stable since 12:05 18/02/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.** Type: Incident

Duration: 4 hours and 34 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>12:06:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): Matlock, DE4 **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>Feb <var data-var='date'> 18</var>, <var data-var='time'>14:56:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update: **Update (18 Feb 2026 14:56hrs)** Our third party service provider has confirmed that their equipment has remained stable for the past two hours. Their engineers are continuing to perform further checks to ensure ongoing service stability. We will share additional updates as soon as new information becomes available..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>16:40:00</var> GMT+0</small><br><strong>Resolved</strong> - Please see latest update below: > **Update (18 Feb 2026 16:40hrs)** > **Services have remained stable since 12:05 18/02/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> ]]> Wed, 18 Feb 2026 12:06:00 +0000 https://mthn.instatus.com/incident/cmls0a72f047011k0o58vaapl https://mthn.instatus.com/incident/cmls0a72f047011k0o58vaapl