I've seen that once or twice before, always with an odd-looking route that crosses blueyonder from ntl - anything crossing that route, seems to pick up a wrong IP.
Tracing route to aboutus.org [66.249.16.230]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 13 ms 13 ms 12 ms 10.3.48.1
3 12 ms 11 ms 15 ms wapk-t2cam1-a-v107.inet.ntl.com [80.1.170.29]
4 11 ms 15 ms 13 ms walt-dpim1-2-coc-1-gw.service.virginmedia.net [62.255.80.165]
5 11 ms 11 ms 13 ms pop-bb-a-so-210-0.inet.ntl.com [213.105.174.234]
6 18 ms 17 ms 14 ms win-bb-b-so-010-0.inet.ntl.com [62.253.185.202]
7 16 ms 17 ms 15 ms bir-bb-a-so-100-0.inet.ntl.com [62.253.185.141]
8 23 ms 23 ms 27 ms florence-pos20.inet.ntl.com [213.105.175.218]
9 27 ms 26 ms 27 ms brad-wit-pos.telewest.net [194.117.136.22]
10 25 ms 27 ms 25 ms 194.117.136.214
11 153 ms 199 ms 206 ms 194.117.136.209
12 23 ms 31 ms 24 ms
pc-62-30-249-169-ha.blueyonder.co.uk [62.30.249.169]
13 25 ms 26 ms 25 ms pc-62-31-0-204-nm.blueyonder.co.uk [62.30.0.204]
14 29 ms 31 ms 30 ms
pc-62-30-249-46-ha.blueyonder.co.uk [62.30.249.46]
15 30 ms 33 ms 36 ms linx.ge1-0.cr01.lhr01.mzima.net [195.66.225.15]
16 135 ms 126 ms 123 ms eos1-0.cr01.lga02.mzima.net [216.193.255.45]
17 132 ms 130 ms 137 ms xe1-0.cr01.lga01.mzima.net [216.193.255.213]
18 127 ms 125 ms 126 ms eos3-2.cr01.ord01.mzima.net [216.193.255.54]
19 185 ms 178 ms 180 ms eos1-22.cr02.sjc02.mzima.net [216.193.255.154]
20 201 ms 197 ms 199 ms eos1-23.cr01.sea01.mzima.net [216.193.255.174]
21 190 ms 188 ms 187 ms ge0-spry.cust.sea01.mzima.net [72.37.232.14]
22 190 ms 190 ms 191 ms 216.145.11.110
23 203 ms 204 ms 202 ms 66.249.16.230
Trace complete.
------------------
Tracing route to
www.badongo.com [69.80.228.120]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 13 ms 11 ms 11 ms 10.3.48.1
3 13 ms 13 ms 13 ms wapk-t2cam1-a-v107.inet.ntl.com [80.1.170.29]
4 14 ms 12 ms 12 ms walt-dpim1-4-coc-1-gw.service.virginmedia.net [62.255.80.173]
5 13 ms 13 ms 14 ms pop-bb-a-so-210-0.inet.ntl.com [213.105.174.234]
6 14 ms 13 ms 13 ms win-bb-b-so-010-0.inet.ntl.com [62.253.185.202]
7 17 ms 17 ms 17 ms bir-bb-a-so-100-0.inet.ntl.com [62.253.185.141]
8 22 ms 22 ms 21 ms florence-pos20.inet.ntl.com [213.105.175.218]
9 21 ms 20 ms 31 ms brad-wit-pos.telewest.net [194.117.136.22]
10 21 ms 20 ms 21 ms 194.117.136.169
11 24 ms 24 ms 27 ms 194.117.136.149
12 18 ms 28 ms 19 ms
pc-62-30-249-173-ha.blueyonder.co.uk [62.30.249.173]
13 21 ms 27 ms 22 ms pc-62-31-0-204-nm.blueyonder.co.uk [62.30.0.204]
14 25 ms 26 ms 25 ms
pc-62-30-249-46-ha.blueyonder.co.uk [62.30.249.46]
15 25 ms 21 ms 23 ms gsr12012.lon.he.net [195.66.224.21]
16 92 ms 94 ms 103 ms 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
17 110 ms 98 ms 98 ms 10gigabitethernet2-3.core1.ash1.he.net [72.52.92.86]
18 138 ms 138 ms 133 ms 10gigabitethernet1-1.core1.dal1.he.net [72.52.92.61]
19 136 ms 138 ms 136 ms 69.80.236.97
20 139 ms 141 ms 137 ms dfw01.te2-4.cs02.hou02.fiberstorm.alphared.com [69.80.236.66]
21 145 ms 145 ms 145 ms 69.80.228.120
Trace complete.
The second route is especially screwed up, as
Tracing route to 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 13 ms 13 ms 15 ms 10.3.48.1
3 12 ms 12 ms 17 ms wapk-t2cam1-a-v107.inet.ntl.com [80.1.170.29]
4 15 ms 11 ms 12 ms popl-t3core-1a-ge-018-0.inet.ntl.com [195.182.180.229]
5 13 ms 12 ms 16 ms pop-bb-a-so-210-0.inet.ntl.com [213.105.174.234]
6 14 ms 16 ms 15 ms nth-bb-b-so-010-0.inet.ntl.com [213.105.172.13]
7 20 ms 18 ms 16 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
8 16 ms 19 ms 23 ms gsr12012.lon.he.net [195.66.224.21]
9 99 ms 87 ms 86 ms 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
Trace complete.
It can make a direct path via gsr12012.lon.he.net [195.66.224.21] though that address follows yet another route if traced directly, looks like a right old peering screwup, with indirect paths being preferred to a direct interchange - that whole section of routing is a mess.