Gateway Checker Update

[#1]

Thanks, that final hop should be pcl-bng02. Still awaiting Plusnet updating its DNS entry.
David

[#2]

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 Update topic in the Community Announcements forum will help us to diagnose the problem.
ae2.ptw-cr02.plus.net (195.166.129.5) 3.259 ms
*
*

[#3]

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-10.telehouse.ukcore.bt.net (109.159.254.104) 4.796 ms
195.99.126.183 (195.99.126.183) 6.033 ms
*
*
Okay I guess this is down to the DSN/Networking issues that have been ongoing since just after midnight. So not a real issue.

[#4]

Quote from: georgelnx

Okay I guess this is down to the DSN/Networking issues that have been ongoing since just after midnight. So not a real issue.

Yes, I think you are right. Until things return to normal please ignore any errors from the gateway checker.
David

[#5]

The gateway checker seems to be working OK again now the network and/or DNS issues have been fixed.
David

[#6]

Gateway checker gives me this
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 Update topic in the Community Announcements forum will help us to diagnose the problem.
peer6-te0-9-0-15.telehouse.ukcore.bt.net (109.159.252.59) 3.502 ms
195.99.126.183 (195.99.126.183) 6.715 ms
ae1.pcl-cr02.plus.net (195.166.129.3) 3.669 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 3.635 ms

[#7]

Ditto^^^^^^^
acc2-10GigE-0-3-0-2.l-far.21cn-ipp.bt.net (109.159.249.172) 3.800 ms
195.99.126.99 (195.99.126.99) 2.503 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 3.333 ms

[#8]

Thanks. A month has now passed since these IPs were flagged up for attention. I guess it's a low priority task.
David

[#9]

Why on earth after all these years they still haven't got setting up the DNS entries as part of the tick list when new end points are set up is beyond me!

[#10]

I've just lost connection and the troubleshooter tells me it was a gateway problem when checking again I got this
acc2-10GigE-0-3-0-2.l-far.21cn-ipp.bt.net (109.159.249.172) 4.702 ms
195.99.126.99 (195.99.126.99) 3.444 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 4.145 ms
No idea if it's related tho' as I don't understand such things.

[#11]

I think the gateway that refers to is probably your router rather than the handover point to Plusnet. The latter, which the checker refers to a your gateway was unchanged after the incident.
David

[#12]

Just got this from the gateway checker,
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 Update topic in the Community Announcements forum will help us to diagnose the problem.
ae2.ptw-cr02.plus.net (195.166.129.5) 35.634 ms
ae1.pcl-cr02.plus.net (195.166.129.3) 3.247 ms
link3-central10.pcl-gw01.plus.net (84.93.249.164) 3.111 ms
Thanks.

[#13]

Thanks, the problem has been reported.
David

[#14]

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-21.telehouse.ukcore.bt.net (109.159.254.46) 3.878 ms
195.99.126.183 (195.99.126.183) 3.868 ms
link3-central10.pcl-gw01.plus.net (84.93.249.196) 3.863 ms

[#15]

Thanks, problem noted.
David