cancel
Showing results for 
Search instead for 
Did you mean: 

Packet loss for the last week

hrtheboss
Newbie
Posts: 2
Registered: 22-07-2016

Packet loss for the last week

So I've started getting packet loss since about 8 days ago (we've had the service for some time and there has never been an issue like this) and it's been getting worse making online games unplayable.

I've checked the ethernet cables (and tried using wireless) as well as the rj11 cable and there doesn't appear to be any issues there. 

Is this likely to be a fault with the router or modem or could it be an issue on plusnet's end?

It does appear that at some times it gets better for a while (although never completely fixed) and then gets worse which makes me think it could be the service rather than hardware.

___________________________________________________________________

C:\Windows\system32>ping community.plus.net -n 200

Pinging aptgm87544.lithium.com [46.19.168.229] with 32 bytes of data:
.......

Ping statistics for 46.19.168.229:
Packets: Sent = 200, Received = 172, Lost = 28 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 26ms, Average = 18ms

Tags (3)
3 REPLIES
SpendLessTime
Aspiring Hero
Posts: 2,597
Thanks: 699
Fixes: 67
Registered: 21-09-2009

Re: Packet loss for the last week

I would suggest that packet loss is more likely to be outside of your premises so in Plusnet's domain.

There is a guide for you to try various actions before logging a fault at https://community.plus.net/t5/Library/Broadband-Faults-Guide-I-have-a-fault/ba-p/1322773

which ends with the link to the fault logging mechanism at https://faults.plus.net/ 

dratddestroyer
Grafter
Posts: 164
Registered: 27-09-2007

Re: Packet loss for the last week

Are your MTU settings the same on your router and PC?

 

This web page helped me. Its from TP link.  http://www.tp-link.us/FAQ-190.html

hrtheboss
Newbie
Posts: 2
Registered: 22-07-2016

Re: Packet loss for the last week

Thanks for the help everyone. I decided to buy myself a new router/modem in order to test that. It turns out that seems to have been the issue.