cancel
Showing results for 
Search instead for 
Did you mean: 

Packet loss and ping problem?

johnukd
Newbie
Posts: 9
Registered: 11-03-2015

Packet loss and ping problem?

Hi all.
I have a problem which I first noticed this afternoon. The internet became very unresponsive and although it has recovered somewhat, there still seems to be a major fault. If I ping google.co.uk 25 times, this is the result:

C:\Users\John>ping -n 20 google.co.uk
Pinging google.co.uk [216.58.208.35] with 32 bytes of data:
Reply from 216.58.208.35: bytes=32 time=11ms TTL=55
Request timed out.
Reply from 216.58.208.35: bytes=32 time=434ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.208.35: bytes=32 time=463ms TTL=55
Reply from 216.58.208.35: bytes=32 time=10ms TTL=55
Reply from 216.58.208.35: bytes=32 time=449ms TTL=55
Reply from 216.58.208.35: bytes=32 time=9ms TTL=55
Reply from 216.58.208.35: bytes=32 time=459ms TTL=55
Reply from 216.58.208.35: bytes=32 time=10ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.208.35: bytes=32 time=8ms TTL=55
Reply from 216.58.208.35: bytes=32 time=7ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.58.208.35:
    Packets: Sent = 20, Received = 10, Lost = 10 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 463ms, Average = 186ms

Anyone else having this issue? Im in Rainham, RM13 on FTTC.
Cheers, John.
8 REPLIES
Alucidnation
Grafter
Posts: 182
Thanks: 8
Registered: 03-01-2015

Re: Packet loss and ping problem?

Try hoping gateways.
For some reason, Plusnet system seems to change your gateway without you noticing, until this happens.
Ive asked why this happens and so far, no one has even responded.
plumbz
Newbie
Posts: 1
Registered: 11-03-2015

Re: Packet loss and ping problem?

Same for me tonight up in Scotland! Really slow.  I came on here to see if anyone else had the same issue.
C:\Windows\system32>tracert www.google.co.uk
Tracing route to www.google.co.uk [216.58.208.67]
over a maximum of 30 hops:
 1     1 ms    <1 ms     6 ms  192.168.1.1
 2    33 ms    29 ms    32 ms  lo0-central10.ptn-ag02.plus.net [195.166.128.191
]
 3    78 ms    33 ms    29 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.13
2]
 4    68 ms    57 ms    55 ms  xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
 5    69 ms    92 ms    85 ms  72.14.222.97
 6   870 ms  1268 ms  1075 ms  209.85.246.242
 7    40 ms    36 ms    67 ms  216.239.51.233
 8   992 ms  1032 ms  1273 ms  lhr14s27-in-f3.1e100.net [216.58.208.67]
Trace complete.
johnukd
Newbie
Posts: 9
Registered: 11-03-2015

Re: Packet loss and ping problem?

Quote from: Alucidnation
Try hoping gateways.

What does this mean?
Thanks Plumz. Not sure what I can do.
musser666
Newbie
Posts: 4
Registered: 12-03-2015

Re: Packet loss and ping problem?

Having the same issue in Scotland (Edinburgh) at the moment.
Normal speeds for me are 60-70Mbps down and 15-18 Mbps up with steady ping of 17ms
As of yesterday I am getting 1-4Mbps down and 15-18Mbps up with a ping of 17ms dropping multiple packets every 5-10 pings.
Logged it with support last night who did the usual troubleshooting. Laptop connected directly to the BT modem using PPPoE was showing the same, so the fault is clearly not my equipment.
Was hoping it would be fixed this morning but it is still the same. Not pleased at the moment, I really don't care too much about the download speed, but the packets dropping is messing up my ability to play games.
I see on the service status page there is maintenance work by BT all this week. I was advised by 2 people at plusnet this was unlikely to be the cause of the issue, but I'm not sure how they can say this when the status page says: "Although these are the areas or exchanges we have been notified of, due to the nature of the broadband network these outages may affect customers nationwide. There are also a number of smaller exchange works most nights of the week that may cause smaller outages at individual exchanges."
johnukd
Newbie
Posts: 9
Registered: 11-03-2015

Re: Packet loss and ping problem?

I play Counter Strike (game) and that's how I noticed the issue, it was not playable.The issue I had seems to be OK at the moment.
Ping statistics for 216.58.208.35:
    Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 304ms, Average = 10ms

Lets hope whatever it was has resolved Smiley
musser666
Newbie
Posts: 4
Registered: 12-03-2015

Re: Packet loss and ping problem?

Still bad tonight, if not worse.
This is my ping to any destination (google, gaming servers in london, bbc, work, etc)
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Request timed out.
Request timed out.
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=22ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Reply from 85.236.96.22: bytes=32 time=18ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=17ms TTL=124
Getting 2Mbps download and 18Mbps up.....
No update on my open ticket yet, ref: 100756676
whats going on?
musser666
Newbie
Posts: 4
Registered: 12-03-2015

Re: Packet loss and ping problem?

Still the same this morning
joclark
Grafter
Posts: 140
Registered: 09-03-2015

Re: Packet loss and ping problem?

Hi, I have had a look at your account, this will be picked up in the next couple of days. Sorry for the delay.
Thank you
Jo