Performance Woes Hamper PlusNet Users as New Network Takes Blame

[#1]

Nothing special at 8am for me, just awful all day. Looks like something was happening at 4am and 1pm though.

[#2]

Hi everyone,

We're really sorry about the problems people have been seeing and some are continuing to see. To those of you who have TBB monitors set up it would be really useful if you could do a couple of things please, could you post the link to the live graph and then in the same post either post which gateway this page returns or post a traceroute to 8.8.8.8

http://usertools.plus.net/@gateway

If we can put this data together it will really help in seeing if the changes we're making are improving things and also to help us to see when it's fixed.

Thanks

[#3]

An update on the Static IP, still 0% packet loss since being switched to it.

This of course not counting the maintenance period when it was unusable between 3am and 9am.

[#4]

OK, thanks for the response Dave.

This is my live graph:

And the response from the Gateway checker is:

Which gateway
Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.910 ms
*
*
*

Hope this helps.

[#5]

24hrs on the static IP to gateway ptw-bng-01 and not much packet loss apart from the maintenance period.

 http://www.thinkbroadband.com/ping/share/87e0e60c3a7c7b6fd80e7b1561a3269b.html

[#6]

Here's mine

Which gateway

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

• core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.084 ms
• *
• *
• *

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets

1  192.168.1.1 (192.168.1.1)  1.606 ms  0.963 ms  0.781 ms

2  * * *

3  * 137.hiper04.sheff.dial.plus.net.uk (195.166.143.137)  11.352 ms  10.003 ms

4  be3-3104.psb-ir01.plus.net (195.166.143.136)  11.142 ms  10.606 ms  11.210 ms

5  195.99.125.134 (195.99.125.134)  10.508 ms

    core1-be1.southbank.ukcore.bt.net (195.99.125.130)  10.328 ms  10.708 ms

6  peer1-xe-11-0-1.faraday.ukcore.bt.net (213.121.193.201)  10.893 ms

    62.172.103.193 (62.172.103.193)  10.682 ms

    62.172.103.27 (62.172.103.27)  11.498 ms

7  109.159.253.67 (109.159.253.67)  11.232 ms

    195.99.126.105 (195.99.126.105)  10.518 ms  10.884 ms

8  72.14.234.65 (72.14.234.65)  10.248 ms

    216.239.54.247 (216.239.54.247)  10.050 ms

    216.239.54.239 (216.239.54.239)  11.210 ms

9  216.239.57.131 (216.239.57.131)  11.429 ms

    216.239.58.107 (216.239.58.107)  12.616 ms

    216.239.57.67 (216.239.57.67)  12.253 ms

10  google-public-dns-a.google.com (8.8.8.8)  12.521 ms  11.450 ms  11.935 ms

[#7]

Since 8pm, my connection has returned to its "normal" (of the last month) pattern of low level but still noticeable contiunual packet loss.

Using gateway psb-ir01 (Southbank Point of Presence)

tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_VR600
2 * * * Request timed out.
3 * * * Request timed out.
4 7 ms 6 ms 7 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 7 ms 7 ms 8 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 8 ms 8 ms 7 ms peer1-et-10-1-0.telehouse.ukcore.bt.net [195.99.127.3]
7 7 ms 8 ms 7 ms 195.99.126.105
8 8 ms 7 ms 7 ms 72.14.232.187
9 8 ms 10 ms 8 ms 216.239.57.83
10 8 ms 8 ms 7 ms google-public-dns-a.google.com [8.8.8.8]

[#8]

• core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.118 ms
• *
• *
• *

1 <1 ms <1 ms <1 ms gw [192.168.1.1]
2 * * * Request timed out.
3 7 ms 7 ms 7 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 6 ms 6 ms 6 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 8 ms 8 ms 8 ms 195.99.125.134
6 9 ms 8 ms 9 ms 213.121.193.207
7 6 ms 6 ms 6 ms 195.99.126.185
8 8 ms 8 ms 8 ms 216.239.54.223
9 9 ms 9 ms 9 ms 209.85.142.225
10 8 ms 8 ms 9 ms google-public-dns-a.google.com [8.8.8.8]

[#9]

Unfortunately I do not have a TBB live graph. But here is the gateway and a couple of traceroutes (first one timed out on hop 3, second one did not).

core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 3.946 ms

1 1 ms <1 ms <1 ms BTHUB5 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 14 ms 14 ms 15 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 13 ms 13 ms 13 ms 195.99.125.140
6 14 ms 14 ms 13 ms 195.99.127.81
7 14 ms 14 ms 14 ms 109.159.253.67
8 14 ms 13 ms 13 ms 216.239.54.251
9 23 ms 27 ms 40 ms 216.239.57.47
10 15 ms 15 ms 15 ms google-public-dns-a.google.com [8.8.8.8]

1 <1 ms <1 ms <1 ms BTHUB5 [192.168.1.254]
2 * * * Request timed out.
3 * * 15 ms 133.hiper04.sheff.dial.plus.net.uk [195.166.143.133]
4 14 ms 14 ms 14 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 13 ms 13 ms 12 ms 195.99.125.140
6 14 ms 13 ms 14 ms 195.99.127.81
7 14 ms 15 ms 14 ms 109.159.253.67
8 14 ms 13 ms 14 ms 216.239.54.251
9 15 ms 15 ms 15 ms 216.239.57.47
10 15 ms 15 ms 15 ms google-public-dns-a.google.com [8.8.8.8]

[#10]

@dave: here is a TBB graph which is pretty much OK. (It has been worse, but nowhere near as bad as others). I'm on a static IP, in Edinburgh:

Custom diagnostic check on IP 212.56.103.219

Array

    [1] =>  7  core3-te0-0-0-15.faraday.ukcore.bt.net (213.121.193.164)  3.017 ms
    [2] =>  8  acc1-10GigE-0-0-0-2.l-far.21cn-ipp.bt.net (109.159.249.8)  4.184 ms
    [3] =>  9  peer2-ae-1.redbus.ukcore.bt.net (195.99.126.97)  3.768 ms
    [4] => 10  ae2.pcl-cr02.plus.net (195.166.129.7)  4.119 ms
    [5] => 11  ae1.ptw-cr02.plus.net (195.166.129.2)  4.274 ms
    [6] => 12  te8-1.ptn-gw02.plus.net (212.159.0.107)  4.239 ms
    [7] => 13  link-b-central10.ptn-ag01.plus.net (212.159.2.131)  6.464 ms

TBB live graph (I hope):

http://www.thinkbroadband.com/ping/share/89493edf03886b2dcd280962c6420627.html

[#11]

Currently on a static IP and not showing any packet noticeable loss.

Historical: https://f8lure.mouselike.org/index.asp?DoAction=HistoricList&Host=ipv4.homedsl.co.uk&FBMode=True

Live: https://f8lure.mouselike.org/proxyfirebrick.asp?ID=57253

You are currently connected to gateway ptw-bng01.

This is located in Telehouse West.

$ traceroute -I 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets
 1  homedsl.co.uk (192.168.0.1)  1.703 ms  1.650 ms  1.345 ms
 2  192.168.0.250 (192.168.0.250)  2.663 ms  1.851 ms  1.662 ms
 3  192.168.1.250 (192.168.1.250)  2.551 ms  2.586 ms  2.513 ms
 4  lo0.11.central11.ptw-bng01.plus.net (195.166.128.171)  23.519 ms  23.889 ms  24.601 ms
 5  irb.11.ptw-cr01.plus.net (84.93.249.17)  24.673 ms  26.615 ms  31.603 ms
 6  72.14.222.97 (72.14.222.97)  24.353 ms  25.858 ms  25.753 ms
 7  216.239.48.77 (216.239.48.77)  29.942 ms  25.867 ms  24.783 ms
 8  216.239.58.73 (216.239.58.73)  29.384 ms  26.521 ms  25.908 ms
 9  google-public-dns-a.google.com (8.8.8.8)  26.334 ms  28.218 ms  25.759 ms

[#12]

I don't wish to speak too soon but, since last night I am now back to 0% packet loss and the browser has stopped stuttering and coughing. Streams are streaming and email coming in unabated.

Hooray?

Which gateway

You are currently connected to gateway psb-ir01.

This is located in Southbank Point of Presence.

[#13]

---

@Flabula wrote:

I don't wish to speak too soon but, since last night I am now back to 0% packet loss and the browser has stopped stuttering and coughing. Streams are streaming and email coming in unabated.

Hooray?

---

Same here. Fingers crossed!

You are currently connected to gateway pcn-ir01.

This is located in Colindale Point of Presence.

[#14]

Ive had 2 disconnections from 6am to 8am this morning, must be work being done

[#15]

Already known to @dave, but for the the purpose of this thread, here's my live graphing:

Starting to creep in again this morning. Doesn't look as severe from another destination (this one isn't live) but suspect it will ramp up as the day progresses looking at the ticks that are starting to show:

Pingtest coming back clean at the time of writing:

Gateway check as follows, the IR isn't responding to ICMP:

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

    core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.995 ms
    *
    *
    *

Save

Save

Save

Save

Traceroute:

tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     7 ms     6 ms     7 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    16 ms    16 ms    13 ms  133.hiper04.sheff.dial.plus.net.uk [195.166.143.133]
  4    18 ms    19 ms    19 ms  be3-3102.pcn-ir02.plus.net [195.166.143.132]
  5    15 ms    17 ms    16 ms  195.99.125.144
  6    17 ms    18 ms    30 ms  195.99.127.87
  7    13 ms    14 ms    15 ms  195.99.126.185
  8    17 ms    16 ms    21 ms  216.239.54.247
  9    16 ms    16 ms    15 ms  216.239.57.53
 10    17 ms    16 ms    15 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.