0

Discussion topic: Internet connection drops approx once a fortnight but it's random

Reply
This message was authored by georgeZ1 This message was authored by: georgeZ1

Internet connection drops approx once a fortnight but it's random

This is annoying as I spot the orange light (internet) and have to reboot the router.
We have Ring /Alexa devices connected (as well as mobiles, PCs etc). Some Ring devices have to be reset.
 
I attach router details and the log. It appears to me that the log is cleared on reboot (?) and time starts 1970 until GMT time is acquired. Are there any other diagnostics to try and see whats happening at the time just before the link goes down?
 
ManufacturerSky
ModelSR203
Firmware Version7.03.0704.R
DSL Firmware VersionA2pvfbH043p1.d26u

 

NOTE cant just paste the log contents as the system objects to dates!

And there are no buttons to allow files to be attached!

 

[start of log]

<start date had to edited as 1970/01/01 blocked> 00:00:25 syslog: [ 24.951000] eth3 (Ext switch port: 4) (Logical Port: 12) Link UP 1000 mbps full duplex
<start date had to edited as 1970/01/01 blocked> 00:00:45 syslog: [ 40.408000] Line 0: xDSL link down
<start date had to edited as 1970/01/01 blocked> 00:00:47 syslog: [ 46.432000] Line 0: xDSL link down
<start date had to edited as 1970/01/01 blocked> 00:00:55 syslog: Voice Configured
<start date had to edited as 1970/01/01 blocked> 00:01:00 syslog: Voice Initialized
<start date had to edited as 1970/01/01 blocked> 00:01:00 syslog: Voice Connecting
<start date had to edited as 1970/01/01 blocked> 00:01:13 syslog: Voice Disconnected
<start date had to edited as 1970/01/01 blocked> 00:01:16 syslog: [ 57.439000] Line 0: xDSL link down
<start date had to edited as 1970/01/01 blocked> 00:01:27 syslog: sky dhcpc client (v0.0.1) started
<start date had to edited as 1970/01/01 blocked> 00:01:47 syslog: sky dhcpc client (v0.0.1) started
<start date had to edited as 1970/01/01 blocked> 00:01:53 syslog: eth3.1 - WAN link UP.
<start date had to edited as 1970/01/01 blocked> 00:01:53 syslog: Received valid DHCP lease from server. Connection UP.
<start date had to edited as 1970/01/01 blocked> 00:01:55 syslog: Connection Up. SNO/MAC/IP/SWVER/IPv6: [D210233D033307/B4BA9D3CC678/90.218.244.225/7.03.0704.R/::1]
<start date had to edited as 1970/01/01 blocked> 00:01:55 syslog: Send out NTP request to ntp1.isp.sky.com
<start date had to edited as 1970/01/01 blocked> 00:01:55 syslog: Time has been set from ntp1.isp.sky.com
2024-<may 23rd> 16:28:57 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 16:29:06 syslog: WAN IPV6 UP
2024-<may 23rd> 16:29:06 syslog: Voice IP Connection Up: 2a02:c7c:b233:fe00::1/64
2024-<may 23rd> 16:29:06 syslog: Connection Up. SNO/MAC/IP/SWVER/IPv6: [D210233D033307/B4BA9D3CC678/90.218.244.225/7.03.0704.R/2a02:c7c:b233:fe00::1]
2024-<may 23rd> 16:29:09 syslog: TR69: Connect to Production ACS
2024-<may 23rd> 16:29:09 syslog: TR69: Connection to ACS Complete
2024-<may 23rd> 16:29:15 syslog: Voice Configured
2024-<may 23rd> 16:29:16 syslog: TR69: Close ACS Connection
2024-<may 23rd> 16:29:19 syslog: Voice Initialized
2024-<may 23rd> 16:29:19 syslog: Voice Connecting
2024-<may 23rd> 16:29:19 syslog: Voice HARDENING
2024-<may 23rd> 16:29:21 syslog: Voice Connected
2024-<may 23rd> 16:29:21 syslog: Voice Disconnected
2024-<may 23rd> 16:29:25 syslog: Voice DeInitialized
2024-<may 23rd> 16:29:28 syslog: Voice Configured
2024-<may 23rd> 16:29:32 syslog: Voice Initialized
2024-<may 23rd> 16:29:32 syslog: Voice Connecting
2024-<may 23rd> 16:29:33 syslog: Voice Connected
2024-<may 23rd> 16:30:17 syslog: [ 195.501000] eth0 (Ext switch port: 0) (Logical Port: 😎 Link UP 1000 mbps full duplex
2024-<may 23rd> 16:30:21 syslog: [ 199.540000] eth0 (Ext switch port: 0) (Logical Port: 😎 Link DOWN.
2024-<may 23rd> 16:30:41 syslog: [ 219.647000] eth0 (Ext switch port: 0) (Logical Port: 😎 Link UP 1000 mbps full duplex
2024-<may 23rd> 16:58:53 syslog: WAN IPV6 UP
2024-<may 23rd> 16:59:43 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 17:25:13 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 17:28:53 syslog: WAN IPV6 UP
2024-<may 23rd> 17:58:49 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 17:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 18:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 18:32:25 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 18:47:01 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 18:47:01 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 18:47:01 syslog: System time is up to date
2024-<may 23rd> 18:58:53 syslog: WAN IPV6 UP
2024-<may 23rd> 19:03:01 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 19:27:19 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 19:28:53 syslog: WAN IPV6 UP
2024-<may 23rd> 19:58:53 syslog: WAN IPV6 UP
2024-<may 23rd> 20:00:01 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 20:28:53 syslog: WAN IPV6 UP
2024-<may 23rd> 20:34:31 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 20:50:58 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 20:50:59 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 20:50:59 syslog: System time is up to date
2024-<may 23rd> 20:52:00 syslog: TR69: Connect to Production ACS
2024-<may 23rd> 20:52:00 syslog: TR69: Connection to ACS Complete
2024-<may 23rd> 20:52:08 syslog: TR69: Close ACS Connection
2024-<may 23rd> 20:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 21:08:43 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 21:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 21:40:31 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 21:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 22:14:43 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 22:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 22:40:50 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 22:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 23:02:49 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 23:02:49 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 23:02:49 syslog: System time is up to date
2024-<may 23rd> 23:05:08 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 23:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 23:31:50 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 23:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 00:02:44 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 00:28:14 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 00:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 00:57:56 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 00:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 01:22:32 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 01:25:05 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 01:25:05 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 01:25:05 syslog: System time is up to date
2024-<may 23rd> 01:28:54 syslog: WAN IPV6 UP
2024-<may 23rd> 01:49:14 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 01:58:54 syslog: WAN IPV6 UP
2024-<may 23rd> 02:24:20 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 02:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 02:53:26 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 02:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 03:26:44 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 03:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 03:42:35 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 03:42:35 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 03:42:35 syslog: System time is up to date
2024-<may 23rd> 03:56:09 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 03:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 04:20:09 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 04:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 04:50:27 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 04:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 05:21:39 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 05:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 05:50:34 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 05:50:34 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 05:50:34 syslog: System time is up to date
2024-<may 23rd> 05:54:57 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 05:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 06:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 06:30:39 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 06:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 07:04:33 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 07:28:51 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 07:28:56 syslog: WAN IPV6 UP
2024-<may 23rd> 07:58:56 syslog: WAN IPV6 UP
2024-<may 23rd> 08:04:33 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 08:12:35 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 08:12:35 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 08:12:35 syslog: System time is up to date
2024-<may 23rd> 08:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 08:33:03 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 08:57:21 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 08:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 09:25:15 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 09:28:55 syslog: WAN IPV6 UP
2024-<may 23rd> 09:58:55 syslog: WAN IPV6 UP
2024-<may 23rd> 09:59:45 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 10:28:56 syslog: WAN IPV6 UP
2024-<may 23rd> 10:33:57 syslog: Lease renewed 3600 ip 90.218.244.225
2024-<may 23rd> 10:37:40 syslog: Send out NTP request to ntp1.isp.sky.com
2024-<may 23rd> 10:37:41 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
2024-<may 23rd> 10:37:41 syslog: System time is up to date
2024-<may 23rd> 10:58:56 syslog: WAN IPV6 UP
2024-<may 23rd> 11:00:40 syslog: Lease renewed 3600 ip 90.218.244.225

Reply

All Replies

This message was authored by jamesn123 This message was authored by: jamesn123

Re: Internet connection drops approx once a fortnight but it's random

Posted by a Superuser, not a Sky employee. Find out more

@georgeZ1 

If its only dropping once every few weeks it may be difficult to pin down and unlikely that Sky or Openreach would accept it as a fault.

 

Please post your router stats
https://helpforum.sky.com/t5/Broadband/How-to-find-your-Sky-Broadband-router-stats/td-p/2855717/jump... 

I am NOT a Sky Employee
Myself & Others offer our time to help others, please be respectful.
georgeZ1
Topic Author
This message was authored by georgeZ1 This message was authored by: georgeZ1

Re: Internet connection drops approx once a fortnight but it's random

stats.jpg

This message was authored by jamesn123 This message was authored by: jamesn123

Re: Internet connection drops approx once a fortnight but it's random

Posted by a Superuser, not a Sky employee. Find out more

@georgeZ1 

Nothing on there suggests an issue unfortunately. 

I am NOT a Sky Employee
Myself & Others offer our time to help others, please be respectful.
georgeZ1
Topic Author
This message was authored by georgeZ1 This message was authored by: georgeZ1

Re: Internet connection drops approx once a fortnight but it's random

Another instance of the internet dropping out today. 

 

The router shows 

Connection Time00:00:00
Connecting to ServerDSL down

 

extract from log attached

 

Any help appreciated - thnaks

 

 

georgeZ1_0-1716901060428.png

 

 

Reply

Was this discussion not helpful?

No problem. Browse or search to find help, or start a new discussion on Community.

Start a new discussion

On average, new discussions are replied to by our users within 4 hours

New Discussion