I'm also invariably getting 504 gateway timeout. I access the Internet via tethering
Ping:
doer@miamese:~$ ping
www.entropiawiki.com
PING
www.entropiawiki.com (5.153.53.42) 56(84) bytes of data.
64 bytes from 5.153.53.42-static.reverse.softlayer.com (5.153.53.42): icmp_req=1 ttl=106 time=201 ms
64 bytes from 5.153.53.42-static.reverse.softlayer.com (5.153.53.42): icmp_req=2 ttl=106 time=223 ms
64 bytes from 5.153.53.42-static.reverse.softlayer.com (5.153.53.42): icmp_req=3 ttl=106 time=186 ms
64 bytes from 5.153.53.42-static.reverse.softlayer.com (5.153.53.42): icmp_req=4 ttl=106 time=185 ms
64 bytes from 5.153.53.42-static.reverse.softlayer.com (5.153.53.42): icmp_req=5 ttl=106 time=188 ms
^C
---
www.entropiawiki.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12016ms
rtt min/avg/max/mdev = 182.144/193.558/223.609/11.884 ms
Traceroute:
doer@miamese:~$ traceroute
www.entropiawiki.com
traceroute to
www.entropiawiki.com (5.153.53.42), 30 hops max, 60 byte packets
1 Nokia-N900-42-11.local (10.x.x.x) 24.022 ms 25.573 ms 29.090 ms
2 10.x.x.x (10.x,x,x) 77.721 ms 87.782 ms 89.051 ms
3 10.170.200.133 (10.170.200.133) 95.498 ms 97.114 ms 98.944 ms
4 10.184.80.132 (10.184.80.132) 90.330 ms 91.851 ms 101.652 ms
5 10.184.80.137 (10.184.80.137) 110.653 ms 105.537 ms 108.879 ms
6 10.170.200.11 (10.170.200.11) 114.298 ms 89.785 ms 88.111 ms
7 10.184.6.189 (10.184.6.189) 93.641 ms 70.251 ms 81.251 ms
8 10.185.128.22 (10.185.128.22) 177.932 ms 189.921 ms 188.105 ms
9 * * *
10 * * *
11 vlan51.ebr1.Atlanta2.Level3.net (4.69.150.62) 288.596 ms 293.270 ms 301.438 ms
12 ae-6-6.ebr1.Washington12.Level3.net (4.69.148.106) 303.835 ms 327.390 ms 322.390 ms
13 ae-1-100.ebr2.Washington12.Level3.net (4.69.143.214) 248.409 ms 169.076 ms 162.315 ms
14 ae-58-58.ebr1.NewYork1.Level3.net (4.69.201.69) 193.559 ms ae-57-57.ebr1.NewYork1.Level3.net (4.69.201.65) 196.006 ms ae-58-58.ebr1.NewYork1.Level3.net (4.69.201.69) 202.353 ms
15 ae-44-44.ebr2.London1.Level3.net (4.69.137.77) 227.370 ms ae-41-41.ebr2.London1.Level3.net (4.69.137.65) 232.326 ms 225.088 ms
16 ae-56-221.csw2.London1.Level3.net (4.69.153.130) 236.862 ms ae-59-224.csw2.London1.Level3.net (4.69.153.142) 234.418 ms ae-57-222.csw2.London1.Level3.net (4.69.153.134) 246.610 ms
17 ae-232-3608.edge4.London1.Level3.net (4.69.166.29) 244.177 ms 242.547 ms ae-229-3605.edge4.London1.Level3.net (4.69.166.17) 247.892 ms
18 SOFTLAYER-T.edge4.London1.Level3.net (212.113.14.82) 253.714 ms 249.149 ms 220.217 ms
19 ae0.bbr02.eq01.ams02.networklayer.com (50.97.18.211) 181.858 ms 167.093 ms 187.863 ms
20 ae6.dar02.sr01.ams01.networklayer.com (50.97.18.251) 190.949 ms 196.862 ms 192.173 ms
21 159.253.158.151-static.reverse.softlayer.com (159.253.158.151) 193.648 ms 198.059 ms 159.253.158.149-static.reverse.softlayer.com (159.253.158.149) 189.322 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Dunno if either is helpful. If additional hops on traceroute (of * * * no doubt) are useful, let me know.
ETA: Works fine through TOR, so entropedia must be on some blacklist for T-mobile. Usually that would pop up a notification page, so there must be something strange going on in entropedia code now.