Gateway Checker Update

[#1]

ae1.pcl-cr01.plus.net (195.166.129.1) 2.676 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 3.103 ms

[#2]

Quote from: Riza

Btw; I do have Safeguard on if this is causing the inaccurate findings? Quote 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. peer6-te0-10-0-8.telehouse.ukcore.bt.net (109.159.254.154) 6.247 ms 195.99.126.183 (195.99.126.183) 48.126 ms ae1.pcl-cr02.plus.net (195.166.129.3) 5.183 ms ae2.pcl-cr01.plus.net (195.166.129.6) 4.650 ms link3-central10.pcl-gw01.plus.net (84.93.249.164) 4.744 ms

No, the occurrence of this message from the checker has no implications whatsoever on the performance of your router or line. The incorrect information could be likened to the wrong label being attached to the device. It's confusing but doesn't affect the device performance.
Correcting the information requires Plusnet to make what effectively is an administrative change to its "label" in DNS.
David

[#3]

Quote from: spraxyt

Thanks. Another instance of pcl-bng02 needing DNS updating. David

May I in ignorance ask, what the effects on internet use and performance of an incorrect rDNS is?

[#4]

Quote from: lucerne

May I in ignorance ask, what the effects on internet use and performance of an incorrect rDNS is?

Quote from: spraxyt

...... the occurrence of this message from the checker has no implications whatsoever on the performance of your router or line. The incorrect information could be likened to the wrong label being attached to the device. It's confusing but doesn't affect the device performance. Correcting the information requires Plusnet to make what effectively is an administrative change to its "label" in DNS.

[#5]

  Posted as requested

peer6-0-10-0-12.telehouse.ukcore.bt.net (62.172.102.25) 2.704 ms
    195.99.126.183 (195.99.126.183) 2.673 ms
    ae1.pcl-cr02.plus.net (195.166.129.3) 2.926 ms
    ae2.pcl-cr01.plus.net (195.166.129.6) 2.566 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.164) 2.659 ms
CJC1942

[#6]

Thanks, the necessary change to DNS records has been noted.
David

[#7]

Gateway not identified -

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. peer6-te0-9-0-10.telehouse.ukcore.bt.net (213.121.193.146) 3.320 ms 195.99.126.183 (195.99.126.183) 3.273 ms ae1.pcl-cr02.plus.net (195.166.129.3) 3.461 ms link3-central10.pcl-gw01.plus.net (84.93.249.164) 3.234 ms

[#8]

Thanks, this has been noted.
David

[#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.
peer6-te0-0-0-17.telehouse.ukcore.bt.net (109.159.254.140) 4.475 ms
195.99.126.183 (195.99.126.183) 3.037 ms
ae1.pcl-cr02.plus.net (195.166.129.3) 3.124 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 2.999 ms

[#10]

Thanks. That gateway should be pcl-bng02. The labelling error has been noted.
David

[#11]

peer6-te0-10-0-20.telehouse.ukcore.bt.net (109.159.254.255) 4.439 ms
195.99.126.183 (195.99.126.183) 19.462 ms
ae1.pcl-cr02.plus.net (195.166.129.3) 12.414 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 4.292 ms

[#12]

Thanks. The DNS change needed to fix the problem is on the "to do" list.
David

[#13]

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.    ae1.pcl-cr01.plus.net (195.166.129.1) 2.279 ms    ae2.pcl-cr02.plus.net (195.166.129.7) 5.628 ms    link3-central10.pcl-gw01.plus.net (84.93.249.164) 2.291 ms

wanting to check the gateway as have noticed on the ping graphs some packet loss last night 8pm-midnight, and looks like the same is happening tonight

[#14]

That trace shows your gateway is pcl-bng02. Hopefully its DNS entry will be corrected soon.
Packet loss issues are best discussed elsewhere on the forums.
David

[#15]

i just got another one
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.
    ae2.ptw-cr02.plus.net (195.166.129.5) 25.390 ms
    ae1.pcl-cr02.plus.net (195.166.129.3) 2.700 ms
    link3-central10.pcl-gw01.plus.net (84.93.249.164) 2.709 ms