For me, up to now this problem was manifesting for overseas sites but now I am experiencing it with sites hosted in the Indian subcontinent.
PHP: Hypertext Preprocessor kept timing out, whereas PHP: Hypertext Preprocessor worked fine. (Actually, PHP: Hypertext Preprocessor redirects the browser to the closest server based on Geo IP). See traceroutes below.
# traceroute in2.php.net
traceroute to in2.php.net (203.199.107.5), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.423 ms 1.391 ms 2.023 ms
2 * * *
3 * * *
4 * * *
5 59.160.16.38.static.vsnl.net.in (59.160.16.38) 18.844 ms 18.798 ms 21.942 ms
6 203.197.33.200.static.vsnl.net.in (203.197.33.200) 17.018 ms 20.908 ms 21.815 ms
7 * * *
8 vashi-117-lan.73.static.vsnl.net.in (202.54.117.73) 16.455 ms 17.267 ms 17.477 ms
9 vashi-lan-203.199.113.8.static.vsnl.net.in (203.199.113.8) 28.385 ms 31.280 ms 31.947 ms
10 * * *
11 * * *
... snip ...
28 * * *
29 * * *
30 * * *
When the hop count reaches 30, your packets are going to never land.
Whereas in.php.net is reachable in 10 hops.
# traceroute in.php.net
traceroute to in.php.net (203.199.124.94), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.438 ms 1.384 ms 3.055 ms
2 * * *
3 * * *
4 triband-mum-59.185.0.65.mtnl.net.in (59.185.0.65) 16.636 ms 16.437 ms 17.973 ms
5 59.160.30.46.static.vsnl.net.in (59.160.30.46) 18.047 ms 18.861 ms 23.107 ms
6 * * *
7 vashi-117-lan.73.static.vsnl.net.in (202.54.117.73) 35.271 ms 44.993 ms 40.665 ms
8 vashi-lan-203.199.113.8.static.vsnl.net.in (203.199.113.8) 18.424 ms 20.232 ms 19.234 ms
9 203.199.124.94.static.vsnl.net.in (203.199.124.94) 17.089 ms 20.680 ms 21.279 ms
Folks, keep a record of the time when this happens. For me it starts around 13:30 and continues well into the the evening till 00:00. IMO, this is the time frame when most subscribers are active on the 'Net.
Therefore, my second hypothesis is that some router(s) in the MTNL/VSNL link is running into a capacity problem and dropping connections. Only MTNL NOC engineers will be able to investigate it.
PHP: Hypertext Preprocessor kept timing out, whereas PHP: Hypertext Preprocessor worked fine. (Actually, PHP: Hypertext Preprocessor redirects the browser to the closest server based on Geo IP). See traceroutes below.
# traceroute in2.php.net
traceroute to in2.php.net (203.199.107.5), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.423 ms 1.391 ms 2.023 ms
2 * * *
3 * * *
4 * * *
5 59.160.16.38.static.vsnl.net.in (59.160.16.38) 18.844 ms 18.798 ms 21.942 ms
6 203.197.33.200.static.vsnl.net.in (203.197.33.200) 17.018 ms 20.908 ms 21.815 ms
7 * * *
8 vashi-117-lan.73.static.vsnl.net.in (202.54.117.73) 16.455 ms 17.267 ms 17.477 ms
9 vashi-lan-203.199.113.8.static.vsnl.net.in (203.199.113.8) 28.385 ms 31.280 ms 31.947 ms
10 * * *
11 * * *
... snip ...
28 * * *
29 * * *
30 * * *
When the hop count reaches 30, your packets are going to never land.
Whereas in.php.net is reachable in 10 hops.
# traceroute in.php.net
traceroute to in.php.net (203.199.124.94), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.438 ms 1.384 ms 3.055 ms
2 * * *
3 * * *
4 triband-mum-59.185.0.65.mtnl.net.in (59.185.0.65) 16.636 ms 16.437 ms 17.973 ms
5 59.160.30.46.static.vsnl.net.in (59.160.30.46) 18.047 ms 18.861 ms 23.107 ms
6 * * *
7 vashi-117-lan.73.static.vsnl.net.in (202.54.117.73) 35.271 ms 44.993 ms 40.665 ms
8 vashi-lan-203.199.113.8.static.vsnl.net.in (203.199.113.8) 18.424 ms 20.232 ms 19.234 ms
9 203.199.124.94.static.vsnl.net.in (203.199.124.94) 17.089 ms 20.680 ms 21.279 ms
Folks, keep a record of the time when this happens. For me it starts around 13:30 and continues well into the the evening till 00:00. IMO, this is the time frame when most subscribers are active on the 'Net.
Therefore, my second hypothesis is that some router(s) in the MTNL/VSNL link is running into a capacity problem and dropping connections. Only MTNL NOC engineers will be able to investigate it.