1310.io Outage History

Started Oct 21, 2026, 04:26 PM UTC· resolved Oct 22, 2026, 04:05 PM UTC

1. investigating Oct 21, 2026, 04:26 PM UTC

   There are some critical severity vulnerabilities which have been released into the wild. These affect all PHP versions, including those used by our control panel. We have taken the difficult decision to take our control panel offline for public access until a patched release has been made. Our team can still receive emails via [email protected] or on the phone at 0333 300 1310. We have access to the platform and all systems should continue to operate normally. To be clear: The system has not been compromised, we are taking this approach to protect your and our data.

2. resolved Oct 22, 2026, 04:05 PM UTC

   We have deployed new versions of PHP and mitigations to our control panel, it is fully open for service again.

Read the full incident report →

Started Oct 20, 2026, 10:02 AM UTC· resolved Oct 21, 2026, 03:16 PM UTC

1. investigating Oct 20, 2026, 10:02 AM UTC

   Some customers connected to our Overton POP are currently experiencing a loss of service. Engineers are investigating to identify thge router cause. Updates to follow in the next hour.

2. monitoring Oct 20, 2026, 10:22 AM UTC

   The engineers have completed their investigation restored connectivity and are monitoring for stability. This incident is now pending closure one stability is confirmed.

3. resolved Oct 21, 2026, 03:16 PM UTC

   Following a period of monitoring, this incident is now being closed.

Read the full incident report →

Started Oct 20, 2026, 04:52 AM UTC· resolved Oct 20, 2026, 08:14 AM UTC

1. investigating Oct 20, 2026, 02:00 AM UTC

   Our engineers are aware of an ongoing outage from one of our national carrier links. They have initiated third party resources to investigate We apologise for the inconvenience this is causing and will issue another update at 07:00 when we and they have had time to investigate the issue.

2. investigating Oct 20, 2026, 06:52 AM UTC

   We have identified the issue and we are waiting on third party engineers to attend site. This appears linked to maintenance activity on third party equipment last night which should not have affected our services. We will update this message as soon as we have further information

3. investigating Oct 20, 2026, 07:39 AM UTC

   Engineers are on site and investigating the issue - An update will be posted around 09:00

4. resolved Oct 20, 2026, 08:14 AM UTC

   Engineers identified cable damage in the rack at Telehouse North after maintenance was completed by another provider last night (unrelated to 1310). The cable has been swapped and the services are back online. Our apologies for this outage

Read the full incident report →

Started Oct 01, 2026, 08:32 AM UTC· resolved Oct 06, 2026, 01:03 PM UTC

1. investigating Oct 01, 2026, 08:32 AM UTC

   1310 are aware of an issue causing loss of service to a number of customers our connected to our Overton POP. Engineers are actively investigating. Updates to follow by 11:00 or upon receipt of further information.

2. investigating Oct 01, 2026, 08:56 AM UTC

   Senior engineers have activated a failover to a backup and are seeing restoration of service. Services may observe slow performance. Investigations are underway on the primary link and 1310 will provide an update once these investigations have been completed. Updates to follow by 11:00 or upon receipt of further information.

3. investigating Oct 01, 2026, 09:35 AM UTC

   The senior engineers have completed their investigations and identified the issue with the circuit to be with Openreach. Openreach are actively investigating and looking to restore service as soon as possible. Unfortunately, no ERT has yet been provided by Openreach. Updates to follow within 4 hours or upon receipt of further information.

4. investigating Oct 01, 2026, 01:10 PM UTC

   Openreach have confirmed that the incident effect the primary link estimated to be resolved by 17:00. Customer services are expected to automatically fail back over upon restoration of the primary link. As such, the next update will follow by COB.

5. investigating Oct 01, 2026, 04:29 PM UTC

   The primary service remains offline. Openreach have not yet provided a new ERT. As such, updates will follow in the morning.

6. investigating Oct 02, 2026, 11:00 AM UTC

   The primary service remains offline. Openreach have updated with a new ERT of 17:00 today. Further updates will be provided by COB.

7. monitoring Oct 02, 2026, 03:52 PM UTC

   We are pleased to report restoration of the primary link. We are monitoring for stability but are not currently seeing any issues. This incident will be closed after a period of stability on the primary link.

8. resolved Oct 06, 2026, 01:03 PM UTC

   After an extended period monitoring, 1310 are satisfied that the primary link is stable and we are seeing traffic flow as expected. A full RFO will be available on request.

Read the full incident report →

Started Sep 10, 2026, 02:45 AM UTC· resolved Sep 11, 2026, 08:18 AM UTC

1. investigating Sep 10, 2026, 03:20 AM UTC

   We are investigating with our NOC team

2. investigating Sep 10, 2026, 03:33 AM UTC

   Our engineers have restored connectivity. A review of this incident will occur in the coming day(s) and an update will be provided to this ticket with an outcome. We do not anticipate further event(s) however if they do occur they will also be posted to this ticket.

3. investigating Sep 10, 2026, 08:34 AM UTC

   We’re aware some customers on certain suppliers may still have no service. We are investigating this urgently.

4. investigating Sep 10, 2026, 09:27 AM UTC

   Engineers have found the routing issue in the network core affecting customers on some suppliers. The team are working on a fix.

5. investigating Sep 10, 2026, 12:25 PM UTC

   Our engineers continue to work on the affected services and are seeing restoration of some services. They are continuing to investigate and hope to restore more services shortly.

6. monitoring Sep 10, 2026, 01:16 PM UTC

   The senior engineers believe to the issue to now be resolved and are seeing restoration of the final services. We are monitoring to see if there are any further issues but believe this particular issue to be fixed and to not r-occur moving forward. A full RFO will be available upon request.

7. resolved Sep 11, 2026, 08:18 AM UTC

   This issue has been resolved.

Read the full incident report →

Started Jul 29, 2026, 08:21 AM UTC· resolved Jul 30, 2026, 08:08 AM UTC

1. investigating Jul 29, 2026, 08:21 AM UTC

   Senior engineers are investigating an issue affecting services connected to out Langley POP. Updates to follow upon completion of initial investigations.

2. investigating Jul 29, 2026, 08:32 AM UTC

   Our senior engineers have investigated and identified that the issue appears to be in our wholesale supplier’s part of the network. We have engaged with wholesale supplier and can confirm that they are actively investigating a card failure. Unfortunately, no estimated resolution time has been provided as of yet. Updates to follow within an hour or upon receipt of further information.

3. investigating Jul 29, 2026, 09:20 AM UTC

   Our wholesale provider have escalated to their Tier 3 who have been unable to recover the card remotely. The NOC have engaged with their vendor for further investigations. Updates to follow within the hour or upon receipt of further information.

4. investigating Jul 29, 2026, 10:14 AM UTC

   Our wholesale provider’s have engaged with their 3rd party provider for the card and are currently on a conference call providing node logs and further detail(s) for investigation. Updates to follow in an hour or upon receipt of further information.

5. investigating Jul 29, 2026, 11:00 AM UTC

   Our wholesale provider’s NOC have concluded the conference call with their thrid party vendor. The vendor will now raise PR and FE requests to attend. ETA TBC.

6. investigating Jul 29, 2026, 12:04 PM UTC

   The NOC at our wholesale provider have continued to chase the vendor for an update on the ETA for parts and a filed engineer to site. ETA to site today is 13:30. Updates to follow in an hour or upon receipt of further information.

7. investigating Jul 29, 2026, 12:58 PM UTC

   We are currently awaiting confirmation of arrival of the wholesale vendor’s 3rd party engineers on site. Updates to follow in an hour or upon receipt of further information.

8. investigating Jul 29, 2026, 01:59 PM UTC

   Due unforeseen circumstances, the 3rd party engineers have been delayed. The new ETA on site is 15:30. Updates to follow in an hour or upon receipt of further information.

9. investigating Jul 29, 2026, 03:00 PM UTC

   The engineers have arrived on site and attempted to re-seat the effected card but unfortunately this has not restored service. The parts are still scheduled to arrive but at this point there is no ETA for their arrival. Updates to follow in an hour or upon receipt of further information.

10. investigating Jul 29, 2026, 04:00 PM UTC

    The engineer is onsite and currently liaising with remote support to carry out the card replacement. We are now transitioning to our out of hours support service. The next update will be posted around 19:00.

11. resolved Jul 30, 2026, 08:08 AM UTC

    The card was replaced yesterday evening, and verified to be working. Services recovered around 19:00 and have been stable. If you are continuing to experience issues, please let our support team know via [email protected] or 0333 300 1310

Read the full incident report →

Started Jul 05, 2026, 03:47 PM UTC· resolved Jul 06, 2026, 11:23 AM UTC

1. investigating Jul 05, 2026, 03:47 PM UTC

   We are aware of an ongoing incident - our monitoring has detected reachability issues for portions of the internet. Our team is investigating now.

2. investigating Jul 05, 2026, 04:05 PM UTC

   Our team have investigated and we are seeing recovery across the network - Apologies for the inconvenience this has caused for the past 30 minutes. We will continue to investigate and provide further details. Our team are monitoring the network for further issues, everything should be restored now.

3. resolved Jul 06, 2026, 11:23 AM UTC

   This incident is resolved, network is stable. A root cause analysis will come out in due course

Read the full incident report →

Started Jun 24, 2026, 02:43 PM UTC· resolved Jun 25, 2026, 10:22 AM UTC

1. investigating Jun 24, 2026, 02:43 PM UTC

   We have been alerted to an issue at the Slades POP causing a total loss of service, affecting all customers on the HiWiFi platform. This is currently under investigation by senior engineers. Updates to follow upon completion of initial investigations.

2. investigating Jun 24, 2026, 03:56 PM UTC

   After initial diagnostics, 1310 need to deploy an engineer to investigate this further, on site. As such, we expect to have an engineer on site by 10AM 25/06/2026. Updates to follow once our initial on site checks have been completed.

3. investigating Jun 25, 2026, 07:36 AM UTC

   Our engineer has arrived on site. Services will be disrupted will testing is performed.

4. investigating Jun 25, 2026, 08:57 AM UTC

   Engineers have identified a possible cause and are implementing a solution. Due to the rising temperatures, this is going to take longer than normal to ensure that the engineers health and safety is maintained. Apologies for the ongoing issue, we aim to have you restored by mid day. The next update will be at 12:00 or earlier if the issue is resolved.

5. resolved Jun 25, 2026, 10:22 AM UTC

   The engineers have resolved the issue and have left the area. All services are confirmed online and working. If you are continuing to experience issues, please let our support team know via [email protected] or 0333 300 1310

Read the full incident report →

Started Jun 17, 2026, 08:45 AM UTC· resolved Jun 18, 2026, 02:14 PM UTC

1. investigating Jun 17, 2026, 08:50 AM UTC

   Our monitoring has alerted that the core switch has crashed and rebooted in Telehouse North. We are investigating, the network will route around the problem but instability may be experienced for a short while. Our apologies for the inconvenience this has caused.

2. investigating Jun 17, 2026, 08:58 AM UTC

   The switch has been stable for 10 minutes. We are going to continue to monitor, we will also be bringing forward the maintenance work for it’s replacement.

3. resolved Jun 18, 2026, 02:14 PM UTC

   This issue has been resolved. We are waiting on confirmation of the new date to replace the hardware.

Read the full incident report →

Started Jun 04, 2026, 07:16 AM UTC· resolved Jun 04, 2026, 08:15 AM UTC

1. investigating Jun 04, 2026, 07:16 AM UTC

   We are aware of the issue and our NOC is investigating. Next update 08:45

2. investigating Jun 04, 2026, 07:23 AM UTC

   The NOC engineers have identified the issue on a network device and are implementing a fix. They expect this to be resolved shortly.

3. investigating Jun 04, 2026, 07:30 AM UTC

   The fix has been implemented and services are returning

4. resolved Jun 04, 2026, 08:15 AM UTC

   The issue has been resolved and services are looking stable. Please contact [email protected] / 0333 300 1310 if you have continue to have any issues.

Read the full incident report →

Started May 30, 2026, 08:07 AM UTC· resolved Jun 23, 2026, 02:15 PM UTC

1. investigating May 30, 2026, 08:07 AM UTC

   We are aware of total service outage at the above locations, engineer are investigating with our connectivity supplier and we will update at 10:30.

2. investigating May 30, 2026, 08:48 AM UTC

   The UPS has failed overnight at the cabinet. We are bypassing that and services will be up on utility power only. This means if there is a power cut, the services will drop again. We will perform maintenance next week to 10 days to replace the UPS, which will be published once dates are confirmed.

3. monitoring May 30, 2026, 09:10 AM UTC

   The UPS has been bypassed and all services are showing as online. We will continue to monitor for any further issues, and plan for maintenance works to replace the UPS.

4. resolved Jun 23, 2026, 02:15 PM UTC

   Resolved

Read the full incident report →

Started May 22, 2026, 12:52 PM UTC· resolved May 22, 2026, 06:10 PM UTC

1. investigating May 22, 2026, 12:52 PM UTC

   We are seeing a network outage at Pittleworth - Our team are actively investigating the fault

2. investigating May 22, 2026, 02:32 PM UTC

   Our engineers are en route to the location to investigate the outage. Their expected ETA is 16:30 Once on site, they will begin diagnosis of the problem and report back. Next update, 17:00

3. investigating May 22, 2026, 04:39 PM UTC

   We’re currently experiencing an outage affecting services in Pittleworth. Initial investigations indicate damage to fibre optic cabling caused by rodents. Our engineers are on site assessing the full extent of the damage and preparing a repair plan. At this stage, we do not yet have an estimated time for restoration, however work is actively underway and we will continue to provide updates as more information becomes available. We apologise for the disruption and appreciate your patience while we work to restore service.

4. resolved May 22, 2026, 06:10 PM UTC

   We have replaced the faulty cable in the cabinet and all customers are back online as of 17:35. We have checked all customer sessions and all seem to be working correctly. If your issue is not resolved, please reboot your router by turning the power off for up to 10 minutes and turning it back on. We will continue to monitor the site closely for the next 24 hours and work to implement rodent mitigation in the near future. We will issue a maintenance notification for when this works takes place. Apologies for any inconvenience our friends caused 🐭

Read the full incident report →

Started Apr 14, 2026, 08:10 AM UTC· resolved Apr 14, 2026, 05:31 PM UTC

1. investigating Apr 14, 2026, 08:32 AM UTC

   We are aware from our monitoring that Langley is reporting as down. We have investigations ongoing, local power to our equipment is online and we are raising a fault with our connection provider. We are sorry for the inconvenience this is causing, we will update shortly.

2. investigating Apr 14, 2026, 09:14 AM UTC

   Our engineers have identified the fault being with a provider which connects from our network in Langley and Bearley back to the rest of our network for internet access. A fault has been raised with them and they are investigating, As soon as we have an update and return to service estimate we will advise. We are sorry once again on behalf of our supplier for the inconvenience this is causing.

3. investigating Apr 14, 2026, 02:09 PM UTC

   We had an update from our supplier and they are sending engineers to investigate. We do not currently have an ETA for service restoration. As soon as we have an update or ETA for service resolution we will be in touch. Apologies for the ongoing service disruption.

4. resolved Apr 14, 2026, 05:31 PM UTC

   This issue was resolved approximately 16:20 this afternoon by our upstream provider. We have requested a Reason For Outage (RFO) and we will provide this when it is available (up to 10 days). Our apologies for the issue again, we will look into options to prevent reoccurrence.

Read the full incident report →

Started Apr 08, 2026, 05:09 AM UTC· resolved Apr 10, 2026, 02:15 PM UTC

1. investigating Apr 08, 2026, 05:09 AM UTC

   OFNL have been doing maintenance on their network overnight. It was due to finish at 06:00. Following the maintenance window and bringing back online our monitoring of their hardware we see that our connection to them Is currently down. We are raising with the OFNL network operations team and hope to have an update shortly. Please do not reboot your router.

2. monitoring Apr 08, 2026, 05:43 AM UTC

   The port has been up and stable since 06:15. Your internet should be online and working, I fit is not, please do not reset your router and let our team know via [email protected] or on 0333 300 1310. Apologies for the inconvenience OFNLs overrunning maintenance has caused.

3. resolved Apr 10, 2026, 02:15 PM UTC

   Outage has been resolved.

Read the full incident report →

Started Mar 28, 2026, 11:04 AM UTC· resolved Mar 29, 2026, 06:58 AM UTC

1. investigating Mar 28, 2026, 11:04 AM UTC

   We are aware of a fibre service break between two service locations in the area of Nine Mile Water. Our engineers are investigating and once the cause is known we will update this incident. Please do not reset your router.

2. resolved Mar 29, 2026, 06:58 AM UTC

   Power to the cabinet had been lost in the early hours. Service restored at 12:30 on 28/3/26.

Read the full incident report →

Started Mar 26, 2026, 07:10 PM UTC· resolved Mar 28, 2026, 11:03 AM UTC

1. investigating Mar 26, 2026, 07:10 PM UTC

   Linked to ongoing maintenance we are seeing authentication failures for Internet services. Our team are investigating as a priority over the maintenance and aim to restore services shortly.

2. resolved Mar 28, 2026, 11:03 AM UTC

   This incident was resolved at 01:00 on the 27th March. We apologise the the inconvenience caused during this period of works.

Read the full incident report →

Started Feb 13, 2026, 09:04 AM UTC· resolved Feb 16, 2026, 11:32 AM UTC

1. monitoring Feb 13, 2026, 09:00 AM UTC

   The BGP router in Telehouse North crashed at 08:51 this morning causing network service interruption for approximately 5 minutes whilst the routes reconverged and the router rebooted itself. The last lines on the log file prior to it rebooting itself; Feb 13 08:51:24 ro2.thn netplugd[11297]: eth13: state ACTIVE flags 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 -> 0x00001003 UP,BROADCAST,MULTICAST Feb 13 08:51:24 ro2.thn netplugd[3534490]: /etc/netplug/netplug eth13 out -> pid 3534490 Feb 13 08:51:25 ro2.thn netplugd[11297]: eth13.3000: state ACTIVE flags 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 -> 0x00001003 UP,BROADCAST,MULTICAST Feb 13 08:51:25 ro2.thn netplugd[3534495]: /etc/netplug/netplug eth13.3000 out -> pid 3534495 Feb 13 08:51:25 ro2.thn netplugd[11297]: eth13: state OUTING flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Feb 13 08:51:25 ro2.thn netplugd[11297]: eth13.3000: state OUTING flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Feb 13 08:51:28 ro2.thn bgpd[2060]: [PXVXG-TFNNT] %ADJCHANGE: neighbor 95.131.87.159(ro2.thw) in vrf default Down BGP Notification send Feb 13 08:51:28 ro2.thn bgpd[2060]: [HKQ2F-8D0MY][EC 100663315] Thread Starvation: {(thread *)0x7f75f87a9fd0 arg=0x55df8cae5140 timer r=-11.352 update_group_refresh_default_originate_route_map() &bgp->t_rmap_def_originate_eval from ../bgpd/bgp_route.c:3438} was scheduled to pop greater than 4s ago Feb 13 08:51:30 ro2.thn netplugd[11297]: eth13: state OUTING flags 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 -> 0x00001003 UP,BROADCAST,MULTICAST Feb 13 08:51:30 ro2.thn netplugd[11297]: eth13.3000: state OUTING flags 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 -> 0x00001003 UP,BROADCAST,MULTICAST Feb 13 08:51:30 ro2.thn netplugd[11297]: eth13: state OUTING flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 Feb 13 08:51:30 ro2.thn netplugd[11297]: eth13.3000: state OUTING flags 0x00001003 UP,BROADCAST,MULTICAST -> 0x00011043 UP,BROADCAST,RUNNING,MULTICAST,10000 We are investigating the cause of these events and will continue to monitor the network for stability. For the past 10 minute period there have been no further issues.

2. resolved Feb 16, 2026, 11:32 AM UTC

   Issue has not returned - Router to be monitored for repeat issues. Router is part of network upgrade path in 2026 so will be replaced in due course.

Read the full incident report →