Comments on: Is your webhost really in India ? How it affects your site speed http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/ Low Latency hosting in India Sat, 07 Jan 2012 12:07:52 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: rahim http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/comment-page-1/#comment-3642 rahim Sat, 07 Jan 2012 12:07:52 +0000 http://e2enetworks.com/?p=197#comment-3642 why bother? Just use flagfox plugin for firefox (or for other browser if they have) and see the flag to determine where they host your site. why bother? Just use flagfox plugin for firefox (or for other browser if they have) and see the flag to determine where they host your site.

]]> By: Why Latency matters in India? – E2E Networks http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/comment-page-1/#comment-3265 Why Latency matters in India? – E2E Networks Tue, 04 May 2010 09:10:01 +0000 http://e2enetworks.com/?p=197#comment-3265 [...] There are several hosting companies in India which have their servers in USA and thus sites hosted by these get impacted by high latencies.  How to determine if your site is in USA or India. [...] [...] There are several hosting companies in India which have their servers in USA and thus sites hosted by these get impacted by high latencies.  How to determine if your site is in USA or India. [...]

]]> By: weblogic http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/comment-page-1/#comment-3231 weblogic Wed, 09 Dec 2009 21:12:10 +0000 http://e2enetworks.com/?p=197#comment-3231 I had again checked latency, it is quiet good.Please also have a look of other networks --- e2enetworks.com ping statistics --- 24 packets transmitted, 24 received, 0% packet loss, time 23423ms rtt min/avg/max/mdev = 93.155/96.265/115.846/4.347 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4917ms rtt min/avg/max/mdev = 305.556/309.969/313.173/2.822 ms --- google.co.in ping statistics --- 13 packets transmitted, 13 received, 0% packet loss, time 12012ms rtt min/avg/max/mdev = 93.497/95.772/98.732/1.502 ms --- yahoo.com ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5045ms rtt min/avg/max/mdev = 290.190/290.650/291.489/0.550 ms --- yahoo.co.in ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6131ms rtt min/avg/max/mdev = 357.589/360.222/361.882/1.482 ms I had again checked latency, it is quiet good.Please also have a look of other networks

— e2enetworks.com ping statistics —
24 packets transmitted, 24 received, 0% packet loss, time 23423ms
rtt min/avg/max/mdev = 93.155/96.265/115.846/4.347 ms

— google.com ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4917ms
rtt min/avg/max/mdev = 305.556/309.969/313.173/2.822 ms

— google.co.in ping statistics —
13 packets transmitted, 13 received, 0% packet loss, time 12012ms
rtt min/avg/max/mdev = 93.497/95.772/98.732/1.502 ms

— yahoo.com ping statistics —
6 packets transmitted, 6 received, 0% packet loss, time 5045ms
rtt min/avg/max/mdev = 290.190/290.650/291.489/0.550 ms

— yahoo.co.in ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6131ms
rtt min/avg/max/mdev = 357.589/360.222/361.882/1.482 ms

]]> By: tarun http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/comment-page-1/#comment-3230 tarun Sat, 05 Dec 2009 13:04:49 +0000 http://e2enetworks.com/?p=197#comment-3230 Can you send us a traceroute to contact@e2enetworks.com. Our ping suggests otherwise ping 122.161.224.197 PING 122.161.224.197 (122.161.224.197) 56(84) bytes of data. 64 bytes from 122.161.224.197: icmp_seq=1 ttl=56 time=103 ms 64 bytes from 122.161.224.197: icmp_seq=2 ttl=56 time=103 ms 64 bytes from 122.161.224.197: icmp_seq=3 ttl=56 time=120 ms 64 bytes from 122.161.224.197: icmp_seq=4 ttl=56 time=108 ms 64 bytes from 122.161.224.197: icmp_seq=5 ttl=56 time=125 ms --- 122.161.224.197 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 103.085/112.165/125.488/9.042 ms Its not quite good I agree but the latency appears to be at Airtel DSLam end rather than ours traceroute to 122.161.224.197 (122.161.224.197), 30 hops max, 40 byte packets 1 server1.e2enetworks.net.in (180.151.0.193) 0.193 ms 0.165 ms 0.141 ms 2 203.122.32.33 (203.122.32.33) 0.636 ms 0.709 ms 0.786 ms 3 203.122.61.33 (203.122.61.33) 41.856 ms 41.810 ms 39.248 ms 4 203.122.61.66 (203.122.61.66) 46.006 ms 45.878 ms 45.852 ms 5 125.18.13.93 (125.18.13.93) 63.837 ms 63.815 ms 63.825 ms 6 203.101.100.182 (203.101.100.182) 58.671 ms 58.653 ms 58.633 ms 7 203.101.83.198 (203.101.83.198) 58.881 ms 59.058 ms 59.034 ms 8 ABTS-North-Static-150.230.160.122.airtelbroadband.in (122.160.230.150) 59.351 ms 59.525 ms 59.798 ms 9 ABTS-North-Static-213.230.160.122.airtelbroadband.in (122.160.230.213) 59.572 ms 60.245 ms 59.866 ms Can you send us a traceroute to contact@e2enetworks.com. Our ping suggests otherwise
ping 122.161.224.197
PING 122.161.224.197 (122.161.224.197) 56(84) bytes of data.
64 bytes from 122.161.224.197: icmp_seq=1 ttl=56 time=103 ms
64 bytes from 122.161.224.197: icmp_seq=2 ttl=56 time=103 ms
64 bytes from 122.161.224.197: icmp_seq=3 ttl=56 time=120 ms
64 bytes from 122.161.224.197: icmp_seq=4 ttl=56 time=108 ms
64 bytes from 122.161.224.197: icmp_seq=5 ttl=56 time=125 ms

— 122.161.224.197 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 103.085/112.165/125.488/9.042 ms
Its not quite good I agree but the latency appears to be at Airtel DSLam end rather than ours

traceroute to 122.161.224.197 (122.161.224.197), 30 hops max, 40 byte packets
1 server1.e2enetworks.net.in (180.151.0.193) 0.193 ms 0.165 ms 0.141 ms
2 203.122.32.33 (203.122.32.33) 0.636 ms 0.709 ms 0.786 ms
3 203.122.61.33 (203.122.61.33) 41.856 ms 41.810 ms 39.248 ms
4 203.122.61.66 (203.122.61.66) 46.006 ms 45.878 ms 45.852 ms
5 125.18.13.93 (125.18.13.93) 63.837 ms 63.815 ms 63.825 ms
6 203.101.100.182 (203.101.100.182) 58.671 ms 58.653 ms 58.633 ms
7 203.101.83.198 (203.101.83.198) 58.881 ms 59.058 ms 59.034 ms
8 ABTS-North-Static-150.230.160.122.airtelbroadband.in (122.160.230.150) 59.351 ms 59.525 ms 59.798 ms
9 ABTS-North-Static-213.230.160.122.airtelbroadband.in (122.160.230.213) 59.572 ms 60.245 ms 59.866 ms

]]> By: weblogic http://e2enetworks.com/2009/11/30/is-your-webhost-really-in-india-how-it-affects-your-site-speed/comment-page-1/#comment-3229 weblogic Sat, 05 Dec 2009 12:58:21 +0000 http://e2enetworks.com/?p=197#comment-3229 What do you say about these results Pinging e2enetworks.com [180.151.0.212] with 32 bytes of data: Reply from 180.151.0.212: bytes=32 time=257ms TTL=54 Reply from 180.151.0.212: bytes=32 time=257ms TTL=54 Reply from 180.151.0.212: bytes=32 time=200ms TTL=54 Reply from 180.151.0.212: bytes=32 time=127ms TTL=54 Ping statistics for 180.151.0.212: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 127ms, Maximum = 257ms, Average = 210ms What do you say about these results

Pinging e2enetworks.com [180.151.0.212] with 32 bytes of data:

Reply from 180.151.0.212: bytes=32 time=257ms TTL=54
Reply from 180.151.0.212: bytes=32 time=257ms TTL=54
Reply from 180.151.0.212: bytes=32 time=200ms TTL=54
Reply from 180.151.0.212: bytes=32 time=127ms TTL=54

Ping statistics for 180.151.0.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 127ms, Maximum = 257ms, Average = 210ms

]]>