The Nginx version of PageSpeed is now ready for production use. You
can see it in action with examples on our demonstration site:
http://ngxpagespeed.com
Read more in our official announcement:
http://googledevelopers.blogspot.com/2013/04/speed-up-your-sites-with-pagespeed-for.html
Get started with ngx_pagespeed or upgrade to beta with the installation
guide:
https://github.com/pagespeed/ngx_pagespeed#readme
Join our mailing lists to keep up with changes in ngx_pagespeed:
https://groups.google.com/forum/#!forum/ngx-pagespeed-discuss
https://groups.google.com/forum/#!forum/ngx-pagespeed-announce
Thanks to everyone who helped with getting us to beta, especially Otto
van der Schaff, Chai Zhenhua, Weibin Y., Junmin Xiong, and Ben
Noordhuis.
Jeff Kaufman
Google
But the web-site appears to be down; tested from two distinct locations.
Cns# http_ping -count 4 -interval 1 http://ngxpagespeed.com/; date
http://ngxpagespeed.com/: timed out
http://ngxpagespeed.com/: timed out
http://ngxpagespeed.com/: timed out
http://ngxpagespeed.com/: timed out
— http://ngxpagespeed.com/ http_ping statistics —
4 fetches started, 0 completed (0%), 0 failures (0%), 4 timeouts (100%)
Thu Apr 25 14:41:29 PDT 2013
Cns# traceroute ngxpagespeed.com; date
traceroute to ngxpagespeed.com (67.207.141.173), 64 hops max, 40 byte
packets
1 static.33.203.4.46.clients.your-server.de (46.4.203.33) 0.712 ms
3.311 ms 0.507 ms
2 hos-tr2.juniper1.rz13.hetzner.de (213.239.224.33) 0.243 ms
hos-tr1.juniper1.rz13.hetzner.de (213.239.224.1) 0.240 ms
hos-tr4.juniper2.rz13.hetzner.de (213.239.224.97) 0.242 ms
3 hos-bb2.juniper4.rz2.hetzner.de (213.239.240.138) 2.868 ms 2.846
ms 2.847 ms
4 r1nue1.core.init7.net (77.109.135.101) 2.913 ms 10.420 ms 3.176
ms
5 r1ams1.core.init7.net (77.109.140.25) 25.4 ms 25.49 ms 25.43 ms
6 er1.ams1.nl.above.net (195.69.144.122) 25.284 ms 25.262 ms
r1fra2.core.init7.net (77.109.140.49) 17.540 ms
7 xe-1-2-0.mpr1.fra4.de.above.net (80.81.194.26) 6.691 ms 6.735 ms
6.733 ms
8 xe-5-3-0.cr2.lga5.us.above.net (64.125.25.57) 93.279 ms 93.273 ms
99.8 ms
9 xe-3-0-0.cr2.ord2.us.above.net (64.125.31.74) 115.35 ms
so-2-1-0.mpr2.lga5.us.above.net (64.125.31.182) 92.991 ms 93.40 ms
10 xe-2-3-0.cr2.ord2.us.above.net (64.125.24.30) 114.972 ms 114.513
ms 114.564 ms
11 xe-0-0-0.cr1.ord2.us.above.net (64.125.28.233) 114.73 ms 117.839
ms 114.441 ms
12 64.124.65.218.allocated.above.net (64.124.65.218) 116.262 ms
116.354 ms 116.227 ms
13 coreb.ord1.rackspace.net (184.106.126.142) 115.435 ms
corea.ord1.rackspace.net (184.106.126.140) 115.231 ms
coreb.ord1.rackspace.net (184.106.126.142) 115.219 ms
14 core1-CoreA.ord1.rackspace.net (184.106.126.125) 115.323 ms
core1-CoreB.ord1.rackspace.net (184.106.126.129) 117.682 ms
corea.ord1.rackspace.net (184.106.126.140) 114.820 ms
15 core1-CoreB.ord1.rackspace.net (184.106.126.129) 117.579 ms
core1-CoreA.ord1.rackspace.net (184.106.126.125) 114.855 ms
core1-CoreB.ord1.rackspace.net (184.106.126.129) 117.336 ms
16 184.106.126.69 (184.106.126.69) 115.970 ms 116.285 ms 115.802 ms
17 67-207-141-173.static.cloud-ips.com (67.207.141.173) 115.950 ms !C
115.894 ms !C 115.999 ms !C
Thu Apr 25 14:41:44 PDT 2013
C.
Shoot. Fixed.
On Thu, Apr 25, 2013 at 5:43 PM, Constantine A. Murenin
Yup http://ngxpagespeed.com/ isn’t accessible at all from my end either.
Posted at Nginx Forum: