Increasing consistent small packet loss

[davecollins]

I share your frustration, but have given up trying to get Idnet to reply. Or apparently even take this seriously. Nothing is happening about this.

[SimonM_IDNet]

Hi All,

Just a quick update we checked the network again today and found no issues. As part of a test as well we have two FTTC lines setup on the TBB checker and both of those are showing no packet loss. As has been suggested earlier if are experiencing any issues please contact support directly so we can take a further look. including any speedtests/trace routes etc so we can get as much data as we can.

Kind regards
Simon Mulliss
IDNet support

[mervl]

including any speedtests/trace routes etc so we can get as much data as we can.

Just about to go on to IDNet connected pc so will try to do so. Other TBB monitors are showing packet loss from 12.30pm today (6 Jan) on IDNet, why aren't IDNets two set ups???

[Gary]

Traceroute has started...

traceroute: Warning: www.bbc.co.uk has multiple addresses; using 212.58.246.93
traceroute to www.bbc.net.uk (212.58.246.93), 64 hops max, 72 byte packets
1  192.168.1.1 (192.168.1.1)  0.409 ms  0.160 ms  0.145 ms
2  telehouse-gw4-lo1.idnet.net (212.69.63.98)  13.696 ms  10.715 ms  18.202 ms
3  212.69.63.78 (212.69.63.78)  7.762 ms  7.524 ms  7.991 ms
4  rt-lonap-b.thdo.bbc.co.uk (5.57.80.91)  7.666 ms  7.491 ms  8.186 ms
5  * * *
6  ae0.er01.cwwtf.bbc.co.uk (132.185.254.93)  8.811 ms  9.202 ms  9.069 ms
7  * 132.185.255.165 (132.185.255.165)  9.620 ms  9.219 ms
8  bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93)  8.995 ms  9.242 ms  9.302 ms

[sobranie]

Hi Simon,

Please Note, since Christmas my speeds have been excellent ... even touched 75Mbps at one point. But, starting today things have all gone to pot again.
I shall post TBB monitor readings in a few hours time.
I haven't the time to commence an extended dialogue with IDNet at the mo.... sorry about that!

[Gary]

Traceroute has started...

traceroute to www.idnet.com (212.69.36.10), 64 hops max, 72 byte packets
1  192.168.1.1 (192.168.1.1)  0.440 ms  0.160 ms  0.143 ms
2  telehouse-gw4-lo1.idnet.net (212.69.63.98)  130.145 ms  223.093 ms  200.195 ms
3  212.69.63.84 (212.69.63.84)  7.897 ms  7.797 ms  7.554 ms
4  redbus-gw5-gi2-1276.idnet.net (212.69.63.9)  7.653 ms  7.722 ms  7.505 ms
5  redbus-gw1-gi5-0-301.idnet.net (212.69.63.209)  8.305 ms  7.796 ms  7.711 ms
6  bob.idnet.net (212.69.36.10)  7.909 ms  8.059 ms  7.645 ms

[sobranie]

[davecollins]

Tracert to Google is meaningless, but this is what I get to CNN.com:

1 192.168.1.1       2ms    2ms    2ms  TTL:255  (Vigor.router ok)
2 212.69.63.98     17ms   18ms   31ms  TTL:254  (telehouse-gw4-lo1.idnet.net ok)
3 212.69.63.78     17ms   16ms   17ms  TTL:253  (No rDNS)
4 212.113.9.65     17ms   16ms   16ms  TTL:251  (ge-5-2-7.edge6.London1.Level3.net ok)
5 4.69.139.120    103ms  143ms  153ms  TTL: 52  (ae-52-52.csw2.London1.Level3.net ok)
6 4.69.153.141    152ms  103ms  142ms  TTL: 52  (ae-59-224.ebr2.London1.Level3.net ok)
7 4.69.137.78     103ms  142ms  162ms  TTL: 52  (ae-44-44.ebr1.NewYork1.Level3.net ok)
8 4.69.201.66     143ms  122ms  122ms  TTL: 52  (No rDNS)
9 4.69.143.213    143ms  103ms  143ms  TTL: 52  (ae-1-100.ebr1.Washington12.Level3.net ok)
10 4.69.148.105    103ms  102ms  102ms  TTL: 53  (ae-6-6.ebr1.Atlanta2.Level3.net ok)
11 4.69.150.13     113ms  142ms  142ms  TTL:245  (ae-1-51.edge4.Atlanta2.Level3.net ok)
12   No Response      *      *      *                 
13   No Response      *      *      *                 
14   No Response      *      *      *                 
15   No Response      *      *      *                 
16   No Response      *      *      *                 
17   No Response      *      *      *                 
18   No Response      *      *      *                 
19   No Response      *      *      *             

And my Broadband Quality Monitor:

[davecollins]

 1 192.168.1.1       2ms    1ms    2ms  TTL:255  (Vigor.router ok)
2 212.69.63.98     17ms   19ms   50ms  TTL:254  (telehouse-gw4-lo1.idnet.net ok)
3 212.69.63.78     16ms   16ms   16ms  TTL:253  (No rDNS)
4 80.249.97.109    16ms   16ms   16ms  TTL:252  (gi4-42-75-idnet.bdr-rt3.thdo.ncuk.net bogus rDNS: host not found [authoritative])
5 80.249.97.9      17ms   22ms    *    TTL:251  (gi1-24-10-star1.core-rs2.thdo.ncuk.net bogus rDNS: host not found [authoritative])
6 80.249.99.130    17ms   16ms   17ms  TTL: 59  (www.thinkbroadband.com ok)

More if it helps?

[Gary]

traceroute to www.thinkbroadband.co.uk (80.249.99.130), 64 hops max, 72 byte packets
1  192.168.1.1 (192.168.1.1)  0.424 ms  0.187 ms  0.150 ms
2  telehouse-gw4-lo1.idnet.net (212.69.63.98)  106.241 ms  133.778 ms  10.564 ms
3  212.69.63.78 (212.69.63.78)  7.745 ms  7.860 ms  7.730 ms
4  gi4-42-75-idnet.bdr-rt3.thdo.ncuk.net (80.249.97.109)  7.697 ms  7.870 ms  7.630 ms
5  gi1-24-10-star1.core-rs2.thdo.ncuk.net (80.249.97.9)  9.167 ms  8.836 ms  8.374 ms
6  www.thinkbroadband.com (80.249.99.130)  8.168 ms  7.842 ms  8.171 ms

[Steve]

Hi All,

Just a quick update we checked the network again today and found no issues. As part of a test as well we have two FTTC lines setup on the TBB checker and both of those are showing no packet loss. As has been suggested earlier if are experiencing any issues please contact support directly so we can take a further look. including any speedtests/trace routes etc so we can get as much data as we can.

Kind regards
Simon Mulliss
IDNet support

Whilst not denying the validity of that statement, I can assure you that TBBQMs of mine,Lance's  and ZappaDPJ lines, all FTTC are showing signs of packet loss, however a BT Speedtest performed just now for my connection shows excellent throughput.

[Gary]

Ping has started...

PING www.thinkbroadband.co.uk (80.249.99.130): 56 data bytes
64 bytes from 80.249.99.130: icmp_seq=0 ttl=59 time=8.268 ms
64 bytes from 80.249.99.130: icmp_seq=1 ttl=59 time=7.856 ms
64 bytes from 80.249.99.130: icmp_seq=2 ttl=59 time=7.855 ms
64 bytes from 80.249.99.130: icmp_seq=3 ttl=59 time=7.994 ms
64 bytes from 80.249.99.130: icmp_seq=4 ttl=59 time=7.924 ms
64 bytes from 80.249.99.130: icmp_seq=5 ttl=59 time=7.801 ms
64 bytes from 80.249.99.130: icmp_seq=6 ttl=59 time=8.093 ms
64 bytes from 80.249.99.130: icmp_seq=7 ttl=59 time=8.095 ms
64 bytes from 80.249.99.130: icmp_seq=8 ttl=59 time=8.368 ms
64 bytes from 80.249.99.130: icmp_seq=9 ttl=59 time=8.160 ms

--- www.thinkbroadband.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 7.801/8.041/8.368/0.179 ms

And suddenly its all ok again.

[Simon]

Just a thought, but could this be a TBBQM issue? 

[SimonM_IDNet]

Whilst not denying the validity of that statement, I can assure you that TBBQMs of mine,Lance's  and ZappaDPJ lines, all FTTC are showing signs of packet loss, however a BT Speedtest performed just now for my connection shows excellent throughput.

Hi Steve,

That does seem odd. Again this is why we would require more information to find out whats happening with your connections and why.

I have done a 5min test on both yours and Davecollins IP addresses and so far no packet loss. About the CNN trace route that clearly left our network but the default is 30 hops maximum and there is only 19 there did it state trace complete at the end? (those no replys but passed on to another hop would mean traffic was passed on the but the ping request was either not responded to or took to long to respond to that ping request but the traffic was still passed on)

[Gary]

Just a thought, but could this be a TBBQM issue? 

Thing is when it happens Simon instead of hitting 65-68Mbps it goes from 26Mbps to 44Mbps to 30Mbps its all over the place.  Right now its ok again my end and pings are fine.

[Steve]

Thanks Simon, one does wonder what's going on, normally with that degree of packet loss showing I would expect a reduction in throughput, however 42Mbps down is good for my FTTC although if I examine them closely the packet loss disappeared again at 14:00

My live TBBQM

[Bill]

I can assure you that TBBQMs of mine,Lance's  and ZappaDPJ lines, all FTTC are showing signs of packet loss

And mine:



Happens about the same time every day (tho' perhaps a bit earlier today), ditto the yellow in the evening (though I suspect that's my exchange rather than IDNet)

Speedtests are inconclusive, sometimes bad during packet loss periods, sometimes OK.

[Gary]

My thoughput just hit the floor, sites were having issues loading.

[Gary]

Traceroute has started...

traceroute to www.idnet.com (212.69.36.10), 64 hops max, 72 byte packets
1  192.168.1.1 (192.168.1.1)  0.472 ms  0.245 ms  0.163 ms
2  telehouse-gw4-lo1.idnet.net (212.69.63.98)  21.024 ms  20.679 ms  20.877 ms
3  212.69.63.84 (212.69.63.84)  19.849 ms  19.471 ms  19.313 ms
4  redbus-gw5-gi2-1276.idnet.net (212.69.63.9)  19.346 ms  19.420 ms  19.503 ms
5  redbus-gw1-gi5-0-301.idnet.net (212.69.63.209)  20.510 ms  19.609 ms  19.803 ms
6  bob.idnet.net (212.69.36.10)  20.180 ms  7.886 ms  7.922 ms

While gw4 may not treat traces with high priority the difference between then when my speeds were wonky and now they are fine is huge. from 223.093 ms to 21.024ms

[mervl]

It looks to me as though you have to get the data at the EXACT time the packet loss is occurring: my speedtest/ping was 7Mbps down/49ms pings, and a couple of minutes later were at a normal 37Mbps down/24ms pings. Uploads don't seem to be affected though.

EDIT I monitored the router/modem - cab connection via the router GUI and that was consistent throughout.

[psp83]

Mines at the bottom of all my posts if its needed to be checked.

I also get slower down speeds when the packet loss is around, getting into the single digits sometimes.

[Gary]

It looks to me as though you have to get the data at the EXACT time the packet loss is occurring: my speedtest/ping was 7Mbps down/49ms pings, and a couple of minutes later were at a normal 37Mbps down/24ms pings. Uploads don't seem to be affected though.

That does seem to be the case my lowest was 22Mbps and now its back up in the higher 60's again. My upload speeds remain the same.

[Bill]

Mines at the bottom of all my posts if its needed to be checked.

Ditto for mine, I meant to mention that.

[colirv]

FWIW from the sunny north my speed is its usual 20-40Mbs (65Mbs at night). TBBQM shows packet loss.

[zappaDPJ]

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.