Menu
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
291 Views
Message 1 of 11
Flag for a moderator

Packet loss, up to 60% for large periods

I've got large periods of terrible packet loss. Since yesterday I've been measuring it:

Packet lossPacket loss

For hours at a time, the internet connection is nearly unusable. Restarting the router often (but not always) makes the packet loss go away for a short while. (For example, the dip between 14:25 and 15:57 there is likely my housemate rebooting the router).

I need any help I can get to reduce this problem - even browsing the web is nearly impossible when the packet loss is at its worst.

0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
233 Views
Message 2 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

The packet loss continues - here's the measurement for the past week(ish):

 

2017-08-06-packet_loss.png

The internet connection is periodically not usable. Bouncing the router brings back the connection for a while again.

0 Kudos
Reply
  • 8.24K
  • 512
  • 2.26K
Superuser
Superuser
229 Views
Message 3 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

 Set up a BQM

HERE

 

Run it for say 24 hrs, and post the result.

 

Dont forget youll need to make sure your super hub is configured to reply to ICMP echo requests...

 

 

 


0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
204 Views
Message 4 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Today's been amazingly much better:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1abf0a02b0813957dc0fc4b59e8cd3b8e52601d4-09-08-2017

Compare the external and intenal monitoring - and they agree well:

 

I'm going to keep the monitor going for while.

0 Kudos
Reply
  • 8.24K
  • 512
  • 2.26K
Superuser
Superuser
193 Views
Message 5 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Youve still got packet loss. So keep it running, come back and tell us if it kicks off again...

 


0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
171 Views
Message 6 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Good call on keeping the monitoring going. Unfortunately, it looks like the packet loss is picking back up again:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fe4b77e9751ec086c469d19b1bc481b82df478ff-12-08-2017

 

0 Kudos
Reply
  • 9.61K
  • 284
  • 616
Forum Team
Forum Team
115 Views
Message 7 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Hey anglerud,

Thanks for posting Smiley Happy

Sorry to see the problems you're having with your connection. Everything looks good from our end so I'm hoping this has settled down for you now.

Do you still need help with this?

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
87 Views
Message 8 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Thank you for your reply.

A virgin media technician came around and re-crimped the coax connector, and replaced the router. She said it'd take a while to settle in, so I've given it a bit of time to see if things would improve. Unfortunately, I still get dropouts, here is yesterday:

[MOD EDIT: Inappropriate Image removed (Contains IP address), please review the Forum Guidelines]

 

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/e53822f59977d83abfbe7a9756f9ee5130...

 

0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
72 Views
Message 9 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

Interestingly, there is also a constant low level packet loss:

 

$ ping www.yahoo.com 
PING atsv2-fp.wg1.b.yahoo.com (46.228.47.115) 56(84) bytes of data.                                      
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=1 ttl=55 time=31.3 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=2 ttl=55 time=27.8 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=3 ttl=55 time=25.9 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=4 ttl=55 time=25.9 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=5 ttl=55 time=24.3 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=6 ttl=55 time=25.7 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=7 ttl=55 time=87.7 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=8 ttl=55 time=27.8 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=9 ttl=55 time=36.0 ms                   
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=10 ttl=55 time=34.9 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=11 ttl=55 time=27.2 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=12 ttl=55 time=23.0 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=13 ttl=55 time=23.8 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=14 ttl=55 time=24.2 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=15 ttl=55 time=30.6 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=17 ttl=55 time=27.2 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=19 ttl=55 time=27.8 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=20 ttl=55 time=26.8 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=21 ttl=55 time=27.6 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=22 ttl=55 time=25.2 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=23 ttl=55 time=24.6 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=24 ttl=55 time=23.0 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=25 ttl=55 time=22.0 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=26 ttl=55 time=29.0 ms                  
64 bytes from ir1.fp.vip.ir2.yahoo.com (46.228.47.115): icmp_seq=27 ttl=55 time=22.9 ms                  
^C                        
--- atsv2-fp.wg1.b.yahoo.com ping statistics ---    
27 packets transmitted, 25 received, 7% packet loss, time 26068ms                                        
rtt min/avg/max/mdev = 22.018/29.339/87.740/12.404 ms

And this can be seen from my intenal monitoring as well:

Packetloss, intenal monitorPacketloss, intenal monitor

An interesting correlation is that when the average latency to the first hop outside the router shot up to ~450ms, packetloss went down to close to 0. Otherwise it hovers between 2 and 5%.

0 Kudos
Reply
  • 7
  • 0
  • 0
anglerud
Joining in
59 Views
Message 10 of 11
Flag for a moderator

Re: Packet loss, up to 60% for large periods

and today was unfortunately much worse:

 

bank holiday dropoutsbank holiday dropouts

There were fairly long periods today when I couldn't really do much.

0 Kudos
Reply