Reply

Fibre connection dropping... Any thoughts?

Camera Assistant
Posts: 1,010
Post 1 of 117
875 Views

Fibre connection dropping... Any thoughts?

Hi all,

 

My fibre connection has been dropping around every 15mins for the last 24hrs or so. I've noticed the noise margin has decreased from the usual 6.1 to 4.8 and the speed has also gone up, it used to be dead on 75mbps but ever since the line started dropping its been up to 79/80mbps. Any ideas? I guess the lines become unstable due to a higher connection speed?

 

System Up Time: 145:20:06
PortStatusTxPktsRxPktsCollision PktsTx b/sRx b/sUp Time
WANMER151011847390209435148800:13:14
LANUp158128990102031837027502329858145:20:06
WLAN (2.4 GHz)Disable0000000:00:00
WLAN (5 GHz)Disable0000000:00:00
PLCDisable0000000:00:00

Broadband LinkDownstreamUpstream
Connection Speed79348 kbps19999 kbps
Line Attenuation18.3 dB0.0 dB
Noise Margin4.7 dB7.7 dB

 

All Replies
Reply
Oracle
Posts: 8,372
Post 2 of 117
833 Views

Re: Fibre connection dropping... Any thoughts?

Hi @jamesn123 looks like you are correct you are connected to a cabinet which allows for lower noise margins the DLM system will lower the noise margin by roughly 1dB steps until the line either starts to show errors or drops at which time the DLM should return to the last stable value. The DLM system resets each night so hopefully it should be sorted this morning. If it continues into next week talk to Sky as Openreach may need to look at what has got stuck.

==========================


Oracles are customers and people too.
Camera Assistant
Posts: 1,010
Post 3 of 117
809 Views

Re: Fibre connection dropping... Any thoughts?

Thanks @Chrisee , looks like I may need to get in contact with Sky on Monday as it doesnt seem to be settling, still seems to be dropping every 15 and noise margin is fluctuating between 5.5 and 4.8 every 2mins

 

System Up Time: 166:49:23
PortStatusTxPktsRxPktsCollision PktsTx b/sRx b/sUp Time
WANMER31655157550108083021902957400:14:10
LANUp178171451115154794021729376925224166:49:23
WLAN (2.4 GHz)Disable0000000:00:00
WLAN (5 GHz)Disable0000000:00:00
PLCDisable0000000:00:00

Broadband LinkDownstreamUpstream
Connection Speed78748 kbps19999 kbps
Line Attenuation18.3 dB0.0 dB
Noise Margin4.9 dB7.7 dB

 

Camera Assistant
Posts: 1,010
Post 4 of 117
674 Views

Re: Fibre connection dropping... Any thoughts?

Hi all,

 

I'm resurfacing this post in the hopes that someone/Sky will see it and possibly advise on a path to a solution. The issue is my line has become very unstable shortly after an openreach engineer attended to fix an issue with a low speed. 

- The initial issue was the speed was down to around 50mbps with a rasied noise margin, this was fixed by an Openrach engineer who changed the main telephone socket and reset the line

- For a couple of weeks after this visit the connection was fine and was syncing at about 70mbps 

- However after a few weeks the line started to drop around twice a day, usually more on the weekends, and the speed started to climb to almost 80mbps

- The problem now is that the line will be stable for a few days but then it'll start to drop frequently for a few days and then it'll go back to being stable again for a little while. 

- My thoughts were it was just DLM trying to step the noise margin down to increase the speed however DLM doesn't seem to be seeing that the line is unstable therefore I seem to be stuck in a cycle of disconnections.

- This has been going on for about 2 months now, however more so in the last few weeks.

 

I've attached the router stats & support log for reference.

Thanks

P.S. The routers uptime is low as I think a firmware update was installed last night, before this the router had been up for weeks but obviously the WAN connection haddn't

 

System Up Time: 06:55:11
PortStatusTxPktsRxPktsCollision PktsTx b/sRx b/sUp Time
WANMER213944238965470100332289606:43:14
LANUp4252964236778402640024563006:55:11
WLAN (2.4 GHz)Disable0000000:00:00
WLAN (5 GHz)Disable0000000:00:00

Broadband LinkDownstreamUpstream
Connection Speed78140 kbps19999 kbps
Line Attenuation18.5 dB21.1 dB
Noise Margin4.9 dB7.7 dB

 

 

Jan 1 00:00:09 syslog: BusyBox v1.17.2
Jan 1 00:00:09 syslog: plc0 (Int switch port: 4) (Logical Port: 4) Link UP 100 mbps full duplex
Jan 1 00:00:09 syslog: [ 7.010000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:10 syslog: [ 10.075000] eth1 (Int switch port: 6) (Logical Port: 6) Link DOWN.
Jan 1 00:00:14 syslog: [ 14.260000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:20 syslog: [ 20.247000] Line 0: xDSL G.994 training
Jan 1 00:00:24 syslog: [ 24.258000] Line 0: ADSL link down
Jan 1 00:00:26 syslog: [ 26.449000] eth1 (Int switch port: 6) (Logical Port: 6) Link DOWN.
Jan 1 00:00:31 syslog: [ 31.487000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:34 syslog: sky dhcpc client (v0.0.1) started
Jan 1 00:00:35 syslog: [ 35.271000] Line 0: xDSL G.994 training
Jan 1 00:00:39 syslog: [ 39.274000] Line 0: ADSL link down
Jan 1 00:00:41 syslog: [ 41.277000] Line 0: xDSL G.994 training
Jan 1 00:00:56 syslog: [ 56.280000] Line 0: VDSL G.993 started
Jan 1 00:01:08 syslog: [ 68.851000] Line 0: VDSL2 link up, Bearer 0, us=19999, ds=78488
Jan 1 00:01:08 syslog: [ 68.857000] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jan 1 00:01:54 syslog: ptm0.1 - WAN link UP.
Jan 1 00:01:54 syslog: Received valid DHCP lease from server. Connection UP.
Jan 1 00:01:54 syslog: Connection Up. SNO/MAC/IP/SWVER: [AC4017AB009454/24A7DC68B1E0/5.65.154.87/2.07.2355.R]
Jan 1 00:01:54 syslog: Send out NTP request to ntp1.isp.sky.com
Jan 1 00:01:54 syslog: Time has been set from ntp1.isp.sky.com
Jun 1 06:00:05 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Jun 1 06:09:01 syslog: [ 650.941000] Line 0: VDSL2 link down
Jun 1 06:09:02 syslog: [ 652.434000] Line 0: xDSL G.994 training
Jun 1 06:09:02 syslog: Clear IP addresses. IP connection DOWN.
Jun 1 06:09:17 syslog: [ 667.452000] Line 0: VDSL G.993 started
Jun 1 06:09:30 syslog: [ 680.541000] Line 0: VDSL2 link up, Bearer 0, us=19999, ds=78140
Jun 1 06:09:30 syslog: [ 680.546000] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jun 1 06:10:16 syslog: ptm0.1 - WAN link UP.
Jun 1 06:10:16 syslog: Received valid DHCP lease from server. Connection UP.
Jun 1 06:10:16 syslog: Connection Up. SNO/MAC/IP/SWVER: [AC4017AB009454/24A7DC68B1E0/5.65.154.87/2.07.2355.R]
Jun 1 06:39:13 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 07:05:37 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 07:34:43 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 08:04:58 syslog: Send out NTP request to ntp1.isp.sky.com
Jun 1 08:04:58 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Jun 1 08:04:58 syslog: System time is up to date
Jun 1 08:05:52 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 08:34:40 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 09:04:22 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 09:29:16 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 09:57:46 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 10:22:04 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 10:22:04 syslog: Send out NTP request to ntp1.isp.sky.com
Jun 1 10:22:04 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Jun 1 10:22:04 syslog: System time is up to date
Jun 1 10:55:02 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 11:19:20 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 11:43:20 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 12:16:00 syslog: Lease renewed 3600 ip 5.65.154.87
Jun 1 12:42:04 syslog: Send out NTP request to ntp1.isp.sky.com
Jun 1 12:42:04 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Jun 1 12:42:04 syslog: System time is up to date
Jun 1 12:45:22 syslog: Lease renewed 3600 ip 5.65.154.87

 

Executive Producer
Posts: 4,810
Post 5 of 117
668 Views

Re: Fibre connection dropping... Any thoughts?

@jamesn123

 

The router log does show that the firmware was upgraded but it also shows that the line came up then went almost immediately down after 10 minutes. Even though the firmware was upgraded the line should not drop for DLM doesn't adjust itself because of a firmware upgrade, especially so for the VDSL driver on the router was not upgraded in any update since the manufacturer of the Sky router.

 

If the line drops more often than once in a 3 day period then the line has a fault, and if it does it after 10 minutes it needs a BT Openreach engineer booked to look at the fault ASAP.

 

When it happens again, and it will unfortunately then post further updates with logs and the router stats until Sky book a BT Openreach engineer to investigate and fix the fault. And with router stats and logs it may be possible to get further information that may help in locating the estimated location of the fault, whether at the cabinet or along the telephone line length.

 

[add] Also, because the speed is at it top range and that is what is being affected then the fault would likely be close to the cabinet, likely less than 20 metres. So, my estimate is a slightly poor joint at the PCP.

Camera Assistant
Posts: 1,010
Post 6 of 117
649 Views

Re: Fibre connection dropping... Any thoughts?


@mae-3 wrote: 

If the line drops more often than once in a 3 day period then the line has a fault, and if it does it after 10 minutes it needs a BT Openreach engineer booked to look at the fault ASAP.

Interesting you say that, I've been told by multiple advisers that 1 drop per day is acceptable and would not be considered as a fault which seems stupid to me.

 

I'll await inevitable line drop for more logs. In the meantime I'll go to Sky with the information you have given me to see what they say.

Executive Producer
Posts: 4,810
Post 7 of 117
645 Views

Re: Fibre connection dropping... Any thoughts?

@jamesn123

 

The 1 day period is when a line first goes live it does not apply when the line has reached a period of 3-day stability then it's 3 days adjustments and no more, and it certainly doesn't drop after 10 minutes!  And the frequency spectrum of the line doesn't adjust itself in 1 day unless there is a fault, it adjusts itself over seasons and long periods.

Camera Assistant
Posts: 1,010
Post 8 of 117
634 Views

Re: Fibre connection dropping... Any thoughts?


@mae-3 wrote:

@jamesn123

 

The 1 day period is when a line first goes live it does not apply when the line has reached a period of 3-day stability then it's 3 days adjustments and no more, and it certainly doesn't drop after 10 minutes!  And the frequency spectrum of the line doesn't adjust itself in 1 day unless there is a fault, it adjusts itself over seasons and long periods.


Will have to try make this clear to Sky CS as well then, thanks

Executive Producer
Posts: 4,810
Post 9 of 117
613 Views

Re: Fibre connection dropping... Any thoughts?

@jamesn123

 

Just to point out why I say 3 days it is when line(s) are connected to the cabinet otherwise no drops unless over a long period. For each line connected you usually get a 0.2dB to 0.3dB drop in noise margin for each line connected to your own cabinet, the noise margin then doesn't go back up unless a line is disconnected which is unusual. And BT Openreach doesn't connect lines every day of the week!

Camera Assistant
Posts: 1,010
Post 10 of 117
589 Views

Re: Fibre connection dropping... Any thoughts?

@mae-3 It may also be worth pointing out that on a speed test, obviously via ethernet, I only get about 69/70mbps even though the router is synced at 78. This seems slightly more than just the usual overhead loss?

Executive Producer
Posts: 4,810
Post 11 of 117
585 Views

Re: Fibre connection dropping... Any thoughts?

@jamesn123

 

Could you ping bbc.co.uk and could we see a latency figure from the ping with an estimated distance to London? Don't do it from a speed test site do it with the ping command at the command prompt for Windows or terminal prompt for MacOS, and do it over an ethernet connection to a computer. This is to see how much interleaving is being applied to the line itself, and hence the estimated amount of error correction. Also, would like to see that on the thread with about 10 or more pings to see the jitter on the line.

Camera Assistant
Posts: 1,010
Post 12 of 117
582 Views

Re: Fibre connection dropping... Any thoughts?

@mae-3 Here, doesnt seem too bad to me?

 

C:\Users\Administrator>ping bbc.co.uk

Pinging bbc.co.uk [151.101.64.81] with 32 bytes of data:
Reply from 151.101.64.81: bytes=32 time=15ms TTL=59
Reply from 151.101.64.81: bytes=32 time=12ms TTL=59
Reply from 151.101.64.81: bytes=32 time=14ms TTL=59
Reply from 151.101.64.81: bytes=32 time=13ms TTL=59

Ping statistics for 151.101.64.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 13ms

C:\Users\Administrator>

Executive Producer
Posts: 4,810
Post 13 of 117
571 Views

Re: Fibre connection dropping... Any thoughts?

@jamesn123

 

It's not too bad but slightly high unless down in the South West or North England/Scotland. The jitter on the line is quite high also which doesn't look that good either. Jitter should be about 1ms roundtrip maximum on a good line.

Camera Assistant
Posts: 1,010
Post 14 of 117
570 Views

Re: Fibre connection dropping... Any thoughts?

@mae-3 I did a ping -t for 30 seconds also

 

C:\Users\Administrator>ping -t bbc.co.uk

Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=16ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=18ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=26ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=18ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=16ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=16ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=18ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=16ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=13ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=17ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=15ms TTL=59
Reply from 151.101.128.81: bytes=32 time=12ms TTL=59
Reply from 151.101.128.81: bytes=32 time=11ms TTL=59
Reply from 151.101.128.81: bytes=32 time=14ms TTL=59

Ping statistics for 151.101.128.81:
Packets: Sent = 154, Received = 154, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 26ms, Average = 12ms

 

Camera Assistant
Posts: 1,010
Post 15 of 117
566 Views

Re: Fibre connection dropping... Any thoughts?


@mae-3 wrote:

@jamesn123

 

It's not too bad but slightly high unless down in the South West or North England/Scotland. The jitter on the line is quite high also which doesn't look that good either. Jitter should be about 1ms roundtrip maximum on a good line.


I'm based in the North West so a fair distance from London 

Reply
Recommended Threads
28-05-2018 12:38 PM
11-06-2018 02:59 PM
21-03-2018 12:04 PM
08-03-2018 08:14 PM
13-04-2018 08:19 PM