confusedThat's not the weird part. The weird part is both connections at one point go through the same routers (marked in bold)!
Vodafone 3G (via a USB 3G dongle):
Tracing route to livejournal.com [208.93.0.128] over a maximum of 30 hops: 1 116 ms 79 ms 79 ms 10.252.224.29 2 82 ms 79 ms 79 ms host203.msm.che.vodafone [10.203.64.4] 3 100 ms 109 ms 99 ms host203.msm.che.vodafone [10.203.65.1] 4 88 ms 89 ms 89 ms host203.msm.che.vodafone [10.203.65.135] 5 126 ms 129 ms 129 ms host203.msm.che.vodafone [10.203.66.68] 6 * * * Request timed out. 7 86 ms 79 ms 89 ms host203.msm.che.vodafone [10.203.66.212] 8 111 ms 109 ms 89 ms host203.msm.che.vodafone [10.203.70.157] 9 * * * Request timed out. 10 104 ms 99 ms 99 ms TenGigabitEthernet7-1.ar6.LON3.gblx.net [64.214.144.121] 11 203 ms 189 ms 189 ms 0.ge-4-0-0.BR3.NYC4.ALTER.NET [204.255.169.125] 12 250 ms 194 ms 199 ms 0.xe-5-1-3.XL4.NYC4.ALTER.NET [152.63.16.186] 13 177 ms 179 ms 189 ms 0.so-4-2-0.XT2.DCA6.ALTER.NET [152.63.1.169] 14 215 ms 229 ms 249 ms tengigabit9-1.SA2.DCA6.ALTER.NET [207.22.129.6] 15 * * * Request timed out. 16 344 ms 279 ms 280 ms livejournal.com [208.93.0.128] Trace complete
Virgin Media ADSL (via a Netgear DG834G):
Tracing route to livejournal.com [208.93.0.128] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.***.***] 2 16 ms 15 ms 15 ms host82-14-174-16.not-set-yet.ntli.net [82.14.174.16] 3 15 ms 15 ms 15 ms host82-14-173-81.not-set-yet.ntli.net [82.14.173.81] 4 * * 26 ms so-2-2-0.0.cht-cor-001.bddsl.net [83.146.19.57] 5 19 ms 24 ms 24 ms so-3-1-0.0.sqy-cor-001.bddsl.net [83.146.19.21] 6 17 ms 23 ms 16 ms popl-core-1b-ge-410-0.network.virginmedia.net [82.14.168.129] 7 19 ms * 19 ms pop-bb-b-as2-0.network.virginmedia.net [213.105.174.238] 8 142 ms 223 ms 18 ms pop-bb-a-ae0-0.network.virginmedia.net [213.105.174.229] 9 115 ms 33 ms 33 ms 195.50.91.69 10 113 ms 30 ms 112 ms 0.xe-5-0-3.XL3.NYC4.ALTER.NET [152.63.18.6] 11 125 ms 101 ms 124 ms 0.so-6-2-0.XT1.DCA6.ALTER.NET [152.63.0.170] 12 101 ms 101 ms 129 ms 207.22.129.2 13 292 ms 125 ms 127 ms 207.22.129.10 14 102 ms 128 ms 102 ms mci-level3-xe.newyork2.Level3.net [4.68.110.106] 15 101 ms 134 ms 215 ms 0.xe-5-0-0.XL4.NYC4.ALTER.NET [152.63.3.117] 16 133 ms 135 ms 209 ms 0.so-4-2-0.XT2.DCA6.ALTER.NET [152.63.1.169] 17 141 ms 114 ms 110 ms tengigabit9-1.SA2.DCA6.ALTER.NET [207.22.129.6] 18 136 ms 110 ms 135 ms 207.22.129.9 19 143 ms 115 ms 141 ms 207.22.129.10 20 115 ms 114 ms 139 ms 207.22.129.9 21 120 ms 148 ms * 207.22.129.10 22 116 ms * 115 ms 207.22.129.9 23 123 ms 145 ms 126 ms 207.22.129.10 24 148 ms 146 ms 122 ms 207.22.129.9 25 * 125 ms 131 ms 207.22.129.10 26 * * 165 ms 207.22.129.9 27 157 ms 148 ms 163 ms 207.22.129.10 28 127 ms 136 ms 159 ms 207.22.129.9 29 137 ms 164 ms * 207.22.129.10 30 133 ms 173 ms 133 ms 207.22.129.9 Trace complete.
So, who do I pester about this?
Edit: at some point over the past day this mysteriously fixed itself. Of course, something else had to disappear from this connection to maintain the cosmic balance of the routing tables :(
