cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
1,012 Views
Message 1 of 7

High ping / packet loss

Hi there.

 

As of late I have had really high ping and packet loss out of nowhere. It is quite consistent. I noticed it start happening after I decided to leave for virgin and they failed to pull the fibre to my house twice where I then cancelled. Could they have damaged some cabelling?bbc.co.uk.pngI've attached my ping plotter results. I have an engineer coming out on Monday but they have done a test and found no issues. I am pulling my hair out I cannot game at all with this ping and packet loss.

0 Ratings
Reply
6 REPLIES 6
1,011 Views
Message 2 of 7

Re: High ping / packet loss

Screenshot 2023-04-05 194059.png

0 Ratings
Reply
981 Views
Message 3 of 7

Re: High ping / packet loss

You have zero packet loss.

0 Ratings
Reply
940 Views
Message 4 of 7

Re: High ping / packet loss

Screenshot 2023-04-06 195926.pngIn this instance yes. I have done a tracert to bt. Could you help diagnose the results?

0 Ratings
Reply
913 Views
Message 5 of 7

Re: High ping / packet loss

Request timed out just means the a router is either not to reply to ICMP requests or was too busy doing its job of forwarding packets to the next in line to reply in time.

That would apply to almost all BT routers (including your hub) as BT see it as a security risk.

Going back to your ping plotter always start from the destination which showed 0 packet loss so anything previous was meaningless. You only trace backwards if there is loss at the destination.

0 Ratings
Reply
810 Views
Message 6 of 7

Re: High ping / packet loss

@husej Hi mate. Did you ever get a solution to this as I’m getting the same issue. It’s been going on for about 5 weeks now. Had two engineers out and a home tech expert and no one knows. BT have said it’s not their problem. I’m in the same boat, pulling my hair out at this one

0 Ratings
Reply
772 Views
Message 7 of 7

Re: High ping / packet loss

@RyatnThe OP never got a solution as he never had a problem. He just misunderstood the pingplotter and tracert results.

0 Ratings
Reply