Gateway Checker Update

[#1]

well mine got more

    xe-1-2-1.mpr1.lhr18.uk.zip.zayo.com (64.125.29.217) 2.835 ms
    xe-5-0-0.mpr1.lhr1.uk.zip.zayo.com (64.125.29.114) 2.817 ms
    *
    213.137.183.97 (213.137.183.97) 3.291 ms
    core4-te0-8-0-1.faraday.ukcore.bt.net (62.6.201.196) 3.568 ms
    acc2-10GigE-0-1-0-1.l-far.21cn-ipp.bt.net (109.159.249.146) 2.989 ms
    195.99.126.99 (195.99.126.99) 2.974 ms
    ae1.ptw-cr02.plus.net (195.166.129.2) 3.958 ms
    ae2.ptw-cr01.plus.net (195.166.129.4) 3.944 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.196) 4.258 ms

[#2]

Quote from: goatty2

just gone onto thinkbroadband to do speed test and it says am on BT when it normally says on plusnet

and

Quote from: goatty2

just been on speedtest.net and that says i am on BT

and

Quote from: goatty2

just been on http://whois.domaintools.com/ and it says i am on plusnet

With goatty2's cooperation ( thanks  ) I have established the affected IP is within a range reassigned from BT.  IP registration details appear to have been updated but it seems TBB and speedtest.net have still to catch up.
These IPs were previously UK based so country-specific sites such as iPlayer should not be affected by the change.
David

[#3]

Quote from: goatty2

link3-central10.pcl-gw01.plus.net (84.93.249.196) 4.258 ms

Thanks. That IP is on the list for DNS correction.
David

[#4]

Quote from: spraxyt

With goatty2's cooperation ( thanks  ) I have established the affected IP is within a range reassigned from BT.  IP registration details appear to have been updated but it seems TBB and speedtest.net have still to catch up.

Might be worth starting a new thread on this. I can probably get it fixed fairly speedily.

[#5]

Bob,

Quote from: Bob

pcl-bng02 I believe. I've notified the relevant parties.

Why is this still not fixed?

[#6]

The engineer that sorted the last bunch has recently shifted roles and so the request fell by the wayside. As it doesn't have a direct affect on connectivity it's understandably low priority, but I've not lost sight of it and am trying to get it sorted.
Of course, there's a wider question around why these always seem to slip through the gap, but we'll leave that for another day

[#7]

Which gateway am I connected to:
ae-1.r00.londen10.uk.bb.gin.ntt.net (129.250.3.31) 4.835 ms
82.112.101.74 (82.112.101.74) 2.825 ms
166-49-211-249.eu.bt.net (166.49.211.249) 2.794 ms
core4-BE3.faraday.ukcore.bt.net (213.121.193.174) 4.787 ms
acc1-te0-0-0-10.l-far.21cn-ipp.bt.net (109.159.249.56) 4.782 ms
peer2-ae-1.redbus.ukcore.bt.net (195.99.126.97) 4.742 ms
ae1.ptw-cr01.plus.net (195.166.129.0) 4.756 ms
link11-central10.pcl-gw01.plus.net (84.93.249.212) 4.739 ms

[#8]

Thanks, hopefully that IP 84.93.249.212 has been added to the correction list.
David

[#9]

But the gateway is reported as being 195.166.130.221.
see attachment.

[#10]

no it isn't - that IP isn't the Plusnet gateway

[#11]

What is it then? The IP address belongs to PN. I haven't seen another hop between my router and the gateway before. I am aware that BT's kit isn't listed within trace routes, but I have always seen the second hop as the gateway.

[#12]

As Spraxyt posted - the first one after your router which is as shown on your picture
pcl-ag07 [84.93.249.209]

[#13]

It is the gateway IP, it's just a different interface. The corresponding reverse trace for 195.166.130.221 is as follows:

Outbound trace to the customer for the above. The inbound IP to the customer is also wrong:
Tracing route to [REDACTED].dyn.plus.net [REDACTED]
over a maximum of 30 hops:
  1    33 ms    23 ms    27 ms  10.200.200.200
  2    24 ms    23 ms    24 ms  84-93-224-141.plus.net [84.93.224.141]
  3    25 ms    24 ms    24 ms  84-93-224-132.plus.net [84.93.224.132]
  4    40 ms    24 ms    27 ms  84-93-224-133.plus.net [84.93.224.133]
  5    27 ms    25 ms    24 ms  84-93-224-26.plus.net [84.93.224.26]
  6    32 ms    32 ms    32 ms  gi1-22.pcl-gw01.plus.net [84.93.224.49]
  7    90 ms    31 ms    38 ms  ae3.pcl-cr01.plus.net [195.166.129.40]
  8    31 ms    32 ms    45 ms  ae2.pcl-cr02.plus.net [195.166.129.7]
  9    30 ms    31 ms    33 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
 10    32 ms    34 ms    33 ms  link11-central10.pcl-gw01.plus.net [84.93.249.212]
 11    48 ms    45 ms    48 ms  [REDACTED].dyn.plus.net [REDACTED]
Trace complete.

84.93.249.212 is PTN-BNG01 I believe.
Edit: Which means 84.93.249.209 is wrong too. That's a core router and not a gateway looking at the traceroute.

[#14]

That is what I found strange.

[#15]

Whoops

Quote

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.     xe-1-2-1.mpr1.lhr18.uk.zip.zayo.com (64.125.29.217) 5.067 ms     xe-5-0-0.mpr1.lhr1.uk.zip.zayo.com (64.125.29.114) 3.995 ms     *     213.137.183.97 (213.137.183.97) 4.426 ms     core4-te0-18-0-1.faraday.ukcore.bt.net (62.6.201.198) 4.980 ms     peer1-xe-11-1-0.faraday.ukcore.bt.net (213.121.193.181) 3.511 ms     195.99.126.183 (195.99.126.183) 7.364 ms     link11-central10.pcl-gw01.plus.net (84.93.249.212) 4.116 ms

Tracing route to bbc.co.uk [212.58.244.20] over a maximum of 30 hops:
  1    <1 ms    1 ms    1 ms  home.gateway.home.gateway [192.168.1.254]
  2    13 ms    13 ms    13 ms  195.166.130.221
  3    14 ms    18 ms    13 ms  link10-central10.pcl-gw02.plus.net [84.93.249.210]
  4    13 ms    13 ms    13 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  5    13 ms    13 ms    13 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  6