gateway checker down ?

[#1]

The fix the gateway checker 'could not identify your gateway' problem Plusnet need to change the reverse DNS entry for
link3-central10.pcl-gw01.plus.net (84.93.249.100)
to reflect that it should say pcl-bng02.

[#2]

I think the reverse DNS entries are correct, the problem is that the penultimate hop doesn't respond in the traceroute from the usertools gateway checker to you. This traceroute is in the opposite direction to a traceroute command run on your computer, and many of the hops will have different IP addresses. In Hairy McBiker traceroutes, there weren't the last couple of hops missing, but that's presumably because there were two different length routes mixed together, plus Hairy McBiker's wan IP must respond to pings.

[#3]

Yes my wan ip responds to pings to allow the BB ping monitor.

[#4]

just do any outbound traceroute and you find your gateway on first external hop.

[#5]

Just to add to the responding to pings discussion,
My router is configured to ONLY respond to ping requests from known sources (such as the TBB monitor, HE tunnelbroker, Pingtest, IPv6-test ping test, etc) but silently drops (and logs) all other ping requests.
Running the Plusnet Gateway Checker, does indeed send two ICMP ping requests from 84.92.0.74, two seconds apart.
The gateway checker always gives me the expected Plusnet gateway name,  despite those ping requests being silently dropped.
Therefore responding to ICMP pings will give a more complete reverse traceroute, but is not necessary for the Gateway Checker to work.

[#6]

Quote from: spraxyt

To fix the gateway checker 'could not identify your gateway' problem Plusnet need to change the reverse DNS entry for link3-central10.pcl-gw01.plus.net (84.93.249.100) to reflect that it should say pcl-bng02.

Plusnet are aware this change is needed and it is in hand under task ref:82558.

Quote from: purleigh

Just to add to the responding to pings discussion, Running the Plusnet Gateway Checker, does indeed send two ICMP ping requests from 84.92.0.74, two seconds apart.

The gateway checker sends one ping to each hop (up to 9) and waits 2 seconds for an answer before stopping or trying the next hop as appropriate. So receiving two pings implies your router is at hop 8. The checker waits two seconds without an answer, so tries to find the destination at hop 9. Obviously that too goes unanswered but as the hop limit is reached the checker stops. However the gateway will have been passed so (if recognised) the answer to the request will be given.
Edit: add final sentence.