Gateway checker needs updating

[#1]

I'm currently getting

Quote

Sorry, the tool currently could not identify your gateway; this does not mean that anything is wrong with your connection.

Tracert out:

C:\Users\John>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.13.50]
over a maximum of 30 hops:
  1     1 ms     2 ms     2 ms  dg834 [192.168.0.1]
  2    16 ms    17 ms    16 ms  lo0-central2.ptw-ag03.plus.net [195.166.128.48]
  3   233 ms   318 ms   215 ms  gi1-16-321.ptw-gw01.plus.net [84.92.3.216]
  4   102 ms    15 ms   216 ms  po6.ptn-gw02.plus.net [212.159.1.137]
  5    15 ms    14 ms    21 ms  vl55.ptn-lb01.plus.net [212.159.2.124]
  6    15 ms    15 ms    15 ms  cdns02.plus.net [212.159.13.50]
Trace complete.

Tracert from the office back to my home IP:

H:\>tracert ***.dynalias.org
Tracing route to ***.dynalias.org [80.229.7.***]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.100.254
  2     2 ms     1 ms     1 ms  <removed>
  3     *        *        *     Request timed out.
  4     1 ms     1 ms     1 ms  linx-gw2.plus.net [195.66.236.164]
  5     2 ms     1 ms     2 ms  po6.ptw-gw01.plus.net [212.159.1.136]
  6     4 ms     2 ms     2 ms  vl308.ptw-gw01.plus.net [84.92.3.217]
  7    21 ms    19 ms    19 ms  ***.plus.com [80.229.7.***]
Trace complete.

[#2]

Thanks.
The gateway tool itself is OK. To fix this problem Plusnet need to change the rDNS entry for 84.92.3.217 from vl308.ptw-gw01.plus.net to the appropriate gateway/aggregator designation.

[#3]

I'll flag this to Bob as he seems to be able to get these changes made quicker than I can!

[#4]

Delayed response but I've given one of our engineers a nudge about this.

[#5]

I had the same on ptw-gw03.
I also had cr*p pings, so I hopped (onto a ptn) no problem now.

[#6]

rDNS for that host should be sorted now:

>nslookup 84.92.3.217
Server:  pbs-intdns01.plus.net
Address:  84.93.219.251
Name:    gi11-1-321.ptw-ag03.plus.net
Address:  84.92.3.217