This is the ADSL one...

Tracing route to rapid-watch.badc.rl.ac.uk [130.246.191.84]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my router
2 15 ms 15 ms 14 ms 10.20.21.168
3 16 ms 15 ms 15 ms syd-nxg-men-csw1-tengi-4-2.tpgi.com.au [202.7.173.1]
4 15 ms 15 ms 14 ms syd-nxg-men-crt1-ge-7-1-0.tpgi.com.au [202.7.162.105]
5 169 ms 168 ms 168 ms te8-3.ccr01.sjc05.atlas.cogentco.com [38.122.92.41]
6 169 ms 170 ms 169 ms te0-3-0-7.ccr22.sjc01.atlas.cogentco.com [154.54.6.69]
7 169 ms 169 ms 169 ms be2047.ccr21.sjc03.atlas.cogentco.com [154.54.5.114]
8 169 ms 168 ms 169 ms tiscali.sjc03.atlas.cogentco.com [154.54.10.214]
9 316 ms 316 ms 315 ms xe-10-0-0.lon21.ip4.tinet.net [89.149.180.110]
10 310 ms 368 ms 313 ms 141.136.103.210
11 * * 310 ms ae29.londpg-sbr1.ja.net [146.97.33.2]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

As you can see after hop 11 it just disappears. So its looking like a routing issue

---

BOINC blog

JANET6, the Joint Academic NETwork ('ja.net' in the log above) is the private 2Tb/s academic network here in the UK. It blocks pings, so that is why your tracert stops after that point. So actually your log doesn't look too bad.

http://en.wikipedia.org/wiki/JANET


From here (work, not home), mine looks similar. While I'm in the UK, our corporate network proxies out to Florida hence the 5000 mile detour.

Tracing route to rapid-watch.badc.rl.ac.uk [130.246.191.84]
over a maximum of 30 hops:
...
9 116 ms 117 ms 118 ms ge-6-23.car2.Orlando1.Level3.net [4.79.118.181]

10 148 ms 117 ms 117 ms ae-2-9.bar2.Orlando1.Level3.net [4.69.133.70]
11 117 ms 117 ms 116 ms ae-0-11.bar1.Orlando1.Level3.net [4.69.137.145]

12 218 ms 217 ms 217 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
13 221 ms 217 ms 217 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10
6]
14 223 ms 225 ms 224 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.
214]
15 218 ms 217 ms 217 ms 4.69.148.49
16 217 ms 217 ms 217 ms ae-41-41.ebr2.London1.Level3.net [4.69.137.65]
17 221 ms 218 ms 219 ms vlan102.ebr1.London1.Level3.net [4.69.143.89]
18 217 ms 217 ms 217 ms ae-4-4.car1.Manchesteruk1.Level3.net [4.69.133.1
01]
19 217 ms 216 ms 265 ms 195.50.119.98
20 218 ms 274 ms 239 ms ae29.erdiss-sbr1.ja.net [146.97.33.41]
21 223 ms 223 ms 223 ms ae31.londpg-sbr1.ja.net [146.97.33.21]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

Janet Netsight Thames Valley network status shows the link to Rutherford Appleton Laboratory from London has been down for over a month (since 14/10/2013 15:41 BST). Janet (the UK academic network) should automatically switch to using the alternative route via Bradley Stoke (just north of Bristol).

When I browse to the upload handler (http://rapid-watch.badc.rl.ac.uk/cpdn_cgi/file_upload_handler) I get the expected response:

<data_server_reply>
    <status>1</status>
    <message>no command</message>
</data_server_reply>

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

JANET6, the Joint Academic NETwork ('ja.net' in the log above) is the private 2Tb/s academic network here in the UK. It blocks pings, so that is why your tracert stops after that point. So actually your log doesn't look too bad.

Janet allows tracing of the route to climateapps2.oerc.ox.ac.uk, so it's possible that actual traffic is being re-routed via Bradley Stoke but pings aren't. The browser check I mentioned in my last message is the definitive test.

Tracing route to sepia.oerc.ox.ac.uk [129.67.195.185] over a maximum of 30 hops:

...
11 36 ms 37 ms 37 ms ae0.londtn-sbr1.ja.net [146.97.35.109]
12 38 ms 36 ms 38 ms ae29.londtw-sbr1.ja.net [146.97.33.9]
13 39 ms 39 ms 37 ms ae30.londpg-sbr1.ja.net [146.97.33.5]
14 34 ms 37 ms 35 ms ae21.read-rbr3.ja.net [146.97.37.206]
15 37 ms 35 ms 36 ms ae1.read-rbr2.ja.net [193.63.108.129]
16 39 ms 37 ms 36 ms ae2.oxfo-rbr2.ja.net [193.63.108.134]
17 38 ms 40 ms 39 ms Oxford-University-1.ja.net [193.63.109.110]
18 39 ms 37 ms 37 ms cengb.backbone.ox.ac.uk [192.76.21.11]
19 37 ms 36 ms 39 ms sepia.oerc.ox.ac.uk [129.67.195.185]

Trace complete.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Maybe it's Rutherford Appleton labs which is blocking the pings, rather than JANET itself.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

Same behavior for ja.net
11 322 ms 322 ms 323 ms linx-gw1.ja.net [195.66.224.15]
12 323 ms 323 ms 323 ms ae1.londtn-sbr1.ja.net [146.97.35.181]
13 * * * Request timed out.
14 323 ms 322 ms 322 ms ae30.londpg-sbr1.ja.net [146.97.33.5]
15 * * * Request timed out.
...
30 * * * Request timed out.

Trace complete.