|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
[2015-05-28 06:21 UTC] dmaisey at westnet dot com dot au
Description: ------------ I am unable to access windows.php.net for the last few days. All links on php.net to http://windows.php.net fail with timeout. PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Fri Nov 21 14:00:02 2025 UTC |
I tried to use the proxy australia-proxy.com, which seems to be based in the US, the 4FreeProxy.nu however seems to be located in SW, and that works too. Are you on some local network or other type of firewall that could potentially block the site? C:\>ping windows.php.net Pinging windows.php.net [195.8.208.241] with 32 bytes of data: Reply from 195.8.208.241: bytes=32 time=35ms TTL=118 Reply from 195.8.208.241: bytes=32 time=35ms TTL=118 Reply from 195.8.208.241: bytes=32 time=34ms TTL=118 Reply from 195.8.208.241: bytes=32 time=34ms TTL=118 Ping statistics for 195.8.208.241: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 35ms, Average = 34ms (Notice the IP is the same as yours) Microsoft operates the site and I doubt they have blocked you outPing seems ok: Pinging windows.php.net [195.8.208.241] with 32 bytes of data: Reply from 195.8.208.241: bytes=32 time=333ms TTL=117 Reply from 195.8.208.241: bytes=32 time=303ms TTL=116 Reply from 195.8.208.241: bytes=32 time=305ms TTL=116 Reply from 195.8.208.241: bytes=32 time=332ms TTL=117 Ping statistics for 195.8.208.241: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 303ms, Maximum = 333ms, Average = 318ms My ISP's network is iiNet. A trace route shows that I can get to the site: Tracing route to windows.php.net [195.8.208.241] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254] 2 4 ms 3 ms 3 ms lo0.bng1.syd4.on.ii.net [150.101.32.83] 3 3 ms 3 ms 3 ms ae7.cr1.syd4.on.ii.net [150.101.34.28] 4 326 ms 304 ms 297 ms ae5.br1.syd4.on.ii.net [150.101.33.48] 5 342 ms 295 ms 315 ms ae0.br1.syd7.on.ii.net [150.101.33.15] 6 295 ms 294 ms 305 ms te0-2-0-3.br2.sjc2.on.ii.net [203.16.213.158] 7 296 ms 294 ms 294 ms te1-2-0.bdr1.lon1.on.ii.net [150.101.33.96] 8 307 ms 307 ms 306 ms 80.249.208.189 9 337 ms 338 ms 336 ms nikhef.openpeering.nl [82.150.154.25] 10 311 ms 312 ms 311 ms openpeering.eun.ams.duocast.net [82.150.155.75] 11 311 ms 310 ms 310 ms xe-0-0-0.er-r23.tcn.as31477.net [89.188.4.34] 12 309 ms 305 ms 303 ms windows.php.net [195.8.208.241] Trace complete. This has only happened recently, so I assume that iiNet my be at fault.