Increasing consistent small packet loss

Gary · Jan 06, 2014, 14:57:01

Quote from: zappaDPJ on Jan 06, 2014, 14:53:34
Just to confirm what Steve has said, I can see that every IDNet TBBQM we monitor which includes both FTTC and ADSL connections, all showing packet loss between midday and 2.00pm. Although I wouldn't describe the degree of packet loss as substantial, typically four in every hundred packets, it usually coincides with a major drop in throughput.

It seems to happen again early evening to, Zap, and then after 8:30pm ish all is fine again till the next day when it starts again, maybe finding a pattern with timing would be useful?

zappaDPJ · Jan 06, 2014, 14:59:52

It probably would Gary. Posting a snap-shot BQM sometime before the end of each day might help with that.

Gary · Jan 06, 2014, 15:03:05

Quote from: zappaDPJ on Jan 06, 2014, 14:59:52
It probably would Gary. Posting a snap-shot BQM sometime before the end of each day might help with that.

What I don't understand is why we can see it and would have to do this, and support sees nothing when we get wonky speeds, and its not always the same people that get wonky speeds either

Time for a cup of tea I think.

davecollins · Jan 06, 2014, 15:06:06

Yes, I also see the speed drops, and then correlate this with what I see in TBBQM.

I run JD's Auto Speed Tester - http://www.gmwsoftware.co.uk/ - , and you can see what happens to the download speeds. This is sampled every hours. Can you spot where today's packet loss began? And today was mild. So far...

Steve · Jan 06, 2014, 15:08:13

I've just been looking at a Plusnet TBBQM and there a trace of packet loss on there, same timing but not to the same degree!

Gary · Jan 06, 2014, 15:11:59

Im down to 38Mbps but pings are fine at 8ms

Edit 20Mbps now

psp83 · Jan 06, 2014, 15:18:05

Packet loss is back, speeds are slow..

Code Select


Pinging bbc.co.uk [212.58.251.195] with 32 bytes of data:
Reply from 212.58.251.195: bytes=32 time=39ms TTL=120
Reply from 212.58.251.195: bytes=32 time=31ms TTL=120
Reply from 212.58.251.195: bytes=32 time=40ms TTL=120
Reply from 212.58.251.195: bytes=32 time=37ms TTL=120
Reply from 212.58.251.195: bytes=32 time=41ms TTL=120
Reply from 212.58.251.195: bytes=32 time=42ms TTL=120
Reply from 212.58.251.195: bytes=32 time=46ms TTL=120
Reply from 212.58.251.195: bytes=32 time=38ms TTL=120
Reply from 212.58.251.195: bytes=32 time=49ms TTL=120
Reply from 212.58.251.195: bytes=32 time=47ms TTL=120
Reply from 212.58.251.195: bytes=32 time=40ms TTL=120
Reply from 212.58.251.195: bytes=32 time=29ms TTL=120
Reply from 212.58.251.195: bytes=32 time=30ms TTL=120
Reply from 212.58.251.195: bytes=32 time=41ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Request timed out.
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=27ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Request timed out.
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=23ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Request timed out.
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Request timed out.
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120
Reply from 212.58.251.195: bytes=32 time=22ms TTL=120

Ping statistics for 212.58.251.195:
    Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 49ms, Average = 24ms

Code Select


Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 100 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway [192.168.1.254]
  2    43 ms    22 ms    22 ms  telehouse-gw4-lo1.idnet.net [212.69.63.98]
  3    22 ms    22 ms    21 ms  212.69.63.78
  4    22 ms    21 ms    22 ms  rt-lonap-b.thdo.bbc.co.uk [5.57.80.91]
  5     *        *        *     Request timed out.
  6    23 ms    23 ms    23 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
  7    23 ms    23 ms    23 ms  132.185.255.156
  8    24 ms    23 ms    23 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

Gary · Jan 06, 2014, 15:19:27

Quote from: psp83 on Jan 06, 2014, 15:18:05
Packet loss is back, speeds are slow..

My speeds are very low now but pings are fine

Ping has started...

PING www.idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=8.651 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=8.631 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=7.995 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=8.036 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=8.092 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=8.151 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=8.787 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=8.192 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=8.151 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=8.172 ms

--- www.idnet.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 7.995/8.286/8.787/0.273 ms

zappaDPJ · Jan 06, 2014, 15:19:58

I have to agree with the general consensus of opinion here, my throughput at this time is also highly variable (although my upstream is normal). It's also very noticeable while browsing that pages are taking a long time to resolve.

psp83 · Jan 06, 2014, 15:20:41

Just updated mine with trace route and ping.

Gary · Jan 06, 2014, 15:22:23

My traceroute and pings are fine, my speed is now 39.40 Mbps so half my usual, and pages are loading like treacle.

Baz · Jan 06, 2014, 15:46:44

Dont know if this helps in any way but heres mine sorry if its too much.

Tracing route to www.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 30 ms 30 ms redbus-gw3.idnet.net [212.69.63.42]
3 29 ms 29 ms 29 ms redbus-gw2-gi5-301.idnet.net [212.69.63.210]
4 30 ms 30 ms 29 ms rt-lonap-b.thdo.bbc.co.uk [5.57.80.91]
5 * * * Request timed out.
6 31 ms 30 ms 31 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
7 32 ms 33 ms 32 ms 132.185.255.165
8 32 ms 31 ms 31 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

Trace complete.

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 30 ms 30 ms redbus-gw3.idnet.net [212.69.63.42]
3 30 ms 30 ms 30 ms redbus-gw1-gi5-0-301.idnet.net [212.69.63.209]
4 29 ms 29 ms 29 ms bob.idnet.net [212.69.36.10]

Trace complete.

Tracing route to cnn.com [157.166.226.25]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 29 ms 30 ms redbus-gw3.idnet.net [212.69.63.42]
3 29 ms 29 ms 29 ms redbus-gw2-gi5-301.idnet.net [212.69.63.210]
4 30 ms 30 ms 30 ms telehouse-gw5-gi5-331.idnet.net [212.69.63.6]
5 30 ms 29 ms 29 ms ge-5-2-7.edge6.London1.Level3.net [212.113.9.65]

6 118 ms 116 ms 116 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

7 117 ms 117 ms 116 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]

8 117 ms 132 ms 116 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]

9 115 ms 123 ms 115 ms 4.69.201.70
10 115 ms 115 ms 116 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
11 116 ms 116 ms 117 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
12 116 ms 115 ms 116 ms ae-1-51.edge4.Atlanta2.Level3.net [4.69.150.13]

13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to www.thinkbroadband.co.uk [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 30 ms 29 ms redbus-gw3.idnet.net [212.69.63.42]
3 30 ms 30 ms 30 ms redbus-gw2-gi2-300.idnet.net [212.69.63.226]
4 30 ms 30 ms 29 ms telehouse-gw5-gi5-331.idnet.net [212.69.63.6]
5 31 ms 31 ms 31 ms gi4-42-75-idnet.bdr-rt3.thdo.ncuk.net [80.249.97
.109]
6 30 ms 31 ms 30 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.9
7.9]
7 31 ms 31 ms 31 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

Pinging www.thinkbroadband.co.uk [80.249.99.130] with 32 bytes of data:

Reply from 80.249.99.130: bytes=32 time=30ms TTL=58
Reply from 80.249.99.130: bytes=32 time=31ms TTL=58
Reply from 80.249.99.130: bytes=32 time=30ms TTL=58
Reply from 80.249.99.130: bytes=32 time=30ms TTL=58

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

Reya · Jan 06, 2014, 15:47:44

Packet loss here, too:

It definitely appears as if it could be business-related. Rough times of my packet loss so far this year:

Jan 1st (bank holiday): none
Jan 2nd (Thur): between 13:45 and 17:00
Jan 3rd (Fri): intermittently from 11:00 to 11:30, 13:30 to 14:00 and 15:30 to 17:30
Jan 4th (Sat): Small amount, but that coincided with other issues I was having
Jan 5th (Sun): none at all
Jan 6th (Mon): see above

As this thread seems to be collecting data, here's what I have just going back through December last year:

Sun 1st: 20:00 to 23:00
Mon 2nd: Intermittently all day, but mainly between 17:00 and 23:00
Tue 3rd: 12:30 to 16:00
Wed 4th: horrendous day! 04:00 to 11:00 (huge spike at 07:00), 16:30 to 18:00 and 21:00 to 23:00
Thur 5th: 18:30 to 21:00
Mon 9th: 16:00 to 17:00
Tue 10th: Intermittently between 16:30 and 22:00
Wed 11th: 11:00 to 12:00, then intermittently from 14:00 to 22:00
Thur 12th: 15:30 to 16:00
Mon 16th: Intermittently all day between 09:00 and 22:00
Tue 17th: 11:00 to 17:00
Wed 18th: 16:00 to 17:30
Fri 20th: 11:30 to 15:00
Mon 23rd: 10:00 to 13:00
Sat 28th: 13:00 to 15:30

All other days packet loss was either non-existent, negligible, or coincided with other issues I was having. HTH

jane · Jan 06, 2014, 21:35:02

My ADSL2+ connection follows everyone else's patterns. Here's todays

andrue · Jan 07, 2014, 12:25:29

I've also just noticed that since the early hours of the 3rd I've had continuous jitter:

I do have a new router now but that was installed two days before and wasn't showing any jitter back then:

Actually my usage is a little concerning as well

sobranie · Jan 07, 2014, 13:49:29

Here we go again, 3/4 speed vanished. Packet loss has started too!

davecollins · Jan 07, 2014, 14:01:04

Yup - same here. It's always early afternoon.

The question is: if there are so many idnet customers experiencing this and proving it, why are idnet still apparently waiting for the problem to resolve itself?

Simon: seriously, what do we need to do to convince you there's a problem here?

Bill · Jan 07, 2014, 14:04:04

Some packet loss here too (BQMs in sig), and this time speed has taken a hit too:

Even the single-thread download, which never usually budges from ~12Mbps

psp83 · Jan 07, 2014, 14:14:47

Adrian · Jan 07, 2014, 14:15:15

Started here again, worse than before if anything. Ignore spike around 11:00am, I and to reboot the router.

Gary · Jan 07, 2014, 14:15:37

24Mbps...this is ridiculous what the hell is going on IDnet!!?

davecollins · Jan 07, 2014, 14:19:00

Same here. Not expecting any meaningful reply from them though. Would love to be proved wrong.

Steve · Jan 07, 2014, 14:35:00

I've just done 3 BT Speedtests and they confirm I've lost 3/4 of my download speed with the associated packet loss.

Adrian · Jan 07, 2014, 14:38:07

Code Select

 1. 192.168.1.254                                                                                           0.0%    28    0.5   0.5   0.4   0.7   0.0
 2. telehouse-gw4-lo1.idnet.net                                                                             0.0%    28   23.7  36.0  23.2 131.6  30.2
 3. redbus-gw2-gi3-331.idnet.net                                                                           46.4%    28   23.4  23.6  22.6  30.6   1.9
 4. redbus-gw2-gi3-331.idnet.net                                                                           37.0%    28   23.1  23.6  22.7  27.0   1.0
 5. redbus-gw1-gi5-0-301.idnet.net                                                                          0.0%    28   23.8  25.1  22.9  65.1   7.9
 6. www.idnet.net                                                                                           0.0%    27   23.2  23.3  22.6  23.8   0.3

Even worse now

Code Select

 1. 192.168.1.254                                                                                           0.0%   128    0.4   0.4   0.4   1.1   0.1
 2. telehouse-gw4-lo1.idnet.net                                                                             0.8%   128   25.1  39.5  23.1 277.2  36.6
 3. redbus-gw2-gi3-331.idnet.net                                                                            1.6%   128   23.9  23.4  22.4  28.3   0.7
 4. redbus-gw2-gi3-331.idnet.net                                                                           96.8%   128   23.8  23.5  23.0  24.1   0.5
 5. redbus-gw1-gi5-0-301.idnet.net                                                                          2.3%   128   23.6  24.0  22.6  48.3   2.9
 6. www.idnet.net                                                                                           0.0%   128   23.3  24.3  22.7  87.3   6.1

psp83 · Jan 07, 2014, 14:42:32

Damn you IDnet, I'm trying to look online for new carpets and you are stopping me from spending money because sites are slow at loading, DAMN YOU!

On a serious note... Anyone at IDnet want to update ?