Gateway Checker Update

[#1]

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.
    acc2-10GigE-0-4-0-10.l-far.21cn-ipp.bt.net (109.159.249.134) 3.583 ms
    195.99.126.99 (195.99.126.99) 2.606 ms
    ae2.pcl-cr01.plus.net (195.166.129.6) 49.815 ms
    ae1.ptw-cr01.plus.net (195.166.129.0) 3.444 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.196) 3.438 ms

[#2]

Thanks for the report.
David

[#3]

I can't believe how long it's taking them to fix what should have been on the check list of things to do when that end point was added!

[#4]

Just got this
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.
link11-central10.pcl-gw01.plus.net (84.93.249.212) 3.794 ms

Alan

[#5]

Thanks. I think that's one we haven't seen before.
David

[#6]

just got this on checking gateway
    xe-1-2-1.mpr1.lhr18.uk.zip.zayo.com (64.125.29.217) 4.525 ms
    xe-5-0-0.mpr1.lhr1.uk.zip.zayo.com (64.125.29.114) 4.508 ms
    *
    213.137.183.97 (213.137.183.97) 4.857 ms
    core4-te0-8-0-1.faraday.ukcore.bt.net (62.6.201.196) 5.154 ms
    acc2-10GigE-0-1-0-1.l-far.21cn-ipp.bt.net (109.159.249.146) 4.478 ms
    195.99.126.99 (195.99.126.99) 4.548 ms
just gone onto thinkbroadband to do speed test and it says am on BT when it normally says on plusnet

[#7]

What is going on?

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.    213.248.82.250 (213.248.82.250) 2.214 ms    166-49-211-239.eu.bt.net (166.49.211.239) 2.039 ms    core2-te0-15-0-13.ilford.ukcore.bt.net (109.159.255.98) 7.262 ms    194.72.31.139 (194.72.31.139) 4.571 ms    195.99.126.139 (195.99.126.139) 3.907 ms    ae2.ptw-cr02.plus.net (195.166.129.5) 3.876 ms    ae1.pcl-cr02.plus.net (195.166.129.3) 3.818 ms

This may be useful:

C:\Users\John>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.6.9]
over a maximum of 30 hops:
  1    <1 ms     1 ms     1 ms  tg582 [192.168.1.254]
  2    10 ms     9 ms     9 ms  lo0.10.Central10.pcl-bng04.plus.net [195.166.130.177]
  3    10 ms    10 ms     9 ms  irb.10.PCL-CR01.plus.net [84.93.249.81]
  4    10 ms    10 ms    10 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  5    10 ms     9 ms     9 ms  cdns01.plus.net [212.159.6.9]
Trace complete.

[#8]

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

[#9]

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) 25.120 ms
xe-5-0-0.mpr1.lhr1.uk.zip.zayo.com (64.125.29.114) 25.085 ms
*
213.137.183.103 (213.137.183.103) 25.035 ms
core3-te0-8-0-1.faraday.ukcore.bt.net (62.6.201.192) 25.072 ms
peer1-et-1-1-0.telehouse.ukcore.bt.net (213.121.193.161) 25.054 ms
195.99.126.139 (195.99.126.139) 25.050 ms
Alan

[#10]

Quote from: spoon

What is going on?

It looks like Rackspace have introduced additional routing within their cloud which has added extra hops to the path to user gateways. Jelv's router is now hop 15, mine is hop 17. The checker currently stops at 13. It's possible the additional hops are temporary, whilst maintenance is carried out, but in the meantime I'll increase the checker's maximum hop allowance which should fix the current problem.
(goatty2 apparently having a BT IP is a different issue - more on that later.)
David

[#11]

Just got this, looks similar to the post by alanc.

xe-1-2-1.mpr1.lhr18.uk.zip.zayo.com (64.125.29.217) 4.803 ms
xe-5-0-0.mpr1.lhr1.uk.zip.zayo.com (64.125.29.114) 4.959 ms
*
213.137.183.101 (213.137.183.101) 7.380 ms
core3-te0-8-0-1.faraday.ukcore.bt.net (62.6.201.192) 5.076 ms
peer6-hu0-18-0-1.telehouse.ukcore.bt.net (213.121.193.177) 5.509 ms
195.99.126.183 (195.99.126.183) 4.747 ms

[#12]

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

[#13]

Quote from: spraxyt

... in the meantime I'll increase the checker's maximum hop allowance which should fix the current problem.

I've increased the maximum hops to 20 now - could users getting gateway identification failures earlier please check again.
David

[#14]

OK for me right now

[#15]

OK for me now as well.
(You do realise you've just broken Plusnet's standard operating procedures by fixing the issue straight away. Left to Plusnet a simple change like that would have taken months!)