Title: rocjoe's Replies | WordPress.org --- # rocjoe [ ](https://wordpress.org/support/users/rocjoe/) * [Profile](https://wordpress.org/support/users/rocjoe/) * [Topics Started](https://wordpress.org/support/users/rocjoe/topics/) * [Replies Created](https://wordpress.org/support/users/rocjoe/replies/) * [Reviews Written](https://wordpress.org/support/users/rocjoe/reviews/) * [Topics Replied To](https://wordpress.org/support/users/rocjoe/replied-to/) * [Engagements](https://wordpress.org/support/users/rocjoe/engagements/) * [Favorites](https://wordpress.org/support/users/rocjoe/favorites/) Search replies: ## Forum Replies Created Viewing 3 replies - 1 through 3 (of 3 total) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WordPress.org unreachable for one month](https://wordpress.org/support/topic/wordpress-org-unreachable-for-one-month/) * Thread Starter [rocjoe](https://wordpress.org/support/users/rocjoe/) * (@rocjoe) * [7 years, 8 months ago](https://wordpress.org/support/topic/wordpress-org-unreachable-for-one-month/#post-10682934) * It’s a connection timeout. I’ve done several traceroutes and they all stop at your server host, Singlehop: * ``` traceroute wordpress.org traceroute to wordpress.org (198.143.164.252), 30 hops max, 60 byte packets 1 216.182.224.36 (216.182.224.36) 19.246 ms 216.182.226.18 (216.182.226.18) 19.589 ms 216.182.231.0 (216.182.231.0) 28.623 ms 2 100.66.13.92 (100.66.13.92) 17.909 ms 100.66.12.196 (100.66.12.196) 15.788 ms 100.66.12.140 (100.66.12.140) 14.110 ms 3 100.66.15.46 (100.66.15.46) 21.514 ms 100.66.15.42 (100.66.15.42) 13.679 ms 100.66.10.168 (100.66.10.168) 21.739 ms 4 100.66.7.157 (100.66.7.157) 17.554 ms 100.66.6.113 (100.66.6.113) 13.065 ms 100.66.7.207 (100.66.7.207) 17.357 ms 5 100.66.4.159 (100.66.4.159) 16.889 ms 100.66.4.217 (100.66.4.217) 13.950 ms 100.66.4.103 (100.66.4.103) 14.447 ms 6 100.65.10.161 (100.65.10.161) 0.389 ms 100.65.10.65 (100.65.10.65) 0.454 ms 100.65.11.1 (100.65.11.1) 0.386 ms 7 205.251.244.96 (205.251.244.96) 2.189 ms 205.251.244.68 (205.251.244.68) 44.046 ms 52.93.24.108 (52.93.24.108) 2.237 ms 8 52.93.24.117 (52.93.24.117) 1.852 ms 52.93.24.107 (52.93.24.107) 0.741 ms 52.93.24.105 (52.93.24.105) 0.760 ms 9 54.239.111.2 (54.239.111.2) 44.025 ms 54.239.109.42 (54.239.109.42) 21.223 ms 54.239.108.94 (54.239.108.94) 11.587 ms 10 54.239.111.247 (54.239.111.247) 0.844 ms 54.239.111.251 (54.239.111.251) 0.845 ms 54.239.111.255 (54.239.111.255) 0.809 ms 11 ae1.er5.iad10.us.zip.zayo.com (64.125.12.29) 1.111 ms 1.052 ms 0.839 ms 12 ae15.cr2.dca2.us.zip.zayo.com (64.125.31.41) 2.387 ms ae14.cr2.dca2.us.zip.zayo.com (64.125.28.62) 4.033 ms 4.008 ms 13 ae27.cs2.dca2.us.eth.zayo.com (64.125.30.248) 26.126 ms 26.193 ms 26.153 ms 14 ae4.cs2.lga5.us.eth.zayo.com (64.125.29.30) 27.488 ms 26.407 ms 26.847 ms 15 ae3.cs2.ord2.us.eth.zayo.com (64.125.29.213) 26.150 ms 26.142 ms 26.353 ms 16 ae27.cr2.ord2.us.zip.zayo.com (64.125.30.245) 28.457 ms 28.846 ms 28.890 ms 17 ae17.er2.ord7.us.zip.zayo.com (64.125.31.83) 26.624 ms 26.676 ms 26.195 ms 18 128.177.108.98.IPYX-142927-900-ZYO.zip.zayo.com (128.177.108.98) 28.767 ms 27.125 ms 27.485 ms 19 agg2.c13.r03.s101.chi03.singlehop.net (108.178.47.245) 28.742 ms agg1.c13.r03.s101.chi03.singlehop.net (108.178.47.247) 26.976 ms 26.960 ms 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ``` * This is not an AWS problem, it’s a Singlehop/Wordpress.org problem. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WordPress.org un-reachable from AWS US-east-1](https://wordpress.org/support/topic/wordpress-org-un-reachable-from-aws-us-east-1/) * Thread Starter [rocjoe](https://wordpress.org/support/users/rocjoe/) * (@rocjoe) * [7 years, 8 months ago](https://wordpress.org/support/topic/wordpress-org-un-reachable-from-aws-us-east-1/#post-10675465) * Yes it is DEFINITELY a networking problem, but as the traceroute results above show: there is connectivity all the way up to the very last hop before reaching wordpress.org. * In other words, it’s your website, not AWS. * Please just pass this request to somebody who actually does the networking for WordPress’s website. PLEASE. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WordPress.org un-reachable from AWS US-east-1](https://wordpress.org/support/topic/wordpress-org-un-reachable-from-aws-us-east-1/) * Thread Starter [rocjoe](https://wordpress.org/support/users/rocjoe/) * (@rocjoe) * [7 years, 8 months ago](https://wordpress.org/support/topic/wordpress-org-un-reachable-from-aws-us-east-1/#post-10671952) * Ping was unsuccessful. No reply after 19 attempts. * Results of the health-check plugins are: * ``` WordPress Version 4.9.7 ( Latest version: 4.9.8 ) - We strongly urge you to update, as minor updates are often security related. 4.9.7 ( Latest version: 4.9.8 ) - We strongly urge you to update, as minor updates are often security related. Plugin Versions Your site has 1 plugin waiting to be updated. Your site has 2 inactive plugins, it is recommended to remove any unused plugins to enhance your site security. Theme Versions Your site has 1 installed theme, and it is up to date. Your site does not have a default theme, default themes are used by WordPress automatically if anything is wrong with your normal theme. PHP Version 7.0.30-0ubuntu0.16.04.1 - For best performance we recommend using PHP 7.2 or higher. Database Server version 5.7.23-0ubuntu0.16.04.1 JSON Extension Your PHP install supports JSON. MySQL utf8mb4 support Your MySQL version supports utf8mb4 Communication with WordPress.org Unable to reach WordPress.org at 198.143.164.252: cURL error 28: Connection timed out after 10001 milliseconds HTTPS status You are accessing this website using HTTPS. Secure communication Your WordPress install can communicate securely with other services. Scheduled events No scheduled events have been missed. Background updates A previous automatic background update could not occur. You would have received an email because of this. We'll try again with the next release. The error code was mkdir_failed_pclzip. No version control systems were detected. Your installation of WordPress doesn't require FTP credentials to perform updates. Couldn't retrieve a list of the checksums for WordPress 4.9.7. This could mean that connections are failing to WordPress.org. Loopback request The loopback request to your site completed successfully. ``` Viewing 3 replies - 1 through 3 (of 3 total)