1310.io Outage History

1310.io is up right now

There were 6 1310.io outages since February 13, 2026 totaling 205h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.1310.io

Minor April 14, 2026

Langley - Service Outage

Detected by Pingoru
Apr 14, 2026, 08:10 AM UTC
Resolved
Apr 14, 2026, 05:31 PM UTC
Duration
9h 21m
Affected: POPsLangley
Timeline · 4 updates
  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 →

Major April 8, 2026

Outage post OFNL works

Detected by Pingoru
Apr 08, 2026, 05:09 AM UTC
Resolved
Apr 10, 2026, 02:15 PM UTC
Duration
2d 9h
Affected: Nationwide OFNL
Timeline · 3 updates
  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 →

Minor March 28, 2026

Fibre Service Damage - Nine Mile Water

Detected by Pingoru
Mar 28, 2026, 11:04 AM UTC
Resolved
Mar 29, 2026, 06:58 AM UTC
Duration
19h 53m
Affected: POPsNine Mile Water
Timeline · 2 updates
  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 →

Major March 26, 2026

RADIUS authentication failing - no internet

Detected by Pingoru
Mar 26, 2026, 07:10 PM UTC
Resolved
Mar 28, 2026, 11:03 AM UTC
Duration
1d 15h
Affected: Nationwide City FibrePOPsBasingstokeMonk Sherborne
Timeline · 2 updates
  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 →

Minor February 27, 2026

Switch Reboot - Telehouse North

Detected by Pingoru
Feb 27, 2026, 10:57 AM UTC
Resolved
Feb 27, 2026, 03:29 PM UTC
Duration
4h 31m
Affected: Network CoreNationwide City FibreNationwide EthernetNationwide FTTxNationwide OFNLPOPsBasingstokeFarnboroughLangleyRothwellNine Mile WaterOvertonTelephony (VoIP)Telephony - ResidentialTelephony - Enterprise
Timeline · 4 updates
  1. investigating Feb 27, 2026, 10:57 AM UTC

    Our monitoring system has notified us of an unexpected switch reboot in the Telehouse North campus - Services have currently restored after a brief outage and we are investigating the root cause. It is not expected that this event will repeat itself within a short time window at this time.

  2. investigating Feb 27, 2026, 11:25 AM UTC

    The switch has restored and is online - We are seeing some authentication issues with connectivity to our authentication servers. Our team are actively working to resolve the problem, we are really sorry for the inconvenience this is causing to you if you are affected.

  3. investigating Feb 27, 2026, 11:33 AM UTC

    Services are stable and user sessions are logged in. We apologise again for the outage this morning and we are working to implement changes to prevent repeat issues going forward.

  4. resolved Feb 27, 2026, 03:29 PM UTC

    Incident Resolved The unexpected switch reboot that occurred between 10:45 and 10:50 this morning has been resolved. Services were restored automatically once the device completed its restart cycle, and we have not observed any further instability. Initial investigation indicates this was an isolated hardware event. We are continuing to review logs and diagnostics to confirm the underlying trigger. As part of our ongoing network investment programme, we are actively replacing legacy hardware and increasing infrastructure redundancy across our core and access network. This includes staged equipment upgrades and resilience improvements designed to further reduce points of failure. Over the next three months, we will be carrying out a series of planned maintenance activities to complete this work. Where maintenance is service-affecting, it will be scheduled during off-peak hours and communicated in advance via this status page and an email to your account email address. We apologise for the disruption caused and appreciate your patience while we continue strengthening the network.

Read the full incident report →

Minor February 13, 2026

BGP Router Crash - Telehouse North

Detected by Pingoru
Feb 13, 2026, 09:04 AM UTC
Resolved
Feb 16, 2026, 11:32 AM UTC
Duration
3d 2h
Affected: Network Core
Timeline · 2 updates
  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 →

Looking to track 1310.io downtime and outages?

Pingoru polls 1310.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when 1310.io reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track 1310.io alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring 1310.io for free

5 free monitors · No credit card required