Anyone from google? - possible routing loop

The shaperprobe test program from M-Lab is not working. The problem
appears to be a routing loop in google's realm. Emails to m-lab over
the past month were not effective in resolving the issue.

shaperprobe: http://www.measurementlab.net/tools/shaperprobe

64.9.225.153 is server shaperprobe uses.

Traceroute showing routing loop:

$ traceroute 64.9.225.153
traceroute to 64.9.225.153 (64.9.225.153), 64 hops max, 40 byte
packets
1 cat6509-vlan5.edm.tera-byte.com (216.234.161.129) 0.428 ms
0.658 ms 0.399 ms
2 * * *
3 core3-edmonton_1-0-0.net.bell.ca (64.230.119.244) 18.289 ms
    core4-edmonton_1-0-0.net.bell.ca (64.230.119.246) 18.305 ms
    core3-edmonton_1-0-0.net.bell.ca (64.230.119.244) 18.308 ms
4 core4-edmonton_pos10-1-0.net.bell.ca (64.230.77.201) 19.619 ms
18.325 ms
    core3-vancouver_pos15-1-0.net.bell.ca (64.230.77.203) 20.342 ms
5 tcore3-seattle_hundredgige0-5-0-0.net.bell.ca (64.230.79.92)
22.857 ms
    tcore4-seattle_hundredgige0-9-0-0.net.bell.ca (64.230.79.98)
21.344 ms 18.256 ms
6 bx4-seattle_xe1-0-0.net.bell.ca (64.230.125.245) 18.923 ms
18.950 ms
    bx4-seattle_xe8-0-0.net.bell.ca (64.230.125.247) 18.099 ms
7 Global_Crossing_bx3-seattle.net.bell.ca (67.69.246.206) 17.221
ms
    ge-9-29-1G.ar5.sea1.gblx.net (64.212.107.53) 33.570 ms
    Global_Crossing_bx3-seattle.net.bell.ca (67.69.246.206) 171.896
ms
8 204.245.39.194 (204.245.39.194) 74.329 ms 73.353 ms 74.364 ms
9 64.9.224.130 (64.9.224.130) 75.516 ms 75.441 ms 75.421 ms
10 64.9.224.142 (64.9.224.142) 74.722 ms 73.774 ms 73.741 ms
11 64.9.224.230 (64.9.224.230) 74.525 ms 75.333 ms 75.360 ms
12 64.9.224.229 (64.9.224.229) 73.637 ms 74.666 ms 74.619 ms
13 64.9.224.230 (64.9.224.230) 74.812 ms 75.119 ms 75.467 ms
14 64.9.224.229 (64.9.224.229) 73.819 ms 74.694 ms 74.734 ms
15 64.9.224.230 (64.9.224.230) 75.553 ms 74.605 ms 75.588 ms
16 64.9.224.229 (64.9.224.229) 73.833 ms 74.745 ms 73.794 ms
17 64.9.224.230 (64.9.224.230) 74.689 ms 74.691 ms 75.701 ms
18 64.9.224.229 (64.9.224.229) 73.837 ms 74.786 ms 74.986 ms
19 64.9.224.230 (64.9.224.230) 74.722 ms 75.720 ms 75.212 ms
20 64.9.224.229 (64.9.224.229) 74.868 ms 74.881 ms 73.911 ms
21 64.9.224.230 (64.9.224.230) 74.857 ms 74.846 ms 74.788 ms
22 64.9.224.229 (64.9.224.229) 74.909 ms 74.952 ms 73.975 ms
23 64.9.224.230 (64.9.224.230) 75.860 ms 74.898 ms 79.610 ms
24 64.9.224.229 (64.9.224.229) 75.046 ms 74.098 ms 74.112 ms
25 64.9.224.230 (64.9.224.230) 74.928 ms 74.968 ms 75.976 ms
26 64.9.224.229 (64.9.224.229) 74.093 ms 75.088 ms 75.015 ms
27 64.9.224.230 (64.9.224.230) 76.031 ms 75.050 ms 75.989 ms
28 64.9.224.229 (64.9.224.229) 107.876 ms 74.216 ms 75.263 ms
29 64.9.224.230 (64.9.224.230) 75.253 ms 81.958 ms 76.030 ms
30 64.9.224.229 (64.9.224.229) 75.196 ms 75.149 ms 74.183 ms
31 64.9.224.230 (64.9.224.230) 76.127 ms 76.370 ms 75.149 ms
32 64.9.224.229 (64.9.224.229) 75.199 ms 74.242 ms 75.240 ms
33 64.9.224.230 (64.9.224.230) 76.514 ms 75.286 ms 76.278 ms
34 64.9.224.229 (64.9.224.229) 75.308 ms 75.253 ms 75.270 ms
35 64.9.224.230 (64.9.224.230) 75.493 ms 76.337 ms 75.282 ms
36 64.9.224.229 (64.9.224.229) 75.312 ms 75.359 ms 75.344 ms
37 64.9.224.230 (64.9.224.230) 75.449 ms 75.395 ms 75.745 ms
38 64.9.224.229 (64.9.224.229) 74.486 ms 75.419 ms 74.524 ms
39 64.9.224.230 (64.9.224.230) 75.444 ms 76.412 ms 75.474 ms
40 64.9.224.229 (64.9.224.229) 74.467 ms 75.434 ms 75.477 ms
41 64.9.224.230 (64.9.224.230) 77.191 ms 75.567 ms 75.553 ms

looking, thnx

The M-Lab folks are looking at it. The loop is getting resolved as I
type (thanks, Chris).

Unfortunately. the Shaperprobe researchers hard-coded IP addresses in
their experiment for a site that is in the process of being
decommissioned, the M-Lab ops team is working on getting that bit
resolved ASAP.

Thanks,
Stephen