No... haven't tried another browser. That's an interesting thought.
Now, I'm logged in direct from da waterin' hole again, and it appears to be working... I did another tracert... and I was wrong about the 10ms bidness... but here's the trace... and under 50ms ain't bad either...
C:\>tracert www.freerepublic.com
Tracing route to www.freerepublic.com [209.157.64.200]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms eth0.nmd.bes.sea.wayport.net [65.219.162.1]
2 3 ms 3 ms 2 ms 208.252.89.169
3 7 ms 10 ms 6 ms 150.ATM3-0.GW8.SEA1.ALTER.NET [208.214.103.41]
4 6 ms 6 ms 6 ms 109.ATM2-0.XR1.SEA1.ALTER.NET [152.63.105.218]
5 6 ms 7 ms 7 ms 0.so-0-0-0.XL1.SEA1.ALTER.NET [152.63.106.225]
6 6 ms 6 ms 7 ms POS6-0.BR2.SEA1.ALTER.NET [152.63.106.1]
7 7 ms 6 ms 6 ms 204.255.174.246
8 8 ms 8 ms 7 ms p16-0-1-0.r20.sttlwa01.us.bb.verio.net [129.250.
2.14]
9 28 ms 28 ms 28 ms p16-0-1-2.r21.plalca01.us.bb.verio.net [129.250.
5.83]
10 27 ms 27 ms 27 ms p64-0-0-0.r21.mlpsca01.us.bb.verio.net [129.250.
5.49]
11 27 ms 31 ms 27 ms mg-2.a00.mlpsca01.us.da.verio.net [129.250.25.19
4]
12 28 ms 27 ms 28 ms mg-1.a01.mlpsca01.us.da.verio.net [129.250.24.19
5]
13 30 ms 29 ms 27 ms 128.242.105.82
14 32 ms 43 ms 33 ms www.freerepublic.com [209.157.64.200]
Trace complete.