Is MTH Networks down?
Last checked 6m ago7 active incidents: OFNL Incident: Peterborough, PE7, OFNL Incident: Newton Abbot, TQ12, TQ13. · +5 more
MTH Networks is reporting a partial outage right now (last checked 6m ago). Some components are affected; others remain operational.
Real-time MTH Networks status, recent outages, and incident history: pulled directly from MTH Networks's official status page at mthn.instatus.com every 5 minutes. Pingoru tracks 9 MTH Networks services and has captured 34 incidents in the last 90 days (99.14% uptime). Get email, Slack, Discord, or webhook alerts the moment MTH Networks reports a new incident, free for 3 monitors, no credit card.
Active incidents 2
- OFNL
Timeline · 3 updates
- 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.
- 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.
- 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.
Latest: 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…
-
- OFNL
Timeline · 4 updates
- 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.
- 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
- 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.
- 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.
Latest: 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 natu…
-
Recent outages & incidents
Past 90 days- OFNL
Timeline · 3 updates
- 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.
- 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.
- 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.
Latest: 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 w…
-
- OFNL
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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.
Latest: **Update (18 Oct 2026 11:44hrs)** This incident was closed on Sunday, October 18th, 2026 at 11:44hrs.
-
- OFNL
Timeline · 2 updates
- 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.
- 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.
Latest: 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 w…
-
- OFNL
Timeline · 2 updates
- 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.
- resolved · Oct 12, 2026, 08:00 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- OFNL
Timeline · 3 updates
- 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.
- 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.
- resolved · Oct 08, 2026, 01:56 PM UTC
We implemented a fix and are currently monitoring the result.
Latest: We implemented a fix and are currently monitoring the result.
-
See the full MTH Networks outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse MTH Networks outage history →Or sign up free to get alerts when MTH Networks breaks · 10 free monitors · No credit card
Incident record
Since October 2026 · Instatus · 9 components checked every 5 minutesThe longest incident in the last year, OFNL Incident: Loddon NR14 on October 11, 2026, ran for 20 hours. 51 maintenance windows announced in the same period.
Most affected components, last 12 months
- OFNL7
Latest incidents
- OFNL Incident: Peterborough, PE7
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…
- OFNL Incident: Sunderland SR3
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…
- OFNL Incident: Halstead CO9
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…
- OFNL Incident: Peterborough, PE7 OngoingStarted Oct 22, 2026, 10:51 AM UTC · ● 12h 24m
- OFNL Incident: Sunderland SR3 ResolvedStarted Oct 22, 2026, 07:40 AM UTC · Resolved Oct 22, 2026, 02:15 PM UTC · 6h 34m
- OFNL Incident: Halstead CO9 ResolvedStarted Oct 18, 2026, 09:30 AM UTC · Resolved Oct 18, 2026, 10:44 AM UTC · 1h 14m
- OFNL Incident: NR29, NR30 ResolvedStarted Oct 14, 2026, 05:00 PM UTC · Resolved Oct 14, 2026, 05:18 PM UTC · 18m
- Started Oct 14, 2026, 08:18 AM UTC · ● 8d 14h
- OFNL Incident: Loddon NR14 ResolvedStarted Oct 11, 2026, 11:34 AM UTC · Resolved Oct 12, 2026, 08:00 AM UTC · 20h 25m
- OFNL Incident: HG5 Harrogate ResolvedStarted Oct 08, 2026, 08:00 AM UTC · Resolved Oct 08, 2026, 01:56 PM UTC · 5h 55m