Increasing consistent small packet loss

[davecollins]

I'm done here - my migration is now underway. I'll post here when I've moved to compare experiences.

[mervl]

For what it's worth this week (unlike previous weeks when I've had the same issues as everyone else, apparently) my IDNet broadband on VDSL2 based off the red6 PoP at Stepney Green has had negligible packet loss showing off TBQM (with only the 5m known outage at 2.25pm on Tuesday, when the router failed to connect to the IDNet's server for 4 minute-apart attempts), and so far as I can see peak afternoon/evening speeds on the TB speedtester have been consistent at my max 36-38Mbps on a line capped at 40Mpbs (old package). Many issues, not a single one, methinks. Strangely I always get weird 1-3Mpbs results on the 6x test, but I tend to blame the router which thinks I'm getting a DoS attack, presumably! And using the mobile Android tester via wifi again gives a pathetic result, but then wireless gives the the same result as wired on the PC.

[Gary]

Much better here this afternoon, and so far less red on the graphs too mainly.

[davecollins]

Ironically I'm seeing the same thing too. But the last three months have taught me one thing: this won't last.

I've been very patient, and so has everyone else here. But enough.

[Simon_idnet]

Dave, it certainly will last. As I've explained to you personally, many times, we are continually working at getting this right and we will succeed. We're aiming at engineering our network to absorb these traffic-generating events, with a particular eye on the upcoming football World Cup.

[davecollins]

I hope you're right - but I've been waiting (fairly) patiently for literally months now. Each time there's been a fix, things have improved and then the problem has returned.

The reason you've had to explain this personally to me many times is that the situation has not been resolved! I suspect and hope that you will succeed, but in the meantime these issues have had a terrible impact on the quality of the video conferencing with our US clients and even with a webinar we were holding.

I can no longer afford to sit and wait in good faith for this to be fixed.

[zappaDPJ]

Well I don't know about anybody else but my patience has run out. I'm currently experiencing 88% packet loss so I can't even browse the net.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>tracert google.co.uk

Tracing route to google.co.uk [173.194.41.119]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    11 ms    11 ms    12 ms  telehouse-gw3-lo1.idnet.net [212.69.63.47]
  3     7 ms     7 ms     7 ms  212.69.63.82
  4    15 ms    17 ms     *     redbus-gw2-gi3-331.idnet.net [212.69.63.5]
  5     *        *        *     Request timed out.
  6    20 ms    20 ms     *     209.85.255.78
  7     *        *        *     Request timed out.
  8     *       24 ms     *     lhr08s02-in-f23.1e100.net [173.194.41.119]
  9    21 ms     *        *     lhr08s02-in-f23.1e100.net [173.194.41.119]
10    24 ms    24 ms     *     lhr08s02-in-f23.1e100.net [173.194.41.119]
11    17 ms     *        *     lhr08s02-in-f23.1e100.net [173.194.41.119]
12     *        *        *     Request timed out.
13     *        *       19 ms  lhr08s02-in-f23.1e100.net [173.194.41.119]

Trace complete.

C:\Users\zappaDPJ>ping google.co.uk -n 25

Pinging google.co.uk [173.194.41.87] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 173.194.41.87: bytes=32 time=22ms TTL=58
Reply from 173.194.41.87: bytes=32 time=20ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.194.41.87: bytes=32 time=22ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.41.87:
    Packets: Sent = 25, Received = 3, Lost = 22 (88% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 22ms, Average = 21ms

C:\Users\zappaDPJ>

[Gary]

Something's not right but my speed test is fine  Edit nope its all ok now

Download speed achieved during the test was - 67.32 Mbps
For your connection, the acceptable range of speedsis 55.6 Mbps-69.5 Mbps .
Additional Information:
IP Profile for your line is - 69.5 Mbps

[Bill]

I'm having problems too- tbb and BTw tests are slow (the BT one is showing as red, first time I've ever seen that), speedtest.net just spins its wheels at "connecting", some US sites I use are also very slow, and IPv6 is a waste of time atm:




IPv4 about normal so far.

[Aaron]

Experiencing massive packet loss right now.

Code Select Expand

C:\Users\Aaron>pathping 213.155.155.233

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
  0  Heimdall.home.gateway [192.168.1.1]
  1  192.168.1.254
  2  212.69.63.39
  3  212.69.63.88
  4  ge-2-25.r02.londen03.uk.bb.gin.ntt.net [213.130.48.161]
  5  ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.40]
  6  ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.198]
  7  ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
  8  ae-0.teliasonera.amstnl02.nl.bb.gin.ntt.net [129.250.8.66]
  9     *        *        *
Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Heimdall.home.gateway [192.168.1.1]
                                0/ 100 =  0%   |
  1    3ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  212.69.63.39
                                0/ 100 =  0%   |
  3   17ms     0/ 100 =  0%     0/ 100 =  0%  212.69.63.88
                                3/ 100 =  3%   |
  4   17ms     4/ 100 =  4%     1/ 100 =  1%  ge-2-25.r02.londen03.uk.bb.gin.ntt.net [213.130.48.161]
                                0/ 100 =  0%   |
  5   21ms     5/ 100 =  5%     2/ 100 =  2%  ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.40]
                                0/ 100 =  0%   |
  6   27ms     7/ 100 =  7%     4/ 100 =  4%  ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.198]
                                0/ 100 =  0%   |
  7   27ms     3/ 100 =  3%     0/ 100 =  0%  ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
                               24/ 100 = 24%   |
  8   61ms    27/ 100 = 27%     0/ 100 =  0%  ae-0.teliasonera.amstnl02.nl.bb.gin.ntt.net [129.250.8.66]

Trace complete.

[Gary]

Speed test working fine here, Bill.



Ping has started...

PING bbc.co.uk (212.58.244.18): 56 data bytes
64 bytes from 212.58.244.18: icmp_seq=0 ttl=57 time=8.191 ms
64 bytes from 212.58.244.18: icmp_seq=1 ttl=57 time=8.484 ms
64 bytes from 212.58.244.18: icmp_seq=2 ttl=57 time=8.811 ms
64 bytes from 212.58.244.18: icmp_seq=3 ttl=57 time=8.625 ms
64 bytes from 212.58.244.18: icmp_seq=4 ttl=57 time=8.921 ms
64 bytes from 212.58.244.18: icmp_seq=5 ttl=57 time=8.271 ms
64 bytes from 212.58.244.18: icmp_seq=6 ttl=57 time=8.596 ms
64 bytes from 212.58.244.18: icmp_seq=7 ttl=57 time=8.894 ms
64 bytes from 212.58.244.18: icmp_seq=8 ttl=57 time=8.401 ms
64 bytes from 212.58.244.18: icmp_seq=9 ttl=57 time=8.396 ms

--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.191/8.559/8.921/0.242 ms

No packet loss either. I have no idea, I suspect this maybe outside IDNet.

[Bill]

I suspect this maybe outside IDNet.

It could easily be the "local" problem that Zap and I are lumbered with (I suspect it is), but I can't think of any reliable way to tell

[Gary]

No idea, Bill.  Everything is fine at my end. There was a fault with 01773 numbers at 8PM according to Zens page but that's been fixed.   

[Bill]

Now even my email is timing out



edit- but only the IDNet accounts.... which doesn't sound local.

[zappaDPJ]

I've just attempted to email IDNet support my best wishes but I can neither send or receive mail.

[Gary]

Now even my email is timing out



edit- but only the IDNet accounts.... which doesn't sound local.

Email has been behaving oddly for a while there was a post about it earlier. Maybe an issue with the new DNS servers? I can send fine though now.

[Simon]

Aaron doesn't appear to be on an IDNet connection (unless I'm being characteristically thick), and is still experiencing packet loss:

http://www.idnetters.co.uk/forums/index.php/topic,31600.msg727142.html#msg727142

Doesn't that suggest an outside issue?

My connection seems fine on ADSL2+.

[Aaron]

I am on IDNet, the 2 IP addresses aren't resolving in my tracerts at the moment  (212.69.63.39   212.69.63.88)

[Bill]

Getting about 8% packet loss on 100 pings to bbc.co.uk.

[Simon]

I am on IDNet, the 2 IP addresses aren't resolving in my tracerts at the moment  (212.69.63.39   212.69.63.88)

OK, sorry. 

[Gary]

The forum has been slow that I have noticed. My speeds are still fine though and no packetloss. At this point I have no idea.

[Simon]

Again, I've not noticed the forum being slow on ADSL2+.

[Bill]

The forum has been slow that I have noticed. My speeds are still fine though and no packetloss. At this point I have no idea.

Haven't noticed any difference with the forum, still quick here

[Gary]

Haven't noticed any difference with the forum, still quick here

Forums fine again now, Bill. I suspect we will find out what this is later, maybe a failure at a node like before? I cannot say for sure but I think people leap to 'its idnet' because of the issues we have had when sometimes is nothing to do with them at all, but tbh its anyones guess. Edit: now forum is slow again...looking at Craig's tgere are no red  curtains apart from joes which is usual on his one.

[Bill]

Everything except email seems back to normal now (well, as normal as ever on my line at this time of night )

Fortunately the IDNet accounts aren't my primary ones... I've sent a couple of test mails to and from another account, I'll see what happens to them.