Is MTH Networks down?

Last checked 5m ago
Current status
MTH Networks is having a partial outage

8 active incidents: MS3 Emergency Maintenance - HU3, MS3 Emergency Maintenance - HU3 · +6 more

MTH Networks is reporting a partial outage right now (last checked 5m 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 9 incidents in the last 90 days (98.46% uptime). Get email, Slack, Discord, or webhook alerts the moment MTH Networks reports a new incident, free for 3 monitors, no credit card.

Users who monitor MTH Networks also follow these Telecom services: Optus SMS iQmetrix TPG Telecom Dubber Vimla Simbase gaiia software Helium Mobile Tuatahi First Fibre Glink View all 8,000+ providers
MTH Networks uptime 98.46% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Active incident 1

  1. Ongoing ● 6d 7h
    Started Oct 26, 2026, 11:00 AM UTC
    MS3
    Timeline · 5 updates
    • investigating · Oct 26, 2026, 11:00 AM UTC

      The MS3 Network has made us aware of an ongoing incident in the following location(s): > HU6 **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 27, 2026, 12:56 PM UTC

      This incident has been resolved.

    • identified · Oct 27, 2026, 12:57 PM UTC

      Please find the latest update below: > We have reviewed this fault, and the works required to be able to resolve this. > > We will be sending a team of engineers tomorrow to rectify this, and we expect the works to last all day. > > Apologies that we have not been able to rectify this today however this is due to the high volume of faults that came in over the weekend. > > Thank you for your continued patience and support.

    • identified · Oct 27, 2026, 03:42 PM UTC

      Please find the latest update below: > Dear Customer, > > Following our previous update, we would like to apologise as we require some additional time to prepare for the works needed to resolve this fault. > > Unfortunately, we will have to reattend tomorrow to carry out the necessary repairs. We understand the inconvenience this delay may cause and sincerely apologise for having to extend these works. > > Thank you for your continued patience and understanding while we work to resolve this issue as quickly as possible. > > Kind regards, > MS3

    • identified · Oct 29, 2026, 09:45 AM UTC

      Please find the update below: > Hi Team, > > Our engineers have attended today and attempted to complete the works, however, we need to complete a little more investigation into the issue and cause. > > Because of this, we were unable to resolve the fault today. Apologies for any inconvenience caused to you and your customers. > > Rest assured we are treating this as a priority and will be assessing it first thing in the morning. > > We shall keep you updated as to the progress.

    Latest: Please find the update below: > Hi Team, > > Our engineers have attended today and attempted to complete the works, however, we need to complete a little more investigation into th…

Recent outages & incidents

Past 90 days
  1. Resolved 23h 40m
    Started Oct 29, 2026, 01:46 PM UTC · Resolved Oct 30, 2026, 01:27 PM UTC
    Freedom Fibre
    Timeline · 5 updates
    • 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.

    • 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._

    • 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._

    • 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._

    • 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.._

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

  2. Resolved 5d 2h
    Started Oct 22, 2026, 10:51 AM UTC · Resolved Oct 27, 2026, 01:21 PM UTC
    OFNL
    Timeline · 5 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.

    • identified · Oct 27, 2026, 01:21 PM UTC

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

    • resolved · Oct 27, 2026, 01:21 PM UTC

      We implemented a fix and are currently monitoring the result.

    Latest: We implemented a fix and are currently monitoring the result.

  3. Resolved 6h 34m
    Started Oct 22, 2026, 07:40 AM UTC · Resolved Oct 22, 2026, 02:15 PM UTC
    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…

  4. Resolved 1h 14m
    Started Oct 18, 2026, 09:30 AM UTC · Resolved Oct 18, 2026, 10:44 AM UTC
    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.

  5. Resolved 18m
    Started Oct 14, 2026, 05:00 PM UTC · Resolved Oct 14, 2026, 05:18 PM UTC
    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…

See the full MTH Networks outage history

4 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 minutes
9incidents recorded
9last 12 months
9last 90 days
3 daystypical duration, 12 months

The longest incident in the last year, OFNL Incident: Newton Abbot, TQ12, TQ13. on October 14, 2026, ran for 13 days. 96 maintenance windows announced in the same period.

Most affected components, last 12 months

  • OFNL7
  • Freedom Fibre1
  • MS31

Latest incidents

  • Freedom Fibre Incident: M44 October 29, 2026 · 24 hours · degraded service

    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…

  • MS3 Incident: HU6 October 26, 2026 · still open · major outage

    The MS3 Network has made us aware of an ongoing incident in the following location(s): > HU6 **PLEASE DO NOT RESET YOUR NETWORK EQUIPMENT!** We apologise on…

  • OFNL Incident: Peterborough, PE7 October 22, 2026 · 5 days · degraded service

    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…

Outage history

Past 90 days · 9 incidents View full outage history →