Kalau website sendiri, atau website baru, kadang perlu refresh cache.
Atau kadang karena perbedaan routing
Atau karena perbedaan dns.
Coba lakukan traceroute memakai Speedy dan Flash, bandingkan jalurnya.
Bisa juga karena masalah rewrite di webserver, bisa juga karena masalah lain. Agak susah memberikan pendapat karena infonya hanya sedikit
Ini nameserver di laptop sdh sy rubah ke google.
Ini hasil pengetesan domain hhvm.com jg bermasalah dgn speedy. Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
Pengetesan dgn SPEEDY (hhvm.com gagal dibuka):
$ ping hhvm.com
PING hhvm.com (140.211.15.195) 56(84) bytes of data.
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=1 ttl=47 time=265 ms
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=2 ttl=47 time=270 ms
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=3 ttl=47 time=263 ms
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=4 ttl=45 time=261 ms
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=5 ttl=45 time=252 ms
64 bytes from facebook2.osuosl.org (140.211.15.195): icmp_req=6 ttl=45 time=267 ms
^C
--- hhvm.com ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 6051ms
rtt min/avg/max/mdev = 252.975/263.625/270.960/5.646 ms
$ traceroute hhvm.com
traceroute to hhvm.com (140.211.15.195), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.566 ms 3.651 ms 3.708 ms
2 36.73.80.1 (36.73.80.1) 29.914 ms 37.969 ms 46.567 ms
3 209.subnet125-160-11.speedy.telkom.net.id (125.160.11.209) 54.664 ms 63.581 ms 76.034 ms
4 61.94.114.121 (61.94.114.121) 79.872 ms 88.726 ms 97.296 ms
5 180.240.193.42 (180.240.193.42) 129.248 ms 140.280 ms 152.822 ms
6 * 180.240.193.41 (180.240.193.41) 288.127 ms *
7 180.240.192.38 (180.240.192.38) 323.999 ms 325.168 ms 326.580 ms
8 * * *
9 ae-11-51.car1.Seattle1.Level3.net (4.69.147.131) 882.572 ms 883.991 ms 885.144 ms
10 ae-11-51.car1.Seattle1.Level3.net (4.69.147.131) 886.357 ms 887.847 ms 889.248 ms
11 UNIVERSITY.car1.Seattle1.Level3.net (4.53.150.46) 681.868 ms 686.480 ms 272.826 ms
12 corv-car1-gw.nero.net (207.98.64.39) 253.624 ms 261.558 ms 270.853 ms
13 facebook2.osuosl.org (140.211.15.195) 279.710 ms 288.065 ms 297.037 ms
Pengetesan dgn FLASH (hhvm.com, berhasil dibuka):
$ ping hhvm.com
PING hhvm.com (140.211.15.195) 56(84) bytes of data.
64 bytes from 140.211.15.195: icmp_req=1 ttl=55 time=300 ms
64 bytes from 140.211.15.195: icmp_req=2 ttl=55 time=293 ms
64 bytes from 140.211.15.195: icmp_req=3 ttl=55 time=294 ms
^C64 bytes from 140.211.15.195: icmp_req=4 ttl=55 time=444 ms
--- hhvm.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 45928ms
rtt min/avg/max/mdev = 293.651/333.216/444.090/64.076 ms
$ traceroute hhvm.com
traceroute to hhvm.com (140.211.15.195), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 180.240.193.77 (180.240.193.77) 148.661 ms 148.529 ms 89.675 ms
5 180.240.192.38 (180.240.192.38) 309.767 ms 250.007 ms 61.94.116.42 (61.94.116.42) 89.802 ms
6 61.94.0.118 (61.94.0.118) 120.099 ms 4.53.228.153 (4.53.228.153) 259.812 ms 61.94.0.118 (61.94.0.118) 119.827 ms
7 61.94.0.117 (61.94.0.117) 160.391 ms 4.69.147.131 (4.69.147.131) 400.297 ms 369.975 ms
8 4.69.147.131 (4.69.147.131) 370.213 ms 61.94.177.186 (61.94.177.186) 139.633 ms 4.69.147.131 (4.69.147.131) 339.882 ms
9 61.5.116.138 (61.5.116.138) 130.052 ms 90.161 ms 100.479 ms
10 207.98.64.39 (207.98.64.39) 319.918 ms 118.98.61.141 (118.98.61.141) 100.137 ms 99.995 ms
11 140.211.15.195 (140.211.15.195) 309.576 ms 180.240.192.38 (180.240.192.38) 299.600 ms 140.211.15.195 (140.211.15.195) 379.617 ms
Bisa bantu analisa?