Gateway Checker Update

[#1]

just to let you know TBB now says I am on plusnet  but speedtest.net not sorted it yet

[#2]

OT: It will take speedtest.net a couple of weeks at least, due to how often the database they depend on is updated.

[#3]

Thanks Bob.
Though misidentification of ISP is a different issue from the main purpose of this thread, the original post started with reporting a Checker problem (our Rackspace service provider added several extra hops to the trace causing the checker to stop searching too soon)..I fixed the latter at the weekend; and the former is on the way to being resolved so concluding the issue here is not unreasonable.
David

[#4]

Getting this tonight on the Gateway Checker. Also seems to be an issue with pages loading slowly and missing images. Tbb speedtest shows no issues, good speeds 1X, 6X and upstream is fine.

    ae-1.r00.londen10.uk.bb.gin.ntt.net (129.250.3.31) 5.587 ms
    82.112.101.74 (82.112.101.74) 3.204 ms
    166-49-211-245.eu.bt.net (166.49.211.245) 4.653 ms
    109.159.254.143 (109.159.254.143) 7.481 ms
    peer1-xe2-1-0.telehouse.ukcore.bt.net (109.159.254.136) 5.633 ms
    195.99.126.139 (195.99.126.139) 4.419 ms
    link11-central10.pcl-gw01.plus.net (84.93.249.212) 3.890 ms

[#5]

Thanks, that is on the list to be corrected.
According to Bob,that gateway is ptn-bng01. There is at least one mention on other boards of performance issues on that gateway. For example here.
David

[#6]

Hi I've got this message when checking gateway
    195.99.126.139 (195.99.126.139) 3.219 ms
    link11-central10.pcl-gw01.plus.net (84.93.249.212) 4.704 ms
jono

[#7]

Thanks, that gateway is ptn-bng01. On the list to have its DNS entry updated.
David

[#8]

just been on gateway checker
    core3-te0-0-0-15.faraday.ukcore.bt.net (213.121.193.164) 3.074 ms
    acc2-10GigE-0-1-0-1.l-far.21cn-ipp.bt.net (109.159.249.146) 4.144 ms
    195.99.126.99 (195.99.126.99) 3.424 ms
    ae1.ptw-cr02.plus.net (195.166.129.2) 15.522 ms
    ae2.ptw-cr01.plus.net (195.166.129.4) 3.832 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.196) 4.568 ms
been onTBB and still on same isp

[#9]

Thanks. That gateway IP is on the list to have its identification corrected.
David

[#10]

I just got this ? for some reason connection dropped at 22.15 last night
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 Update topic in the Community Announcements forum will help us to diagnose the problem.
    195.99.126.139 (195.99.126.139) 2.477 ms
    ae2.ptw-cr02.plus.net (195.166.129.5) 4.562 ms
    ae1.pcl-cr02.plus.net (195.166.129.3) 2.983 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.164) 4.135 ms

[#11]

Im getting this

    core3-hu0-3-0-0.faraday.ukcore.bt.net (213.121.193.160) 3.177 ms
    acc2-10GigE-0-3-0-1.l-far.21cn-ipp.bt.net (109.159.249.170) 4.428 ms
    195.99.126.99 (195.99.126.99) 2.989 ms
    ae1.ptw-cr02.plus.net (195.166.129.2) 2.571 ms
    link12-central10.pcl-gw02.plus.net (84.93.249.54) 22.198 ms

[#12]

It'd be nice if Plusnet also added some reverse DNS entries for the IP addresses you get in outbound traceroutes or from your router. I'm collecting an increasing list of IPs that are more difficult to work out yourself.
I think I've deduced the gateways correctly for these IPs:
195.166.130.179 pcl-bng04
195.166.130.192 ptn-bng02
195.166.130.205 ptw-bng02
195.166.130.211 ptn-bng01
195.166.130.216 ptw-bng01
195.166.130.220 ptn-bng01

[#13]

Any chance plusnet can fix the Gateway Checker or what.

[#14]

There is nothing wrong with the Gateway checker. It is the lack of rDNS entries for the Gateways that means their names aren't returned by the checker.

[#15]

Reporting as requested.

    core1-te0-0-0-10.ealing.ukcore.bt.net (109.159.254.97) 4.995 ms
    peer6-te0-10-0-20.telehouse.ukcore.bt.net (109.159.254.255) 4.046 ms
    195.99.126.183 (195.99.126.183) 3.622 ms
    link12-central10.pcl-gw02.plus.net (84.93.249.54) 5.272 ms
CJC1942