MTH Networks Outage History

Started Oct 29, 2026, 01:46 PM UTC· resolved Oct 30, 2026, 01:27 PM UTC

1. investigating Oct 29, 2026, 01:46 PM UTC

   The Freedom Fibre Network has made us aware of an ongoing incident in the following location(s): > M44 **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.

2. investigating Oct 29, 2026, 03:03 PM UTC

   Please find the latest update below: > _Our NOC have confirmed that traffic on OLTs 2, 3, 4, and 5 have switched to AGN, however services on olt.5mrirl are currently not passing traffic as per the reports. This is currently being investigated further by Network Engineering._

3. investigating Oct 29, 2026, 03:55 PM UTC

   Please find the latest update below: > _Our NOC have confirmed that traffic on OLTs 2, 3, 4, and 5 have switched to AGN, however services on olt.5mrirl are currently not passing traffic as per the reports. This is currently being investigated further by Network Engineering._

4. identified Oct 30, 2026, 10:27 AM UTC

   Please find the latest update below: > _Our Network Engineering team have reverted traffic back onto AGN1 and we can see traffic across the link, should any customers remain down, please complete full CPE checks and raise to Service Ops via a Service Requests for any individual services experiencing any further issues._

5. resolved Oct 30, 2026, 01:27 PM UTC

   Please find the latest update below: > _Traffic on olt5.mrirl has been re-routed back onto AGN1 and no further issues reported.._

Read the full incident report →

Started Oct 22, 2026, 10:51 AM UTC· resolved Oct 27, 2026, 01:21 PM UTC

1. investigating Oct 22, 2026, 10:51 AM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): * Peterborough, PE7 **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.

2. investigating Oct 22, 2026, 10:52 AM UTC

   Please see the latest update from OFNL below: > **Update (22 Oct 2026 11:52hrs)** > We have an engineer on route to try and identify and resolve the fault. > > We apologise for any inconvenience caused.

3. investigating Oct 22, 2026, 02:25 PM UTC

   Please find the latest update below: > **Update (22 Oct 2026 13:09hrs)** > Our engineer has now arrived on site and has begun the investigation. > > We will provide further updates as soon as additional information becomes available from site.

4. identified Oct 27, 2026, 01:21 PM UTC

   Please find the latest update below: This incident has been resolved.

5. resolved Oct 27, 2026, 01:21 PM UTC

   We implemented a fix and are currently monitoring the result.

Read the full incident report →

Started Oct 22, 2026, 07:40 AM UTC· resolved Oct 22, 2026, 02:15 PM UTC

1. investigating Oct 22, 2026, 07:40 AM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): Sunderland SR3 **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.

2. identified Oct 22, 2026, 10:50 AM UTC

   Please find the latest update below: > **Update (22 Oct 2026 11:31hrs)** > Services were restored at 09:03 and have been stable since. However engineers remain at the location of the fault performing further works, and while we do not anticipate further impact to services, they are at risk until further notice. > > We will update you again when we know all works are complete.

3. resolved Oct 22, 2026, 02:15 PM UTC

   Please find the latest update below: > **Update (22 Oct 2026 13:23hrs)** > Work to restore service was completed at 09:03 on 22/10/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.

Read the full incident report →

Started Oct 18, 2026, 09:30 AM UTC· resolved Oct 18, 2026, 10:44 AM UTC

1. investigating Oct 18, 2026, 09:30 AM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): > **Halstead CO9** **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.

2. identified Oct 18, 2026, 10:26 AM UTC

   **Update (18 Oct 2026 11:26hrs)** As our investigation has progressed, we have identified that this issue is impacting the entire customer base at this site. Our engineers are continuing to investigate and work towards identifying the root cause while restoring affected services as quickly as possible. Thank you for your patience and understanding.

3. identified Oct 18, 2026, 10:44 AM UTC

   **Update (18 Oct 2026 11:44hrs)** We have now identified the root cause of the incident, which was related to equipment located on site. The affected equipment has been remotely rebooted, and since completing this action we have seen customer services begin to restore across the site. Based on our observations, we are confident that the issue has now been resolved. We will continue to closely monitor both customer services and the site equipment to ensure stability and confirm there is no recurrence of the issue.

4. resolved Oct 18, 2026, 10:44 AM UTC

   **Update (18 Oct 2026 11:44hrs)** This incident was closed on Sunday, October 18th, 2026 at 11:44hrs.

Read the full incident report →

Started Oct 14, 2026, 05:00 PM UTC· resolved Oct 14, 2026, 05:18 PM UTC

1. investigating Oct 14, 2026, 05:00 PM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): > Caister NR29, NR30 **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.

2. resolved Oct 14, 2026, 05:18 PM UTC

   Please find the latest update below: > Engineers monitoring this incident have seen no further drops for an hour. 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.

Read the full incident report →

Started Oct 14, 2026, 08:18 AM UTC· resolved Oct 27, 2026, 01:22 PM UTC

1. investigating Oct 14, 2026, 08:18 AM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): * Newton Abbot, TQ12, TQ13. **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.

2. investigating Oct 14, 2026, 11:33 AM UTC

   Please see the latest update from OFNL: > **Update (14 Oct 2026 12:33hrs)** > Our engineer has arrived onsite and is starting investigation now. > > We will aim to provide further updates as we get more developments from site

3. identified Oct 15, 2026, 06:59 AM UTC

   Please find the latest update below: > Our engineers are returning to site this morning to continue with fibre repairs. > > It is expected that the fibre repair work will take a significant amount of time. > > We will provide an update as soon as there is significant news on the progress of the repairs.

4. identified Oct 15, 2026, 09:46 AM UTC

   We implemented a fix and are currently monitoring the result. > Our engineers have now located the damaged section of fibre and repair work is underway. > > Due to the complex nature of the damage, the repair process is expected to be extensive and restoration of services may take several hours to complete. Our teams will continue to work on the fault as quickly and safely as possible to restore Internet and Phone services to affected customers. > > We apologise for the ongoing disruption and thank customers for their patience while repairs are carried out. > > A further update will be provided as soon as there is significant progress to report.

5. resolved Oct 27, 2026, 01:22 PM UTC

   We implemented a fix and are currently monitoring the result.

Read the full incident report →

Started Oct 11, 2026, 11:34 AM UTC· resolved Oct 12, 2026, 08:00 AM UTC

1. identified Oct 11, 2026, 11:34 AM UTC

   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.

2. resolved Oct 12, 2026, 08:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 08, 2026, 08:00 AM UTC· resolved Oct 08, 2026, 01:56 PM UTC

1. investigating Oct 08, 2026, 08:00 AM UTC

   The OFNL Network has made us aware of an ongoing incident in the following location(s): * HG5 Harrogate **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.

2. identified Oct 08, 2026, 01:46 PM UTC

   Please see the latest update below: > **Update (08 Oct 2026 14:56hrs)** > Following engineer attendance on site, the root cause of the issue was identified and has now been successfully resolved. We have observed all affected customer services restoring and, following continued monitoring, we are confident that the issue has been fully resolved.

3. resolved Oct 08, 2026, 01:56 PM UTC

   We implemented a fix and are currently monitoring the result.

Read the full incident report →