Strange Plusnet Gateway

[#1]

Anyone else seen a tracert with a plusnet gateway like this?
Tracing route to bbc.co.uk [212.58.244.20]
over a maximum of 30 hops:
  1    2 ms    1 ms    2 ms  ZyXEL.Home [192.168.1.1]
  2    13 ms    12 ms    11 ms  179.core.plus.net [195.166.130.179]
  3    13 ms    14 ms    12 ms  irb.12.pcl-cr02.plus.net [84.93.249.114]
  4    13 ms    *      16 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  5    13 ms    11 ms    11 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    13 ms    11 ms    *    kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    13 ms  104 ms    17 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    14 ms    12 ms    13 ms  132.185.255.149
11    13 ms    12 ms    12 ms  fmt-vip71.telhc.bbc.co.uk [212.58.244.20]
Also seeing a slowdown on multithread speed test -- and this is outside the peak time slowdown. 

[#2]

Yes, that gateway is actually pcl-bng04. Plusnet should be updating the rDNS to correct it "real soon now".

Quote from: Bob

Quote from: frogfoot Can anyone explain this result (more rDNS errors?) These two hops are wrong (should be pcl-bng04): link12-central10.pcl-gw02.plus.net (84.93.249.118) 2.449 ms   2    10 ms    9 ms    9 ms  179.core.plus.net [195.166.130.179] I'll ask for them to be updated.

[#3]

Thanks.

[#4]

I note that Bob's post was SEVEN WEEKS ago - shows how fast Plusnet are at solving easy to fix issues!

[#5]

Give them a minute... They'll try and blame Openreach

[#6]

The slow x6 thread test appears to have been due to Firefox.
The x6 test was ok after restarting firefox.