MTH Networks Status - Incident history https://mthn.instatus.com MTH Networks Mon, 20 Jul 2026 23:00:00 +0000 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Jun 16, 12:00:37 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Worcester A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>12:00:37</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Worcester A brief Service Outage will be expected during the maintenance window..</p> ]]> Mon, 20 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqglbxa805ph2orozeikbs93 https://mthn.instatus.com/maintenance/cmqglbxa805ph2orozeikbs93 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Jun 16, 11:59:45 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Solihull, Stamford A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>11:59:45</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Solihull, Stamford A brief Service Outage will be expected during the maintenance window..</p> ]]> Sat, 18 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqglasrg00nu2io5rb9l7em8 https://mthn.instatus.com/maintenance/cmqglasrg00nu2io5rb9l7em8 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Jun 16, 11:59:05 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Peterborough A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>11:59:05</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Peterborough A brief Service Outage will be expected during the maintenance window..</p> ]]> Thu, 16 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqgl9xxp01wl2plgwv46rr71 https://mthn.instatus.com/maintenance/cmqgl9xxp01wl2plgwv46rr71 CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Jun 15, 10:04:26 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > March A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>10:04:26</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > March A brief Service Outage will be expected during the maintenance window..</p> ]]> Tue, 14 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqf1qn9w0aoz2ip9xapncw5k https://mthn.instatus.com/maintenance/cmqf1qn9w0aoz2ip9xapncw5k CityFibre Maintenance Type: Maintenance Affected Components: CityFibre Jun 15, 10:00:19 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > March A brief Service Outage will be expected during the maintenance window. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>10:00:19</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > March A brief Service Outage will be expected during the maintenance window..</p> ]]> Mon, 13 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqf1lcyq01dj2jqjp9j0v0u1 https://mthn.instatus.com/maintenance/cmqf1lcyq01dj2jqjp9j0v0u1 OFNL Maintenance: Alresford CO7 Tendring CO16 Type: Maintenance Affected Components: OFNL Jul 12, 18:18:49 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Alresford CO7 Tendring CO16 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Type: Maintenance

Affected Components:

<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>18:18:49</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Alresford CO7 Tendring CO16 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> ]]> Mon, 13 Jul 2026 22:00:00 +0000 https://mthn.instatus.com/maintenance/cmri4afiz003q1alv3btr4cfb https://mthn.instatus.com/maintenance/cmri4afiz003q1alv3btr4cfb OFNL Incident: Huntingdon PE28 Type: Incident Affected Components: OFNL Jul 12, 14:08:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>14:08:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> ]]> Sun, 12 Jul 2026 14:08:00 +0000 https://mthn.instatus.com/incident/cmrhwno3r0uxi0zq65riorrbj https://mthn.instatus.com/incident/cmrhwno3r0uxi0zq65riorrbj CityFibre Maintenance Type: Maintenance Duration: 6 hours Affected Components: CityFibre Jun 12, 08:32:30 GMT+0 - Identified - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Hinckley A brief Service Outage will be expected during the maintenance window. Jul 10, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 11, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>08:32:30</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Hinckley A brief Service Outage will be expected during the maintenance window..</p> <p><small>Jul <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>Jul <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> ]]> Fri, 10 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmqao4uvt08wyquezljolf2sg https://mthn.instatus.com/maintenance/cmqao4uvt08wyquezljolf2sg OFNL Maintenance: Swindon SN4 Type: Maintenance Duration: 8 hours Affected Components: OFNL Jul 9, 14:39:13 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Swindon SN4 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 10, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 8 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:39:13</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Swindon SN4 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Jul 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm4h4201a50rs3fuuzbosb https://mthn.instatus.com/maintenance/cmrdm4h4201a50rs3fuuzbosb OFNL Maintenance: Caddington LU1 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:39:41 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Caddington LU1 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:39:41</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Caddington LU1 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm52s807ya0zlh22bkubda https://mthn.instatus.com/maintenance/cmrdm52s807ya0zlh22bkubda OFNL Maintenance: Aylesbury HP22 HP19 HP18 HP20 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:40:07 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Aylesbury HP22 HP19 HP18 HP20 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:40:07</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Aylesbury HP22 HP19 HP18 HP20 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm5mlk00050rnrdx6askpv https://mthn.instatus.com/maintenance/cmrdm5mlk00050rnrdx6askpv OFNL Maintenance: Darlington DL2 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:40:28 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Darlington DL2 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:40:28</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Darlington DL2 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm62v1007h0lnncngwt4lm https://mthn.instatus.com/maintenance/cmrdm62v1007h0lnncngwt4lm OFNL Maintenance: Basildon CM12 CM5 SS15 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:40:54 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Basildon CM12 CM5 SS15 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:40:54</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Basildon CM12 CM5 SS15 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm6mli094n0rlhjhcr6os4 https://mthn.instatus.com/maintenance/cmrdm6mli094n0rlhjhcr6os4 OFNL Maintenance: Bicester OX25 OX26 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:41:20 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Bicester OX25 OX26 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:41:20</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Bicester OX25 OX26 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm76wp098q1blhk5w0pazt https://mthn.instatus.com/maintenance/cmrdm76wp098q1blhk5w0pazt OFNL Maintenance: Bracknell RG12 RG42 RG40 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:41:55 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Bracknell RG12 RG42 RG40 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:41:55</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Bracknell RG12 RG42 RG40 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm7y2h01dx0ks3o5amgivu https://mthn.instatus.com/maintenance/cmrdm7y2h01dx0ks3o5amgivu OFNL Maintenance: Milton Keynes MK10 MK13 MK16 MK17 MK20 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 9, 14:42:19 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Milton Keynes MK10 MK13 MK16 MK17 MK20 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 10, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>14:42:19</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Milton Keynes MK10 MK13 MK16 MK17 MK20 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrdm8g5l094t0rlht0xy1nwp https://mthn.instatus.com/maintenance/cmrdm8g5l094t0rlht0xy1nwp OFNL Incident: Greenwich SE10 Type: Incident Duration: 1 hour and 31 minutes Affected Components: OFNL Jul 9, 09:23:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Greenwich SE10 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jul 9, 10:54:00 GMT+0 - Monitoring - Please see the latest update from OFNL below: > **Update (09 Jul 2026 11:54hrs)** > Work to restore service was completed at 11:50 on 09/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > 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. Jul 9, 10:54:01 GMT+0 - Resolved - Please see latest update below: **Update (09 Jul 2026 11:54hrs)** This incident was closed on Thursday, July 9th, 2026 at 11:54hrs. Type: Incident

Duration: 1 hour and 31 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>09:23:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Greenwich SE10 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>10:54:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update from OFNL below: > **Update (09 Jul 2026 11:54hrs)** > Work to restore service was completed at 11:50 on 09/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > 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>Jul <var data-var='date'> 9</var>, <var data-var='time'>10:54:01</var> GMT+0</small><br><strong>Resolved</strong> - Please see latest update below: **Update (09 Jul 2026 11:54hrs)** This incident was closed on Thursday, July 9th, 2026 at 11:54hrs..</p> ]]> Thu, 9 Jul 2026 09:23:00 +0000 https://mthn.instatus.com/incident/cmrdb7cqx01cs0rlaqu6ub4yn https://mthn.instatus.com/incident/cmrdb7cqx01cs0rlaqu6ub4yn OFNL Maintenance: DN11 Doncaster Type: Maintenance Duration: 8 hours and 5 minutes Affected Components: OFNL Jul 8, 23:00:00 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): * DN11 Doncaster Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 9, 07:05:00 GMT+0 - Completed - **Update (09 Jul 2026 08:05hrs)** This Planned Maintenance was completed on Thursday, July 9th, 2026 at 08:05hrs. Type: Maintenance

Duration: 8 hours and 5 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): * DN11 Doncaster Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>07:05:00</var> GMT+0</small><br><strong>Completed</strong> - **Update (09 Jul 2026 08:05hrs)** This Planned Maintenance was completed on Thursday, July 9th, 2026 at 08:05hrs..</p> ]]> Wed, 8 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrd9dxhd05is0klj8k0e28mp https://mthn.instatus.com/maintenance/cmrd9dxhd05is0klj8k0e28mp OFNL Incident: Maidenhead SL6. Type: Incident Affected Components: OFNL Jul 8, 12:00:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Maidenhead SL6. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jul 8, 12:00:01 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

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

Duration: 9 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:33:54</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Leicester LE1 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 8 Jul 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar1xkx08170kn6p8j04y2l https://mthn.instatus.com/maintenance/cmrar1xkx08170kn6p8j04y2l OFNL Maintenance: Stanton Cross NN8. Type: Maintenance Duration: 9 hours Affected Components: OFNL Jul 7, 14:33:23 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Stanton Cross NN8. Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 8, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 16:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 9 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:33:23</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Stanton Cross NN8. Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 8 Jul 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar19d208020zpi5jvhs8ms https://mthn.instatus.com/maintenance/cmrar19d208020zpi5jvhs8ms OFNL Maintenance: Essex CB10 CB11 Type: Maintenance Duration: 9 hours Affected Components: OFNL Jul 7, 14:32:57 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Essex CB10 CB11 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 8, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 16:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 9 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:32:57</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Essex CB10 CB11 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 8 Jul 2026 07:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar0pb507xz0rn6c2n5fizr https://mthn.instatus.com/maintenance/cmrar0pb507xz0rn6c2n5fizr OFNL Maintenance: London N1 N1C Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 7, 14:41:12 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > London N1 N1C Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 7, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:41:12</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > London N1 N1C Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 7 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrarbazn08ii1ans4dy55gc4 https://mthn.instatus.com/maintenance/cmrarbazn08ii1ans4dy55gc4 OFNL Maintenance: Bramford IP8 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 7, 14:40:12 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Bramford IP8 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 7, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

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

Duration: 6 hours

Affected Components:

<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>08:15:50</var> GMT+0</small><br><strong>Identified</strong> - CityFibre are conducting planned maintenance on their network. Affecting Services to the below areas: > Felixstowe A brief Service Outage will be expected during the maintenance window..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 7 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmq983kus0403qoa153bfvqr9 https://mthn.instatus.com/maintenance/cmq983kus0403qoa153bfvqr9 OFNL Maintenance: Consett DH8 Rugby CV23 Harrogate HG3 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 7, 14:34:24 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Consett DH8 Rugby CV23 Harrogate HG3 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 7, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:34:24</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Consett DH8 Rugby CV23 Harrogate HG3 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 7 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar2kaw081c0kn6yovyochw https://mthn.instatus.com/maintenance/cmrar2kaw081c0kn6yovyochw OFNL Maintenance: Eggington LU7 Type: Maintenance Duration: 3 hours Affected Components: OFNL Jul 7, 14:34:43 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Eggington LU7 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 7, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 02:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:34:43</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Eggington LU7 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 7 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar2z8p08ju0zn6jjcqz2nh https://mthn.instatus.com/maintenance/cmrar2z8p08ju0zn6jjcqz2nh OFNL Maintenance: Brackley NN13 Type: Maintenance Duration: 6 hours Affected Components: OFNL Jul 7, 14:35:07 GMT+0 - Identified - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Brackley NN13 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding. Jul 7, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 8, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 6 hours

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>14:35:07</var> GMT+0</small><br><strong>Identified</strong> - The OFNL Network has made us aware of some scheduled maintenance. This maintenance may impact the following location(s): > Brackley NN13 Addresses located in this region may experience service interruptions. We and the OFNL Network will always endeavour to minimise the impact wherever possible. The OFNL Network may be required to expedite maintenance activity ahead of schedule, but will always provide prior notice where possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 7 Jul 2026 23:00:00 +0000 https://mthn.instatus.com/maintenance/cmrar3hhq08p10rnsqepvno7l https://mthn.instatus.com/maintenance/cmrar3hhq08p10rnsqepvno7l OFNL Incident: Pevensey BN23 BN24 Type: Incident Duration: 6 hours and 55 minutes Affected Components: OFNL Jul 5, 08:27:00 GMT+0 - Identified - Please find OFNL's latest reply: > **Update (05 Jul 2026 09:27hrs)** > Our engineer is on route to site and has a current ETA of 12:00. > > Once the engineer is on site, we will work to restore power to equipment as soon as possible to bring services online and continue to investigate main power supply issues. Jul 5, 08:00:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Pevensey BN23 BN24 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jul 5, 11:40:00 GMT+0 - Identified - Please find the latest here: > **Update (05 Jul 2026 12:40hrs)** > Our engineer is on site and completing testing of site equipment, we have identified we no mains power reaching the cabinet equipment and will require attendance of the electrical supplier. > > In the meantime our engineer is charging the on site batteries to restore back up power to the cab and ensure services restore to customers. > > We will continue to update you as we progress to resolving this fault. Jul 5, 12:33:00 GMT+0 - Identified - Please find the latest update: > **Update (05 Jul 2026 13:33hrs)** > Our on site engineer has managed to charge the cabinet battery back ups and we are no seeing restoration of key equipment. > > We are also observing customer services restoring across the site. We will continue to monitor this carefully to ensure equipment remains powered up via the battery back ups. > > We have also had confirmation of third party engineer attending site to look into mains power issue, current ETA is 17:00. > > Thank you for your patience while we work on this fault. Jul 5, 14:44:00 GMT+0 - Monitoring - Please find the latest: > **Update (05 Jul 2026 15:44hrs)** > Third party engineers have completed works on site to restore mains power to our cabinet, there is still further works required so we may see this further disrupted. > > We still have battery back up power restored on site and this will prevent any further impact to customer services. Our engineer will also remain on standby on site for now. Jul 5, 14:55:00 GMT+0 - Resolved - Please find their resolving statement here: > **Update (05 Jul 2026 15:55hrs)** > Work to restore service was completed at 13:25 on 05/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > We now have mains power and battery back up power to cope with any further mains disruption, we do not expect any further customer service impact. > > 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: 6 hours and 55 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>08:27:00</var> GMT+0</small><br><strong>Identified</strong> - Please find OFNL's latest reply: > **Update (05 Jul 2026 09:27hrs)** > Our engineer is on route to site and has a current ETA of 12:00. > > Once the engineer is on site, we will work to restore power to equipment as soon as possible to bring services online and continue to investigate main power supply issues..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Pevensey BN23 BN24 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>11:40:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest here: > **Update (05 Jul 2026 12:40hrs)** > Our engineer is on site and completing testing of site equipment, we have identified we no mains power reaching the cabinet equipment and will require attendance of the electrical supplier. > > In the meantime our engineer is charging the on site batteries to restore back up power to the cab and ensure services restore to customers. > > We will continue to update you as we progress to resolving this fault..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>12:33:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update: > **Update (05 Jul 2026 13:33hrs)** > Our on site engineer has managed to charge the cabinet battery back ups and we are no seeing restoration of key equipment. > > We are also observing customer services restoring across the site. We will continue to monitor this carefully to ensure equipment remains powered up via the battery back ups. > > We have also had confirmation of third party engineer attending site to look into mains power issue, current ETA is 17:00. > > Thank you for your patience while we work on this fault..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>14:44:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please find the latest: > **Update (05 Jul 2026 15:44hrs)** > Third party engineers have completed works on site to restore mains power to our cabinet, there is still further works required so we may see this further disrupted. > > We still have battery back up power restored on site and this will prevent any further impact to customer services. Our engineer will also remain on standby on site for now..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>14:55:00</var> GMT+0</small><br><strong>Resolved</strong> - Please find their resolving statement here: > **Update (05 Jul 2026 15:55hrs)** > Work to restore service was completed at 13:25 on 05/07/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > We now have mains power and battery back up power to cope with any further mains disruption, we do not expect any further customer service impact. > > 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> ]]> Sun, 5 Jul 2026 08:00:00 +0000 https://mthn.instatus.com/incident/cmr7mp6u90y3e0kqfrve7n9bb https://mthn.instatus.com/incident/cmr7mp6u90y3e0kqfrve7n9bb Freedom Fibre Incident: INC10000485 (TF6 & SY4) Type: Incident Duration: 11 hours and 53 minutes Affected Components: Freedom Fibre Jun 30, 09:00:00 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > TF6 & SY4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jun 30, 13:57:00 GMT+0 - Identified - Freedom Fibre and their engineers are still on site working through this issue, and reconnecting the fibres at this time. Next update is scheduled for or around 17:30 today. Jun 30, 16:26:00 GMT+0 - Identified - Engineers are still on site working on this. The next update should come from Freedom Fibre at around 19:30, 30/06/2026\. This is beyond our office opening times, though we will do our best to have these updates before we close and when we reopen. Thank you for your patience. Jun 30, 20:53:00 GMT+0 - Resolved - Since 9:53 on 30/06/2026, the Freedom Fibre engineers confirmed that all services were restored following the repair of the fibre connection. If you are still experiencing issues, please email us at Support@MTHNetworks.com, and we will provide support accordingly! Thank you for your patience and understanding. Type: Incident

Duration: 11 hours and 53 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > TF6 & SY4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>13:57:00</var> GMT+0</small><br><strong>Identified</strong> - Freedom Fibre and their engineers are still on site working through this issue, and reconnecting the fibres at this time. Next update is scheduled for or around 17:30 today..</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>16:26:00</var> GMT+0</small><br><strong>Identified</strong> - Engineers are still on site working on this. The next update should come from Freedom Fibre at around 19:30, 30/06/2026\. This is beyond our office opening times, though we will do our best to have these updates before we close and when we reopen. Thank you for your patience..</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>20:53:00</var> GMT+0</small><br><strong>Resolved</strong> - Since 9:53 on 30/06/2026, the Freedom Fibre engineers confirmed that all services were restored following the repair of the fibre connection. If you are still experiencing issues, please email us at Support@MTHNetworks.com, and we will provide support accordingly! Thank you for your patience and understanding..</p> ]]> Tue, 30 Jun 2026 09:00:00 +0000 https://mthn.instatus.com/incident/cmr0fmkwa06e00kphl22yeg8c https://mthn.instatus.com/incident/cmr0fmkwa06e00kphl22yeg8c OFNL Incident: Derby DE3 Type: Incident Duration: 2 days, 5 hours and 48 minutes Affected Components: OFNL Jun 30, 08:30:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): * Derby DE3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jul 2, 14:17:37 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 5 hours and 48 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): * Derby DE3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:17:37</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 30 Jun 2026 08:30:00 +0000 https://mthn.instatus.com/incident/cmr0feaoa06i70zrrl2ko5s5v https://mthn.instatus.com/incident/cmr0feaoa06i70zrrl2ko5s5v MS3 Incident: Grimsby Type: Incident Affected Components: MS3 Jun 29, 20:35:00 GMT+0 - Resolved - Hi, The MS3 Network has made us aware of an incident experienced in the Grimsby area. As of 21:35, on 29/06/2026, this incident was resolved. A long-term solution has been implemented, and so we are happy to close this incident. We thank you for your patience and understanding. Kind regards, Your MTH Networks Team. Type: Incident

Affected Components:

<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>20:35:00</var> GMT+0</small><br><strong>Resolved</strong> - Hi, The MS3 Network has made us aware of an incident experienced in the Grimsby area. As of 21:35, on 29/06/2026, this incident was resolved. A long-term solution has been implemented, and so we are happy to close this incident. We thank you for your patience and understanding. Kind regards, Your MTH Networks Team..</p> ]]> Mon, 29 Jun 2026 20:35:00 +0000 https://mthn.instatus.com/incident/cmr0fdws9000f0zmqeexsn9u2 https://mthn.instatus.com/incident/cmr0fdws9000f0zmqeexsn9u2 OFNL Incident: Westoning MK45 Type: Incident Duration: 6 days, 7 hours and 1 minute Affected Components: OFNL Jun 26, 07:17:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Westoning MK45 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jun 26, 09:24:00 GMT+0 - Investigating - Please see latest update from OFNL below: > **Update (26 Jun 2026 10:24hrs)** > An OFNL engineering team has been dispatched to site, with an estimated time of arrival of 12:00 on 26/06/2026, to carry out fault investigation. > > This issue has also been raised with our third-party provider, who are currently investigating their equipment in parallel. > > Further updates will be provided as more information becomes available. Jun 26, 12:39:00 GMT+0 - Investigating - Please see update from OFNL below: > **Update (26 Jun 2026 13:39hrs)** > Engineering teams are currently on site investigating the fibre fault. We are also actively liaising with our third-party provider for further updates. > > Additional updates will be provided as soon as more information becomes available. Jun 26, 16:17:00 GMT+0 - Investigating - Please see latest update below: > **Update (26 Jun 2026 17:17hrs)** > Our engineers have completed testing and cannot find fault within our purview. > > We have escalated the fault to a third-party supplier and are awaiting feedback from their testing. > > Our third-party supplier is unable to provide any timeframe for a response due to the heatwave that has caused major disruption across the UK telecommunications network, which in turn is influencing response times from engineering teams. > > Further updates will be provided as more information becomes available. Jun 27, 20:13:00 GMT+0 - Investigating - Please see update below: > **Update (27 Jun 2026 21:13hrs)** > The third-party supplier has arranged for an engineer to investigate the equipment outside of our network that supplies this area. > > We will continue to provide updates as soon as they become available. Jun 27, 10:57:00 GMT+0 - Investigating - Please see update below: **Update (27 Jun 2026 11:57hrs)** We are continuing to work with our third-party supplier to implement a fix for this issue. At present, we are awaiting their engineers to attend site and carry out the required work on their equipment to restore services. We will provide further information as it becomes available to us. Jun 28, 12:20:00 GMT+0 - Investigating - Please see update below: > **Update (28 Jun 2026 13:20hrs)** > We are continuing to work closely with a third-party supplier to resolve this issue. Due to the complexity of the network, resolution is taking longer than initially anticipated. > > We sincerely apologise for any inconvenience caused and appreciate your patience while we work to restore services. Engineers are currently on-site and actively working to resolve the issue as quickly as possible. > > We will provide further updates as soon as more information becomes available later today. Jun 28, 17:20:00 GMT+0 - Investigating - Please see update below: > **Update (28 Jun 2026 18:50hrs)** > Due to the complexity of this fault, our engineers were unable to resolve the issue today. The matter has now been escalated through the appropriate channels to bring services back online asap. > We will continue to monitor the situation closely and provide further updates as soon as new information becomes available. Jul 2, 14:17:56 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 days, 7 hours and 1 minute

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>07:17:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Westoning MK45 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>09:24:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see latest update from OFNL below: > **Update (26 Jun 2026 10:24hrs)** > An OFNL engineering team has been dispatched to site, with an estimated time of arrival of 12:00 on 26/06/2026, to carry out fault investigation. > > This issue has also been raised with our third-party provider, who are currently investigating their equipment in parallel. > > Further updates will be provided as more information becomes available..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:39:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update from OFNL below: > **Update (26 Jun 2026 13:39hrs)** > Engineering teams are currently on site investigating the fibre fault. We are also actively liaising with our third-party provider for further updates. > > Additional updates will be provided as soon as more information becomes available..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>16:17:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see latest update below: > **Update (26 Jun 2026 17:17hrs)** > Our engineers have completed testing and cannot find fault within our purview. > > We have escalated the fault to a third-party supplier and are awaiting feedback from their testing. > > Our third-party supplier is unable to provide any timeframe for a response due to the heatwave that has caused major disruption across the UK telecommunications network, which in turn is influencing response times from engineering teams. > > Further updates will be provided as more information becomes available..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>20:13:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update below: > **Update (27 Jun 2026 21:13hrs)** > The third-party supplier has arranged for an engineer to investigate the equipment outside of our network that supplies this area. > > We will continue to provide updates as soon as they become available..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>10:57:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update below: **Update (27 Jun 2026 11:57hrs)** We are continuing to work with our third-party supplier to implement a fix for this issue. At present, we are awaiting their engineers to attend site and carry out the required work on their equipment to restore services. We will provide further information as it becomes available to us..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update below: > **Update (28 Jun 2026 13:20hrs)** > We are continuing to work closely with a third-party supplier to resolve this issue. Due to the complexity of the network, resolution is taking longer than initially anticipated. > > We sincerely apologise for any inconvenience caused and appreciate your patience while we work to restore services. Engineers are currently on-site and actively working to resolve the issue as quickly as possible. > > We will provide further updates as soon as more information becomes available later today..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update below: > **Update (28 Jun 2026 18:50hrs)** > Due to the complexity of this fault, our engineers were unable to resolve the issue today. The matter has now been escalated through the appropriate channels to bring services back online asap. > We will continue to monitor the situation closely and provide further updates as soon as new information becomes available..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:17:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 26 Jun 2026 07:17:00 +0000 https://mthn.instatus.com/incident/cmqumwfeh09122onxmpejartk https://mthn.instatus.com/incident/cmqumwfeh09122onxmpejartk OFNL Incident: Barnsley S73 Type: Incident Duration: 7 days, 7 hours and 5 minutes Affected Components: OFNL Jun 25, 07:13:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Barnsley S73 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jun 25, 10:17:44 GMT+0 - Identified - Please find the latest update below: > **Update (25 Jun 2026 10:57hrs)** > Following extensive remote diagnostics, we have deployed a field engineer to carry out further on-site investigations. > > Our engineer is currently on site and continuing to investigate the issue. > > We will provide a further update once this investigation is complete and we move forward with resolving the fault. > > Thank you for your patience while we work to resolve this for you. Jun 25, 12:33:00 GMT+0 - Identified - Please see the latest update below from OFNL: > **Update (25 Jun 2026 13:33hrs)** > Our engineer has completed a comprehensive on-site investigation, and we believe the fault location has now been identified. > > Due to the nature and location of the issue, a specialist engineering team is required to carry out further investigation and complete the necessary repairs to restore service. > > We have arranged for their deployment and will provide an update as soon as we have confirmation of their arrival time. > > Thank you for your patience while we work to resolve this fault as quickly as possible. Jul 2, 14:18:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 7 days, 7 hours and 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:13:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Barnsley S73 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>10:17:44</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (25 Jun 2026 10:57hrs)** > Following extensive remote diagnostics, we have deployed a field engineer to carry out further on-site investigations. > > Our engineer is currently on site and continuing to investigate the issue. > > We will provide a further update once this investigation is complete and we move forward with resolving the fault. > > Thank you for your patience while we work to resolve this for you..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>12:33:00</var> GMT+0</small><br><strong>Identified</strong> - Please see the latest update below from OFNL: > **Update (25 Jun 2026 13:33hrs)** > Our engineer has completed a comprehensive on-site investigation, and we believe the fault location has now been identified. > > Due to the nature and location of the issue, a specialist engineering team is required to carry out further investigation and complete the necessary repairs to restore service. > > We have arranged for their deployment and will provide an update as soon as we have confirmation of their arrival time. > > Thank you for your patience while we work to resolve this fault as quickly as possible..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:18:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 25 Jun 2026 07:13:00 +0000 https://mthn.instatus.com/incident/cmqt7h1530b5g2jru1e3uy633 https://mthn.instatus.com/incident/cmqt7h1530b5g2jru1e3uy633 OFNL Incident: London E14 and E3 Type: Incident Duration: 7 days, 7 hours and 12 minutes Affected Components: OFNL Jun 25, 08:21:41 GMT+0 - Investigating - The OFNL Network have confirmed this incident is also impacting the **E3** region. Jun 25, 07:06:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > London E14, E3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jun 25, 10:18:12 GMT+0 - Identified - Please find the latest update below: > **Update (25 Jun 2026 10:45hrs)** > We now see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are working on a fix. > > We will update you again by 11:30. Jun 25, 11:18:00 GMT+0 - Monitoring - Please see the latest update below from OFNL: > **Update (25 Jun 2026 12:54hrs)** > Our Third-Party Supplier has identified heat related issues at a local Openreach Exchange, which are being worked on. > > Work to restore service was completed by our Third-Party supplier at 11:30 on 25/06/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. Jul 2, 14:18:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 7 days, 7 hours and 12 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>08:21:41</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network have confirmed this incident is also impacting the **E3** region..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:06:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > London E14, E3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>10:18:12</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (25 Jun 2026 10:45hrs)** > We now see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are working on a fix. > > We will update you again by 11:30..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>11:18:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update below from OFNL: > **Update (25 Jun 2026 12:54hrs)** > Our Third-Party Supplier has identified heat related issues at a local Openreach Exchange, which are being worked on. > > Work to restore service was completed by our Third-Party supplier at 11:30 on 25/06/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>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:18:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 25 Jun 2026 07:06:00 +0000 https://mthn.instatus.com/incident/cmqt7gcmz0q372ilnbpg9hphs https://mthn.instatus.com/incident/cmqt7gcmz0q372ilnbpg9hphs OFNL Incident: BIrningham, B4 Type: Incident Duration: 20 hours and 14 minutes Affected Components: OFNL Jun 25, 07:52:20 GMT+0 - Resolved - This incident has been resolved. Jun 24, 15:08:00 GMT+0 - Identified - Please find OFNL's latest update: > **Update (24 Jun 2026 16:08hrs)** > We’ve identified that the issue is not within our systems, but originates from one of our third-party providers. > Their team is actively working on a fix. > > We will update you again by 18:00. Jun 24, 11:38:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): * BIrningham, B4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Type: Incident

Duration: 20 hours and 14 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:52:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>15:08:00</var> GMT+0</small><br><strong>Identified</strong> - Please find OFNL's latest update: > **Update (24 Jun 2026 16:08hrs)** > We’ve identified that the issue is not within our systems, but originates from one of our third-party providers. > Their team is actively working on a fix. > > We will update you again by 18:00..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>11:38:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): * BIrningham, B4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> ]]> Wed, 24 Jun 2026 11:38:00 +0000 https://mthn.instatus.com/incident/cmqs06gq5007f2iocpwpopq5x https://mthn.instatus.com/incident/cmqs06gq5007f2iocpwpopq5x OFNL Incident: Curtis Fields DT4 Type: Incident Duration: 4 hours Affected Components: OFNL Jun 24, 12:07:00 GMT+0 - Monitoring - Please see the latest update from OFNL below: > **Update (24 Jun 2026 14:41hrs)** > Work to restore service was completed at 14:07 on 24/06/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > 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. Jun 24, 10:27:00 GMT+0 - Investigating - Please see the latest update below from OFNL: **Update (24 Jun 2026 11:27hrs)** We are continuing to investigate the problem and suspect there has been an equipment failure. An engineer is travelling to site with spare equipment. ETA 14:30. Will provide a further update by 13:30. Jun 24, 13:41:00 GMT+0 - Resolved - **Update (24 Jun 2026 14:41hrs)** This incident was closed on Wednesday, June 24th, 2026 at 14:41hrs. Jun 24, 09:41:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Curtis Fields DT4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Type: Incident

Duration: 4 hours

Affected Components:

<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>12:07:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest update from OFNL below: > **Update (24 Jun 2026 14:41hrs)** > Work to restore service was completed at 14:07 on 24/06/2026\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. > > 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>Jun <var data-var='date'> 24</var>, <var data-var='time'>10:27:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest update below from OFNL: **Update (24 Jun 2026 11:27hrs)** We are continuing to investigate the problem and suspect there has been an equipment failure. An engineer is travelling to site with spare equipment. ETA 14:30. Will provide a further update by 13:30..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>13:41:00</var> GMT+0</small><br><strong>Resolved</strong> - **Update (24 Jun 2026 14:41hrs)** This incident was closed on Wednesday, June 24th, 2026 at 14:41hrs..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>09:41:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Curtis Fields DT4 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> ]]> Wed, 24 Jun 2026 09:41:00 +0000 https://mthn.instatus.com/incident/cmqrw1lp406t62iqqkkkp8tqv https://mthn.instatus.com/incident/cmqrw1lp406t62iqqkkkp8tqv OFNL Incident: PE7, SS4 TF4 Type: Incident Duration: 3 hours and 30 minutes Affected Components: OFNL Jun 22, 08:53:38 GMT+0 - Identified - Please find the latest update below: > **Update (22 Jun 2026 09:48hrs)** > Our third-party vendor is actively working to resolve the issue from their side. We remain in close communication with them and are receiving regular updates on their progress. > > In the meantime, we will continue to monitor the situation on our end. Thank you for your patience. Jun 22, 10:30:23 GMT+0 - Resolved - This incident has been resolved. > **Update (22 Jun 2026 11:11hrs)** > Following ongoing work with our third-party vendor, services have now been restored across all sites, and we are seeing continued recovery for affected customers. > > We are continuing our investigation to determine the root cause of this incident and will closely monitor services to ensure stability. > > This incident notice will remain open while our investigation is ongoing, and we will provide further updates as required. Jun 22, 07:00:47 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Peterborough PE7, Rochford SS4, Telford TF4. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. Jun 22, 07:35:53 GMT+0 - Identified - Please find the latest update below: > **Update (22 Jun 2026 08:30hrs)** > We have identified that the issue currently resides with a third-party vendor. The matter has been escalated to their highest level of support, and we are awaiting their response. > > We are actively monitoring the situation and will provide an update as soon as we receive any meaningful information. > > Thank you for your patience while we work to resolve this incident. Type: Incident

Duration: 3 hours and 30 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>08:53:38</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (22 Jun 2026 09:48hrs)** > Our third-party vendor is actively working to resolve the issue from their side. We remain in close communication with them and are receiving regular updates on their progress. > > In the meantime, we will continue to monitor the situation on our end. Thank you for your patience..</p> <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>10:30:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. > **Update (22 Jun 2026 11:11hrs)** > Following ongoing work with our third-party vendor, services have now been restored across all sites, and we are seeing continued recovery for affected customers. > > We are continuing our investigation to determine the root cause of this incident and will closely monitor services to ensure stability. > > This incident notice will remain open while our investigation is ongoing, and we will provide further updates as required..</p> <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:00:47</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Peterborough PE7, Rochford SS4, Telford TF4. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:35:53</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (22 Jun 2026 08:30hrs)** > We have identified that the issue currently resides with a third-party vendor. The matter has been escalated to their highest level of support, and we are awaiting their response. > > We are actively monitoring the situation and will provide an update as soon as we receive any meaningful information. > > Thank you for your patience while we work to resolve this incident..</p> ]]> Mon, 22 Jun 2026 07:00:47 +0000 https://mthn.instatus.com/incident/cmqov9hat0ejk2onu8zq2p9q6 https://mthn.instatus.com/incident/cmqov9hat0ejk2onu8zq2p9q6 OFNL Incident: Bridgehill DH8 Type: Incident Duration: 7 days, 22 hours and 28 minutes Affected Components: OFNL Jun 17, 09:25:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Bridgehill DH8 **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. Jun 17, 09:33:00 GMT+0 - Identified - Please find OFNL's newest update here: > **Update (17 Jun 2026 10:33hrs)** > Following our initial investigation, we believe the issue is affecting a small number of customers due to faulty hardware. We are currently working to identify and isolate the impacted cases to prevent any wider disruption, and will then arrange replacement of the affected equipment. > > This may result in us sending an engineer to site to door knock for emergency visits for affected customers if necessary. > > We will continue to monitor the situation closely and provide further updates as soon as they become available. > > Please DO NOT reset your equipment. Jun 17, 13:56:00 GMT+0 - Identified - Please find OFNL's latest update: > **Update (17 Jun 2026 14:56hrs)** > We have observed stability across the site after identifying and isolating the issue to specific equipment. > > We will be attending the site to replace the affected equipment once access can be arranged with those customers. > > In the meantime, we will keep this incident open and continue to monitor the situation closely. > > At this stage, we do not expect any further impact. > > Thank you for your patience. Jun 25, 07:52:32 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 7 days, 22 hours and 28 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>09: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): > Bridgehill DH8 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>09:33:00</var> GMT+0</small><br><strong>Identified</strong> - Please find OFNL's newest update here: > **Update (17 Jun 2026 10:33hrs)** > Following our initial investigation, we believe the issue is affecting a small number of customers due to faulty hardware. We are currently working to identify and isolate the impacted cases to prevent any wider disruption, and will then arrange replacement of the affected equipment. > > This may result in us sending an engineer to site to door knock for emergency visits for affected customers if necessary. > > We will continue to monitor the situation closely and provide further updates as soon as they become available. > > Please DO NOT reset your equipment..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>13:56:00</var> GMT+0</small><br><strong>Identified</strong> - Please find OFNL's latest update: > **Update (17 Jun 2026 14:56hrs)** > We have observed stability across the site after identifying and isolating the issue to specific equipment. > > We will be attending the site to replace the affected equipment once access can be arranged with those customers. > > In the meantime, we will keep this incident open and continue to monitor the situation closely. > > At this stage, we do not expect any further impact. > > Thank you for your patience..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>07:52:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 17 Jun 2026 09:25:00 +0000 https://mthn.instatus.com/incident/cmqi20ocx00kj2orwg7dp78iy https://mthn.instatus.com/incident/cmqi20ocx00kj2orwg7dp78iy OFNL Incident: OX25, GRAVEN HILL Type: Incident Duration: 8 hours and 49 minutes Affected Components: OFNL Jun 16, 11:05:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > OX25, GRAVEN HILL **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. Jun 16, 14:20:42 GMT+0 - Investigating - OFNL initially stated that this was resolved at 13:00 today. However, OFNL has now resumed this incident as the network is still down for some users. Their next update will be sent by 17:00. Thank you for your patience, and on their behalf, we do apologise. Jun 16, 14:30:00 GMT+0 - Identified - Please find OFNL's latest update: > **Update (16 Jun 2026 15:30hrs)** > The site has now been restored. As this is the second outage today, engineers have been engaged to attend site and replace the affected equipment to prevent further occurrences. > We will provide a further update at 18:30. Jun 16, 19:54:00 GMT+0 - Resolved - OFNL reports that this was resolved at 20:30 on 16/06. This service, since then, should be working, though if you are still having any issues, please raise it by emailing us at Support@MTHNetworks.com. Thank you for your patience and understanding. Type: Incident

Duration: 8 hours and 49 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>11:05: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): > OX25, GRAVEN HILL **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>14:20:42</var> GMT+0</small><br><strong>Investigating</strong> - OFNL initially stated that this was resolved at 13:00 today. However, OFNL has now resumed this incident as the network is still down for some users. Their next update will be sent by 17:00. Thank you for your patience, and on their behalf, we do apologise..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Identified</strong> - Please find OFNL's latest update: > **Update (16 Jun 2026 15:30hrs)** > The site has now been restored. As this is the second outage today, engineers have been engaged to attend site and replace the affected equipment to prevent further occurrences. > We will provide a further update at 18:30..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>19:54:00</var> GMT+0</small><br><strong>Resolved</strong> - OFNL reports that this was resolved at 20:30 on 16/06. This service, since then, should be working, though if you are still having any issues, please raise it by emailing us at Support@MTHNetworks.com. Thank you for your patience and understanding..</p> ]]> Tue, 16 Jun 2026 11:05:00 +0000 https://mthn.instatus.com/incident/cmqgjkjij04hb2oro0rbrhkbb https://mthn.instatus.com/incident/cmqgjkjij04hb2oro0rbrhkbb OFNL Incident: NR14 Type: Incident Duration: 6 days, 14 hours and 45 minutes Affected Components: OFNL Jun 10, 21:18:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Loddon, NR14 **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. Jun 10, 23:13:00 GMT+0 - Identified - Please find the latest update below: > We can see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are investigating the fault. > > We will update you again by 08:00. Jun 17, 12:02:35 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 days, 14 hours and 45 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>21:18: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): > Loddon, NR14 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>23:13:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > We can see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are investigating the fault. > > We will update you again by 08:00..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>12:02:35</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 10 Jun 2026 21:18:00 +0000 https://mthn.instatus.com/incident/cmq97dtpx04mrqrk82o8st690 https://mthn.instatus.com/incident/cmq97dtpx04mrqrk82o8st690 OFNL Incident: CH5 Type: Incident Duration: 5 hours Affected Components: OFNL Jun 9, 08:18:24 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > CH5 Deeside **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. Jun 9, 13:18:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 hours

Affected Components:

<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>08:18:24</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > CH5 Deeside **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>13:18:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 9 Jun 2026 08:18:24 +0000 https://mthn.instatus.com/incident/cmq6db62z07gsp0uf5zo8y51z https://mthn.instatus.com/incident/cmq6db62z07gsp0uf5zo8y51z Freedom Fibre Incident: WA4 Type: Incident Duration: 3 hours and 15 minutes Affected Components: Freedom Fibre Jun 8, 08:53:48 GMT+0 - Identified - Please find the latest update below: > _Field engineering are currently on route back to site to carry out the cable replacement. Further updates will be provided once repairs are complete._ Jun 8, 12:08:00 GMT+0 - Resolved - This incident has been resolved. Please find FreedomFibre's message below: > _Field engineering have completed the cable replacement and respliced all 48 fibres. After post work checks, all customers are now back online. Incident resolved._ Jun 8, 08:53:10 GMT+0 - Investigating - The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > WA4 **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 15 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>08:53:48</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > _Field engineering are currently on route back to site to carry out the cable replacement. Further updates will be provided once repairs are complete._.</p> <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>12:08:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Please find FreedomFibre's message below: > _Field engineering have completed the cable replacement and respliced all 48 fibres. After post work checks, all customers are now back online. Incident resolved._.</p> <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>08:53:10</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): > WA4 **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, 8 Jun 2026 08:53:10 +0000 https://mthn.instatus.com/incident/cmq4z40w50bo7qqx1twglusg0 https://mthn.instatus.com/incident/cmq4z40w50bo7qqx1twglusg0 OFNL Incident: N1C Type: Incident Duration: 9 days, 17 hours and 36 minutes Affected Components: OFNL Jun 7, 18:27:34 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > King's Cross N1C **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. Jun 7, 18:28:01 GMT+0 - Investigating - Please find the latest update below: > **Update (07 Jun 2026 14:39hrs)** > Our engineers are unable to locate the fault. We have arranged for additional engineering resource to be on-site tomorrow morning to continue locating the fault. > > We will provide a further update tomorrow 08/06/26 at 10:00. Jun 17, 12:03:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 9 days, 17 hours and 36 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>18:27:34</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > King's Cross N1C **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>18:28:01</var> GMT+0</small><br><strong>Investigating</strong> - Please find the latest update below: > **Update (07 Jun 2026 14:39hrs)** > Our engineers are unable to locate the fault. We have arranged for additional engineering resource to be on-site tomorrow morning to continue locating the fault. > > We will provide a further update tomorrow 08/06/26 at 10:00..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>12:03:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 7 Jun 2026 18:27:34 +0000 https://mthn.instatus.com/incident/cmq446vel01jpqmsj5tztmd0s https://mthn.instatus.com/incident/cmq446vel01jpqmsj5tztmd0s OFNL Incident: Leeds LS16 Type: Incident Duration: 2 days, 11 hours and 14 minutes Affected Components: OFNL Jun 5, 07:13:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Leeds LS16. **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. Jun 5, 07:22:00 GMT+0 - Investigating - Please see latest up date from OFNL: > **Update (05 Jun 2026 08:22hrs)** > Following our initial remote checks, we have identified that this incident is currently impacting a small number of customers. > > We are now dispatching an engineer to site to investigate further and replace the identified faulty equipment, with the aim of resolving the issue for affected customers. > > Once the engineer is confirmed to be en route, we will provide a further update including the estimated time of arrival. > > Thank you for your patience. Jun 5, 13:27:00 GMT+0 - Investigating - Please see update below: > **Update (05 Jun 2026 14:27hrs)** > Engineers are continuing to work on this issue, our next update will be 16:00 Jun 7, 18:27:01 GMT+0 - Resolved - This incident has been resolved. Jun 5, 07:22:01 GMT+0 - Investigating - Please see the latest update below: **Update (05 Jun 2026 11:18hrs)** Engineers are now on site investigating the issue. Our next update will be at 13:00. Type: Incident

Duration: 2 days, 11 hours and 14 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>07:13:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Leeds LS16. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>07:22:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see latest up date from OFNL: > **Update (05 Jun 2026 08:22hrs)** > Following our initial remote checks, we have identified that this incident is currently impacting a small number of customers. > > We are now dispatching an engineer to site to investigate further and replace the identified faulty equipment, with the aim of resolving the issue for affected customers. > > Once the engineer is confirmed to be en route, we will provide a further update including the estimated time of arrival. > > Thank you for your patience..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>13:27:00</var> GMT+0</small><br><strong>Investigating</strong> - Please see update below: > **Update (05 Jun 2026 14:27hrs)** > Engineers are continuing to work on this issue, our next update will be 16:00.</p> <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>18:27:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>07:22:01</var> GMT+0</small><br><strong>Investigating</strong> - Please see the latest update below: **Update (05 Jun 2026 11:18hrs)** Engineers are now on site investigating the issue. Our next update will be at 13:00..</p> ]]> Fri, 5 Jun 2026 07:13:00 +0000 https://mthn.instatus.com/incident/cmq0lbfyk0b3sparmhoix9mh6 https://mthn.instatus.com/incident/cmq0lbfyk0b3sparmhoix9mh6 OFNL Incident: DIDCOT OX11 Type: Incident Duration: 30 minutes Affected Components: OFNL Jun 3, 11:22:00 GMT+0 - Monitoring - Please see the latest Update below: > **Update (03 Jun 2026 12:22hrs)** > This incident has been identified as relating to ongoing planned work Jun 3, 11:00:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > DIDCOT OX11 **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. Jun 3, 11:30:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:22:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please see the latest Update below: > **Update (03 Jun 2026 12:22hrs)** > This incident has been identified as relating to ongoing planned work.</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > DIDCOT OX11 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:30:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 Jun 2026 11:00:00 +0000 https://mthn.instatus.com/incident/cmpxyn62101agp3jhve5p7is4 https://mthn.instatus.com/incident/cmpxyn62101agp3jhve5p7is4 OFNL Incident: NG11 Type: Incident Duration: 21 days, 16 hours and 12 minutes Affected Components: OFNL May 29, 12:32:48 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Rushcliffe NG11 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. May 29, 18:54:00 GMT+0 - Identified - Please find the latest update below: > We have received an update from our third-party vendor confirming that their on-site engineer is currently awaiting the arrival of a required part before they can proceed with resolving the fault. > > We will provide a further update as soon as we receive more information from the vendor. > > Thank you for your patience. May 29, 21:13:00 GMT+0 - Resolved - Please find the latest update below: > We have received confirmation from our third-party vendor that the faulty equipment at the exchange has been successfully replaced, and service was restored at 21:30. > > We have also carried out further checks on our side and can confirm that all services are now operating as expected. At this time, we do not anticipate any further impact. > > Thank you for your patience while this issue was being resolved. Type: Incident

Duration: 21 days, 16 hours and 12 minutes

Affected Components:

<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>12:32:48</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Rushcliffe NG11 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>18:54:00</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > We have received an update from our third-party vendor confirming that their on-site engineer is currently awaiting the arrival of a required part before they can proceed with resolving the fault. > > We will provide a further update as soon as we receive more information from the vendor. > > Thank you for your patience..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>21:13:00</var> GMT+0</small><br><strong>Resolved</strong> - Please find the latest update below: > We have received confirmation from our third-party vendor that the faulty equipment at the exchange has been successfully replaced, and service was restored at 21:30. > > We have also carried out further checks on our side and can confirm that all services are now operating as expected. At this time, we do not anticipate any further impact. > > Thank you for your patience while this issue was being resolved..</p> ]]> Fri, 29 May 2026 12:32:48 +0000 https://mthn.instatus.com/incident/cmpqwk0ds03wjqpmqxf6zx5r5 https://mthn.instatus.com/incident/cmpqwk0ds03wjqpmqxf6zx5r5 OFNL Incident: Caldicot NP26, Magor NP26. Type: Incident Duration: 1 hour and 40 minutes Affected Components: OFNL May 27, 11:50:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Caldicot NP26, Magor NP26. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. May 27, 13:30:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 40 minutes

Affected Components:

<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>11:50:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > Caldicot NP26, Magor NP26. **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 27 May 2026 11:50:00 +0000 https://mthn.instatus.com/incident/cmpo0jq7g01fkqnk3q5oa2xck https://mthn.instatus.com/incident/cmpo0jq7g01fkqnk3q5oa2xck OFNL Incident: NN12 Type: Incident Duration: 2 days Affected Components: OFNL May 23, 09:59:32 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **NN12** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. May 23, 10:00:26 GMT+0 - Identified - Please find the latest update below: > **Update (23 May 2026 10:34hrs)** > Our engineer is on their way to site, once on site they will begin their investigation into the cause of the fault. > > We are now waiting for the engineer to arrive which should be around 11:00am. > > We will update you again by 14:00. May 23, 14:41:37 GMT+0 - Identified - Please find the latest update below: > **Update (23 May 2026 13:04hrs)** > Our engineer is currently on site; however, we have encountered access issues to our equipment. We have engaged with the relevant third-party providers to resolve this and restore access as soon as possible, allowing us to proceed with troubleshooting and work towards resolving the outage. > We will share further updates as soon as more information becomes available. May 23, 18:08:21 GMT+0 - Identified - Please find the latest update below: > **Update (23 May 2026 18:58hrs)** > We have been unable to arrange access to the equipment as the third-party engineers are currently addressing other critical issues. We will continue to liaise with them and aim to secure access early tomorrow. We will keep you updated on the progress of this fault. May 24, 11:04:19 GMT+0 - Identified - Please find the latest update below: > **Update (24 May 2026 09:30hrs)** > We are continuing to engage with the third party responsible for the current access issues to arrange a joint site visit and restore service. > We will provide a further update by 12:00. May 24, 17:27:15 GMT+0 - Identified - Please find the latest update below: > **Update (24 May 2026 14:30hrs)** > We now see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are working on a fix. > > We will update you again by18:00. May 24, 17:27:35 GMT+0 - Identified - Please find the latest update below: > **Update (24 May 2026 18:07hrs)** > The third-party provider has engaged their engineers to investigate the issue. They have identified the root cause and are currently working on a fix to restore the connection. Further updates will be shared as soon as they become available. May 25, 10:00:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days

Affected Components:

<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>09:59:32</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): > **NN12** **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>10:00:26</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (23 May 2026 10:34hrs)** > Our engineer is on their way to site, once on site they will begin their investigation into the cause of the fault. > > We are now waiting for the engineer to arrive which should be around 11:00am. > > We will update you again by 14:00..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>14:41:37</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (23 May 2026 13:04hrs)** > Our engineer is currently on site; however, we have encountered access issues to our equipment. We have engaged with the relevant third-party providers to resolve this and restore access as soon as possible, allowing us to proceed with troubleshooting and work towards resolving the outage. > We will share further updates as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>18:08:21</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (23 May 2026 18:58hrs)** > We have been unable to arrange access to the equipment as the third-party engineers are currently addressing other critical issues. We will continue to liaise with them and aim to secure access early tomorrow. We will keep you updated on the progress of this fault..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>11:04:19</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (24 May 2026 09:30hrs)** > We are continuing to engage with the third party responsible for the current access issues to arrange a joint site visit and restore service. > We will provide a further update by 12:00..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:27:15</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (24 May 2026 14:30hrs)** > We now see that the problem is not on our network, but the network of a third party that supports ours. > > We are talking to the third party, and they are working on a fix. > > We will update you again by18:00..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:27:35</var> GMT+0</small><br><strong>Identified</strong> - Please find the latest update below: > **Update (24 May 2026 18:07hrs)** > The third-party provider has engaged their engineers to investigate the issue. They have identified the root cause and are currently working on a fix to restore the connection. Further updates will be shared as soon as they become available..</p> <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 23 May 2026 09:59:32 +0000 https://mthn.instatus.com/incident/cmpi6fqfa0er3qgni045ca0sy https://mthn.instatus.com/incident/cmpi6fqfa0er3qgni045ca0sy OFNL Incident: Great Wakering SS3 Type: Incident Duration: 3 hours and 29 minutes Affected Components: OFNL May 22, 10:00:00 GMT+0 - Investigating - The OFNL Network has made us aware of an ongoing incident in the following location(s): * Great Wakering SS3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding. May 22, 10:38:00 GMT+0 - Monitoring - Please latest Update below: **Update (22 May 2026 11:38hrs)** Work to restore service was completed at 11:30 am on 22/05/26\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue. May 22, 13:29:07 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 29 minutes

Affected Components:

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The OFNL Network has made us aware of an ongoing incident in the following location(s): * Great Wakering SS3 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on their behalf for any inconvenience this may cause. We will continue to do everything within our power to get your services back up and running as soon as possible. Thank you for your understanding..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:38:00</var> GMT+0</small><br><strong>Monitoring</strong> - Please latest Update below: **Update (22 May 2026 11:38hrs)** Work to restore service was completed at 11:30 am on 22/05/26\. Customers should now find services to be working as expected. We will continue to monitor services to ensure they remain stable. Any issues being experienced after this time should be treated as individual cases and reported in the usual manner. We apologise again for the inconvenience caused and thank you for your patience throughout this issue..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>13:29:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 22 May 2026 10:00:00 +0000 https://mthn.instatus.com/incident/cmpgrv9oi03twp4naz2b3d4uv https://mthn.instatus.com/incident/cmpgrv9oi03twp4naz2b3d4uv