I really must write about this in more detail.

I have mentioned it once or twice before on the blog. The last time, I thought I had fixed it by changing the DNS. I’ve however since reversed these changes as they did not make a lasting difference.

Really simply, and without going too much into it right now, I can access Irish websites but I cannot access websites in other countries. Hence, I can write to this blog but I cant access twitter.com at the moment.

I want to see what the difference is between a tracert on this connection and the tracert on another vodafone connection. I know their not static routes but still, it will be interesting to see what the difference is.

Here is the output of the tracert on my machine.

Tracing route to twitter.com [128.121.146.228]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1 2 33 ms 33 ms 33 ms 89.19.64.2 3 34 ms 35 ms 37 ms 89.19.64.73 4 35 ms 36 ms 37 ms 213.233.129.93 5 138 ms 107 ms 108 ms 193.95.147.61 6 53 ms 51 ms 52 ms vlan72.rt001.cwt.esat.net [193.95.130.209] 7 51 ms 52 ms 50 ms ge3-0.br003.cwt.esat.net [193.95.129.6] 8 54 ms 54 ms 55 ms xe-0-1-0-104.dub20.ip4.tinet.net [213.200.67.253 ] 9 135 ms 138 ms 138 ms xe-5-1-0.was12.ip4.tinet.net [89.149.184.34] 10 * * * Request timed out. 11 191 ms 190 ms 191 ms as-3.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.1 67] 12 191 ms 191 ms 192 ms xe-1-1-0.r20.mlpsca01.us.bb.gin.ntt.net [129.250 .5.61] 13 192 ms 193 ms 189 ms mg-1.c20.mlpsca01.us.da.verio.net [129.250.28.81 ] 14 190 ms 192 ms 189 ms 128.121.150.245 15 293 ms 188 ms 186 ms 128.121.146.213 16 261 ms 191 ms 191 ms 128.121.146.228 Trace complete.

Interestingly, I cannot access twitter from this machine. I can try on any one of the computers here. Not one will load the twitter page. If I ping it, I get a response. If I tracert it get a response also. But it jsut will not load http://www.twitter.com It’s not confined to Twitter either as I said earlier. I was trying to install winamp today from http://www.winamp.com and I couldn’t access that either. Again, I could tracert to it without any problems.

Here however is the output of tracert on another vodafone connection. Note, this check was done within two seconds of the first on my machine. This connection has no problems accessing any website. The configuration of this connection almost completely mirrors my own. The internal P address structure is the only noticeable difference.

Tracing route to twitter.com [128.242.240.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254 2 9 ms 10 ms 11 ms 89.19.64.129 3 13 ms 12 ms 12 ms 89.19.64.181 4 12 ms 13 ms 13 ms 193.95.147.65 5 11 ms 11 ms 11 ms vlan73.sw002.cwt.esat.net [193.95.130.217] 6 11 ms 11 ms 10 ms ge1-1.br003.cwt.esat.net [193.95.131.57] 7 11 ms 11 ms 12 ms xe-0-1-0-104.dub20.ip4.tinet.net [213.200.67.253 ] 8 124 ms 98 ms 97 ms xe-5-0-0.was12.ip4.tinet.net [89.149.185.17] 9 * * * Request timed out. 10 165 ms 168 ms 169 ms as-3.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.1 67] 11 166 ms 164 ms 168 ms xe-1-1-0.r20.mlpsca01.us.bb.gin.ntt.net [129.250 .5.61] 12 168 ms 166 ms 171 ms mg-1.c20.mlpsca01.us.da.verio.net [129.250.28.81 ] 13 170 ms 170 ms 167 ms 128.241.122.197 14 163 ms 165 ms 168 ms 128.242.240.5 15 175 ms 202 ms 174 ms 128.242.240.20 Trace complete.

Again, I’ll vent at another stage about my frustrations while trying to get this fixed. Not now though, it’s late.

Update on Monday 01st March 2010 at 10:37PM.
Around twenty four hours after writing this blog post, internet connectivity seems to be back to normal. I expect it will stay this way for a day or so but unless resolved, the problem described earlier will return. As a demonstration of the change in the connection to the internet tonight, I will provide the output of the tracert command with Twitter continuing to be the required destination.

Tracing route to twitter.com [168.143.162.116]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1 2 34 ms 34 ms 34 ms 89.19.64.129 3 35 ms 34 ms 34 ms 89.19.64.181 4 34 ms 34 ms 34 ms 193.95.147.65 5 35 ms 37 ms 35 ms vlan73.sw002.cwt.esat.net [193.95.130.217] 6 35 ms 34 ms 34 ms ge1-1.br003.cwt.esat.net [193.95.131.57] 7 35 ms 35 ms 34 ms xe-0-1-0-104.dub20.ip4.tinet.net [213.200.67.253 ] 8 121 ms 124 ms 123 ms xe-5-1-0.was12.ip4.tinet.net [89.149.184.34] 9 * * * Request timed out. 10 191 ms 193 ms 190 ms as-3.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.1 67] 11 191 ms 220 ms 191 ms xe-1-1-0.r20.mlpsca01.us.bb.gin.ntt.net [129.250 .5.61] 12 194 ms 193 ms 192 ms mg-1.c20.mlpsca01.us.da.verio.net [129.250.28.81 ] 13 194 ms 192 ms 191 ms 128.121.150.133 14 202 ms 189 ms 191 ms 168.143.162.85 15 191 ms 187 ms 189 ms 168.143.162.116 Trace complete.

Interestingly, the destination address of Twitter has changed and hop 9 timed out.

I cant explain the change, I just know that it exists.

All I can say is I really hope that the people responsibility for providing this connection can do something.