Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Moved to Fixing WordPress, this is not a Requesting WordPress topic.
Could you please ask your server hosts to help figure out this last-mile problem?
It’s not a problem with the WordPress.ORG servers, they’re just a web server on the Internet and get accessed from AWS all the time.
What error are you getting and how are you trying to download WordPress updates? Just from the dashboard?
Thread Starter
rocjoe
(@rocjoe)
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.
Hello,
traceroute is blocked on the servers so this is how a traceroute would normally look for anyone.
You can post output results of curl -vv https://wordpress.org and repost traceroute using the -I flag for ICMP “traceroute -I http://www.wordpress.org”.
