Send PLUG-discuss mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of PLUG-discuss digest..."
Today's Topics:
1. Re: what do these trace routes say? (rusty carruth)
2. Re: what do these trace routes say? (rusty carruth)
3. Re: what do these trace routes say? (rusty carruth)
4. Re: what do these trace routes say? (David Schwartz)
5. Re: what do these trace routes say? (David Schwartz)
6. Re: what do these trace routes say? (Arun Khan)
7. Re: what do these trace routes say? (Arun Khan)
8. Re: what do these trace routes say? (Arun Khan)
9. Re: what do these trace routes say? (Snyder, Alexander J)
----------------------------------------------------------------------
Message: 1
Date: Fri, 24 Jul 2026 21:09:32 -0700
From: rusty carruth <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="UTF-8"
I don't suppose you could attach these as text? I'm much better with
'diff' on the computer than 'diff' using my wetware... :-)
But, yeah, Don't get me started on GoDaddy's "support"... Wasted over
3 hours doing stuff that couldn't possibly have fixed the problem.
On Fri, 2026-07-24 at 12:23 -0700, David Schwartz via PLUG-discuss
wrote:
I?ve been having some intermittent problems reaching my hosting
server for a couple of months now, and of course everybody says it?s
not on their end and it does not seem to be on my end either.
Someone suggested I run Tracert and see what it says and I found this
stuff.
------------------------------
Message: 2
Date: Fri, 24 Jul 2026 21:31:29 -0700
From: rusty carruth <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Fri, 2026-07-24 at 21:09 -0700, rusty carruth via PLUG-discuss
wrote:
I don't suppose you could attach these as text?? I'm much better with
'diff' on the computer than 'diff' using my wetware... :-)
But, yeah, Don't get me started on GoDaddy's "support"...? Wasted
over
3 hours doing stuff that couldn't possibly have fixed the problem.
Not being fully satisfied with my answer, I decided to run 'traceroute'
on Linux Mint.
First, I tried 'tracepath'. Completely bad. It quit getting answers
once it "left the building", basically.
So, time for 'sudo apt-get install traceroute' and viola!:
Fri Jul 24 21:13:53 rusty@alienware:~$ traceroute akashicdata.com
traceroute to akashicdata.com (67.222.30.106), 30 hops max, 60 byte
packets
1 _gateway (192.168.1.1) 0.349 ms 0.329 ms 0.319 ms
2 192.168.12.1 (192.168.12.1) 0.544 ms 0.521 ms 0.504 ms
3 192.0.0.1 (192.0.0.1) 0.954 ms 0.937 ms 0.921 ms
4 192.0.0.1 (192.0.0.1) 22.966 ms 29.192 ms 17.061 ms
5 * * *
6 192.0.0.1 (192.0.0.1) 29.188 ms * 12.612 ms
7 192.0.0.1 (192.0.0.1) 12.581 ms 22.404 ms 16.884 ms
8 10.180.166.66 (10.180.166.66) 16.815 ms 22.187 ms 22.139 ms
9 10.180.162.200 (10.180.162.200) 28.079 ms 28.017 ms
10.180.162.198 (10.180.162.198) 21.990 ms
10 10.180.165.89 (10.180.165.89) 27.931 ms 10.180.165.85
(10.180.165.85) 27.875 ms 27.789 ms
11 10.177.108.0 (10.177.108.0) 33.759 ms 10.177.108.2 (10.177.108.2)
23.216 ms 23.148 ms
12 * 10.164.178.213 (10.164.178.213) 23.789 ms 23.733 ms
13 ae4.er3.lax112.us.above.net (208.185.160.101) 29.609 ms 23.795 ms
23.750 ms
14 ae12.cs1.lax112.us.zip.zayo.com (64.125.27.198) 83.639 ms
ae11.cs2.lax112.us.zip.zayo.com (64.125.30.72) 78.829 ms 78.799 ms
15 * * ae8.cr2.lax20.us.zip.zayo.com (64.125.28.47) 77.691 ms
16 ae1.cr1.lax10.us.zip.zayo.com (64.125.26.4) 71.680 ms
ae2.cr2.dfw7.us.zip.zayo.com (64.125.25.79) 77.761 ms *
17 ae2.cr2.dfw7.us.zip.zayo.com (64.125.25.79) 80.361 ms
ae20.cr1.dfw1.us.zip.zayo.com (64.125.31.168) 85.734 ms *
18 ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 84.680 ms
ae0.cr1.dfw1.us.zip.zayo.com (64.125.20.62) 75.202 ms
ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 80.042 ms
19 ae5.er2.atl10.us.zip.zayo.com (64.125.21.53) 85.845 ms
ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 73.956 ms 78.808 ms
20 ae5.er2.atl10.us.zip.zayo.com (64.125.21.53) 77.786 ms * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Fri Jul 24 21:17:37 rusty@alienware:~$
Fri Jul 24 21:13:53 rusty@alienware:~$ traceroute akashicdata.com
traceroute to akashicdata.com (67.222.30.106), 30 hops max, 60 byte
packets
1 _gateway (192.168.1.1) 0.349 ms 0.329 ms 0.319 ms
2 192.168.12.1 (192.168.12.1) 0.544 ms 0.521 ms 0.504 ms
3 192.0.0.1 (192.0.0.1) 0.954 ms 0.937 ms 0.921 ms
4 192.0.0.1 (192.0.0.1) 22.966 ms 29.192 ms 17.061 ms
5 * * *
6 192.0.0.1 (192.0.0.1) 29.188 ms * 12.612 ms
7 192.0.0.1 (192.0.0.1) 12.581 ms 22.404 ms 16.884 ms
8 10.180.166.66 (10.180.166.66) 16.815 ms 22.187 ms 22.139 ms
9 10.180.162.200 (10.180.162.200) 28.079 ms 28.017 ms
10.180.162.198 (10.180.162.198) 21.990 ms
10 10.180.165.89 (10.180.165.89) 27.931 ms 10.180.165.85
(10.180.165.85) 27.875 ms 27.789 ms
11 10.177.108.0 (10.177.108.0) 33.759 ms 10.177.108.2 (10.177.108.2)
23.216 ms 23.148 ms
12 * 10.164.178.213 (10.164.178.213) 23.789 ms 23.733 ms
13 ae4.er3.lax112.us.above.net (208.185.160.101) 29.609 ms 23.795 ms
23.750 ms
14 ae12.cs1.lax112.us.zip.zayo.com (64.125.27.198) 83.639 ms
ae11.cs2.lax112.us.zip.zayo.com (64.125.30.72) 78.829 ms 78.799 ms
15 * * ae8.cr2.lax20.us.zip.zayo.com (64.125.28.47) 77.691 ms
16 ae1.cr1.lax10.us.zip.zayo.com (64.125.26.4) 71.680 ms
ae2.cr2.dfw7.us.zip.zayo.com (64.125.25.79) 77.761 ms *
17 ae2.cr2.dfw7.us.zip.zayo.com (64.125.25.79) 80.361 ms
ae20.cr1.dfw1.us.zip.zayo.com (64.125.31.168) 85.734 ms *
18 ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 84.680 ms
ae0.cr1.dfw1.us.zip.zayo.com (64.125.20.62) 75.202 ms
ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 80.042 ms
19 ae5.er2.atl10.us.zip.zayo.com (64.125.21.53) 85.845 ms
ae11.cr1.atl10.us.zip.zayo.com (64.125.31.141) 73.956 ms 78.808 ms
20 ae5.er2.atl10.us.zip.zayo.com (64.125.21.53) 77.786 ms * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Fri Jul 24 21:17:37 rusty@alienware:~$
Fri Jul 24 21:16:54 rusty@alienware:~$ traceroute ebay.com
traceroute to ebay.com (23.11.207.242), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.385 ms 0.358 ms 0.341 ms
2 192.168.12.1 (192.168.12.1) 0.438 ms 0.413 ms 0.389 ms
3 192.0.0.1 (192.0.0.1) 0.569 ms 0.548 ms 0.811 ms
4 192.0.0.1 (192.0.0.1) 18.481 ms 18.460 ms 23.598 ms
5 * * *
6 * * 192.0.0.1 (192.0.0.1) 13.621 ms
7 192.0.0.1 (192.0.0.1) 13.599 ms 23.832 ms 23.720 ms
8 10.180.166.64 (10.180.166.64) 23.295 ms 10.180.166.66
(10.180.166.66) 23.554 ms 23.471 ms
9 10.180.162.200 (10.180.162.200) 27.329 ms 10.180.162.198
(10.180.162.198) 27.252 ms 10.180.162.200 (10.180.162.200) 27.150 ms
10 10.180.165.89 (10.180.165.89) 45.171 ms 45.033 ms 10.180.162.197
(10.180.162.197) 50.773 ms
11 10.180.165.89 (10.180.165.89) 34.800 ms 10.177.108.2
(10.177.108.2) 34.476 ms 39.708 ms
12 10.177.108.2 (10.177.108.2) 34.417 ms 39.576 ms 10.164.162.13
(10.164.162.13) 35.797 ms
13 10.177.5.200 (10.177.5.200) 47.771 ms 10.164.162.13
(10.164.162.13) 47.748 ms 10.177.5.200 (10.177.5.200) 44.047 ms
14 10.177.5.200 (10.177.5.200) 38.979 ms 38.252 ms 40.642 ms
15 10.177.118.5 (10.177.118.5) 40.605 ms 40.582 ms 10.177.118.3
(10.177.118.3) 45.874 ms
16 10.177.118.5 (10.177.118.5) 45.821 ms 66.94.0.37 (66.94.0.37)
45.785 ms 31.757 ms
17 * 66.94.0.37 (66.94.0.37) 42.779 ms *
18 * * *
19 * * *
20 a23-11-207-242.deploy.static.akamaitechnologies.com (23.11.207.242)
41.774 ms 41.699 ms *
Fri Jul 24 21:17:03 rusty@alienware:~$
Fri Jul 24 21:16:54 rusty@alienware:~$ traceroute ebay.com
traceroute to ebay.com (23.11.207.242), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.385 ms 0.358 ms 0.341 ms
2 192.168.12.1 (192.168.12.1) 0.438 ms 0.413 ms 0.389 ms
3 192.0.0.1 (192.0.0.1) 0.569 ms 0.548 ms 0.811 ms
4 192.0.0.1 (192.0.0.1) 18.481 ms 18.460 ms 23.598 ms
5 * * *
6 * * 192.0.0.1 (192.0.0.1) 13.621 ms
7 192.0.0.1 (192.0.0.1) 13.599 ms 23.832 ms 23.720 ms
8 10.180.166.64 (10.180.166.64) 23.295 ms 10.180.166.66
(10.180.166.66) 23.554 ms 23.471 ms
9 10.180.162.200 (10.180.162.200) 27.329 ms 10.180.162.198
(10.180.162.198) 27.252 ms 10.180.162.200 (10.180.162.200) 27.150 ms
10 10.180.165.89 (10.180.165.89) 45.171 ms 45.033 ms 10.180.162.197
(10.180.162.197) 50.773 ms
11 10.180.165.89 (10.180.165.89) 34.800 ms 10.177.108.2
(10.177.108.2) 34.476 ms 39.708 ms
12 10.177.108.2 (10.177.108.2) 34.417 ms 39.576 ms 10.164.162.13
(10.164.162.13) 35.797 ms
13 10.177.5.200 (10.177.5.200) 47.771 ms 10.164.162.13
(10.164.162.13) 47.748 ms 10.177.5.200 (10.177.5.200) 44.047 ms
14 10.177.5.200 (10.177.5.200) 38.979 ms 38.252 ms 40.642 ms
15 10.177.118.5 (10.177.118.5) 40.605 ms 40.582 ms 10.177.118.3
(10.177.118.3) 45.874 ms
16 10.177.118.5 (10.177.118.5) 45.821 ms 66.94.0.37 (66.94.0.37)
45.785 ms 31.757 ms
17 * 66.94.0.37 (66.94.0.37) 42.779 ms *
18 * * *
19 * * *
20 a23-11-207-242.deploy.static.akamaitechnologies.com (23.11.207.242)
41.774 ms 41.699 ms *
Fri Jul 24 21:17:03 rusty@alienware:~$
Fri Jul 24 21:20:45 rusty@alienware:~$ traceroute www.amazon.com
traceroute to www.amazon.com (18.238.89.129), 30 hops max, 60 byte
packets
1 _gateway (192.168.1.1) 1.461 ms 1.393 ms 1.225 ms
2 192.168.12.1 (192.168.12.1) 1.168 ms 1.044 ms 0.998 ms
3 192.0.0.1 (192.0.0.1) 72.847 ms 72.819 ms 72.776 ms
4 192.0.0.1 (192.0.0.1) 39.981 ms 45.115 ms 44.979 ms
5 * * *
6 192.0.0.1 (192.0.0.1) 44.784 ms 22.430 ms 22.282 ms
7 192.0.0.1 (192.0.0.1) 29.359 ms 11.880 ms 29.228 ms
8 10.180.166.66 (10.180.166.66) 29.166 ms 12.342 ms 10.180.166.64
(10.180.166.64) 28.354 ms
9 10.180.162.200 (10.180.162.200) 33.799 ms 33.768 ms 40.084 ms
10 10.180.35.146 (10.180.35.146) 40.064 ms 10.180.35.148
(10.180.35.148) 39.865 ms 10.180.35.146 (10.180.35.146) 39.804 ms
11 10.177.114.159 (10.177.114.159) 39.783 ms 39.762 ms 39.743 ms
12 10.177.114.254 (10.177.114.254) 39.715 ms 39.692 ms 27.729 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
Fri Jul 24 21:20:45 rusty@alienware:~$ traceroute www.amazon.com
traceroute to www.amazon.com (18.238.89.129), 30 hops max, 60 byte
packets
1 _gateway (192.168.1.1) 1.461 ms 1.393 ms 1.225 ms
2 192.168.12.1 (192.168.12.1) 1.168 ms 1.044 ms 0.998 ms
3 192.0.0.1 (192.0.0.1) 72.847 ms 72.819 ms 72.776 ms
4 192.0.0.1 (192.0.0.1) 39.981 ms 45.115 ms 44.979 ms
5 * * *
6 192.0.0.1 (192.0.0.1) 44.784 ms 22.430 ms 22.282 ms
7 192.0.0.1 (192.0.0.1) 29.359 ms 11.880 ms 29.228 ms
8 10.180.166.66 (10.180.166.66) 29.166 ms 12.342 ms 10.180.166.64
(10.180.166.64) 28.354 ms
9 10.180.162.200 (10.180.162.200) 33.799 ms 33.768 ms 40.084 ms
10 10.180.35.146 (10.180.35.146) 40.064 ms 10.180.35.148
(10.180.35.148) 39.865 ms 10.180.35.146 (10.180.35.146) 39.804 ms
11 10.177.114.159 (10.177.114.159) 39.783 ms 39.762 ms 39.743 ms
12 10.177.114.254 (10.177.114.254) 39.715 ms 39.692 ms 27.729 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
(no more answers to try 30)
using dnschecker.org's IPv6 traceroute:
Start: 2026-07-25T09:24:55+0500
HOST: DNSChecker.org Loss%
Snt Last Avg Best Wrst StDev
1.|-- 162.243.189.145 0.0%
3 0.8 1.4 0.6 2.7 1.2
2.|-- 143.244.192.168 0.0%
3 0.5 0.9 0.5 1.6 0.6
3.|-- ae29.sdr2.us-ewr1.as14061.net (143.244.225.96) 0.0%
3 1.1 1.6 1.1 2.5 0.8
4.|-- ae6.iar1.us-ewr1.as14061.net (143.244.225.23) 0.0%
3 0.8 0.9 0.8 1.1 0.1
5.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
6.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
8.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
10.|-- server-13-33-66-207.jfk50.r.cloudfront.net (13.33.66.207) 0.0%
3 2.9 2.3 1.7 2.9 0.6
Start: 2026-07-25T09:24:55+0500
HOST: DNSChecker.org Loss%
Snt Last Avg Best Wrst StDev
1.|-- 162.243.189.145 0.0%
3 0.8 1.4 0.6 2.7 1.2
2.|-- 143.244.192.168 0.0%
3 0.5 0.9 0.5 1.6 0.6
3.|-- ae29.sdr2.us-ewr1.as14061.net (143.244.225.96) 0.0%
3 1.1 1.6 1.1 2.5 0.8
4.|-- ae6.iar1.us-ewr1.as14061.net (143.244.225.23) 0.0%
3 0.8 0.9 0.8 1.1 0.1
5.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
6.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
8.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0
3 0.0 0.0 0.0 0.0 0.0
10.|-- server-13-33-66-207.jfk50.r.cloudfront.net (13.33.66.207) 0.0%
3 2.9 2.3 1.7 2.9 0.6
Doesn't help you much, but I found it interesting that tracepath didn't
seem to work as well as traceroute. And I have no idea if DNSChecker's
stuff can help understand it.
Oh, here. I've got a 'host in the cloud', let me do a tracepath there:
root@srv1259587:~# tracepath ebay.com
1?: [LOCALHOST] pmtu 1500
1: ??? 0.162ms
1: ??? 0.237ms
2: 172.17.2.44 0.384ms
3: 2.25.25.11 0.303ms
4: 2.25.25.1 0.318ms
5: no reply
6: be5702.agr62.phx01.atlas.cogentco.com 1.069ms
7: be3057.ccr31.phx01.atlas.cogentco.com 1.725ms
8: be2931.ccr41.lax01.atlas.cogentco.com 12.509ms
9: be3243.ccr41.lax05.atlas.cogentco.com 12.966ms
10: 38.19.140.41 11.911ms
asymm 15
11: ae6.r21.lax01.mag.netarch.akamai.com 10.756ms
asymm 13
12: ae1.r21.lax02.ien.netarch.akamai.com 11.994ms
asymm 15
13: ae-1.akamai.lsanca07.us.bb.gin.ntt.net 11.822ms
14: no reply
15: no reply
16: no reply
17: a23-210-216-154.deploy.static.akamaitechnologies.com 11.839ms
reached
Resume: pmtu 1500 hops 17 back 16
root@srv1259587:~# tracepath ebay.com
1?: [LOCALHOST] pmtu 1500
1: ??? 0.162ms
1: ??? 0.237ms
2: 172.17.2.44 0.384ms
3: 2.25.25.11 0.303ms
4: 2.25.25.1 0.318ms
5: no reply
6: be5702.agr62.phx01.atlas.cogentco.com 1.069ms
7: be3057.ccr31.phx01.atlas.cogentco.com 1.725ms
8: be2931.ccr41.lax01.atlas.cogentco.com 12.509ms
9: be3243.ccr41.lax05.atlas.cogentco.com 12.966ms
10: 38.19.140.41 11.911ms
asymm 15
11: ae6.r21.lax01.mag.netarch.akamai.com 10.756ms
asymm 13
12: ae1.r21.lax02.ien.netarch.akamai.com 11.994ms
asymm 15
13: ae-1.akamai.lsanca07.us.bb.gin.ntt.net 11.822ms
14: no reply
15: no reply
16: no reply
17: a23-210-216-154.deploy.static.akamaitechnologies.com 11.839ms
reached
Resume: pmtu 1500 hops 17 back 16
So, let me install traceroute:
root@srv1259587:~# traceroute ebay.com
traceroute to ebay.com (23.52.40.67), 30 hops max, 60 byte packets
1 169.254.0.1 (169.254.0.1) 0.371 ms 0.277 ms 0.206 ms
2 172.17.2.32 (172.17.2.32) 0.283 ms 0.320 ms 0.345 ms
3 2.25.25.11 (2.25.25.11) 0.211 ms 0.221 ms 2.25.25.12 (2.25.25.12)
0.282 ms
4 2.25.25.1 (2.25.25.1) 0.379 ms 2.25.25.2 (2.25.25.2) 0.197 ms
0.156 ms
5 148.51.176.50 (148.51.176.50) 1.041 ms 0.248 ms 1.761 ms
6 po91.cr02.ngspn.azp2.imdc.com (148.51.251.148) 1.259 ms
po91.cr01.ngspn.azp1.imdc.com (148.51.251.144) 1.309 ms 1.210 ms
7 ae0.0.er01.ngspn.azp2.imdc.com (148.51.252.67) 0.990 ms
ae1.0.er01.ngspn.azp1.imdc.com (148.51.252.69) 1.332 ms
ae1.0.er01.ngspn.azp2.imdc.com (148.51.252.71) 1.049 ms
8 8-2-1.bear1.Phoenix1.Level3.net (4.15.8.33) 1.567 ms * 1.500 ms
9 * * *
10 4637-3356-lax.sp.lumen.tech (4.68.68.78) 11.127 ms 11.086 ms
10.303 ms
11 i-95.1wlt-core02.telstraglobal.net (202.84.143.29) 10.217 ms i-
94.tlot-core02.telstraglobal.net (202.84.143.25) 10.923 ms i-95.1wlt-
core02.telstraglobal.net (202.84.143.29) 12.102 ms
12 i-95.1wlt-core02.telstraglobal.net (202.84.143.29) 191.261 ms
193.643 ms i-15105.sgcn-core01.telstraglobal.net (202.84.141.18)
179.593 ms
13 i-92.sggs01.telstraglobal.net (202.84.219.173) 186.449 ms *
185.213 ms
14 unknown.telstraglobal.net (210.57.38.6) 235.656 ms i-
91.sggs01.telstraglobal.net (202.84.244.41) 183.212 ms 184.192 ms
15 unknown.telstraglobal.net (210.57.38.6) 235.380 ms a23-52-40-
67.deploy.static.akamaitechnologies.com (23.52.40.67) 184.498 ms
unknown.telstraglobal.net (210.57.38.6) 235.327 ms
root@srv1259587:~# ping -c 2 ebay.com
PING ebay.com (23.52.40.51) 56(84) bytes of data.
64 bytes from a23-52-40-51.deploy.static.akamaitechnologies.com
(23.52.40.51): icmp_seq=1 ttl=50 time=190 ms
64 bytes from a23-52-40-51.deploy.static.akamaitechnologies.com
(23.52.40.51): icmp_seq=2 ttl=50 time=190 ms
--- ebay.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 190.111/190.150/190.190/0.039 ms
root@srv1259587:~#
root@srv1259587:~# traceroute ebay.com
traceroute to ebay.com (23.52.40.67), 30 hops max, 60 byte packets
1 169.254.0.1 (169.254.0.1) 0.371 ms 0.277 ms 0.206 ms
2 172.17.2.32 (172.17.2.32) 0.283 ms 0.320 ms 0.345 ms
3 2.25.25.11 (2.25.25.11) 0.211 ms 0.221 ms 2.25.25.12 (2.25.25.12)
0.282 ms
4 2.25.25.1 (2.25.25.1) 0.379 ms 2.25.25.2 (2.25.25.2) 0.197 ms
0.156 ms
5 148.51.176.50 (148.51.176.50) 1.041 ms 0.248 ms 1.761 ms
6 po91.cr02.ngspn.azp2.imdc.com (148.51.251.148) 1.259 ms
po91.cr01.ngspn.azp1.imdc.com (148.51.251.144) 1.309 ms 1.210 ms
7 ae0.0.er01.ngspn.azp2.imdc.com (148.51.252.67) 0.990 ms
ae1.0.er01.ngspn.azp1.imdc.com (148.51.252.69) 1.332 ms
ae1.0.er01.ngspn.azp2.imdc.com (148.51.252.71) 1.049 ms
8 8-2-1.bear1.Phoenix1.Level3.net (4.15.8.33) 1.567 ms * 1.500 ms
9 * * *
10 4637-3356-lax.sp.lumen.tech (4.68.68.78) 11.127 ms 11.086 ms
10.303 ms
11 i-95.1wlt-core02.telstraglobal.net (202.84.143.29) 10.217 ms i-
94.tlot-core02.telstraglobal.net (202.84.143.25) 10.923 ms i-95.1wlt-
core02.telstraglobal.net (202.84.143.29) 12.102 ms
12 i-95.1wlt-core02.telstraglobal.net (202.84.143.29) 191.261 ms
193.643 ms i-15105.sgcn-core01.telstraglobal.net (202.84.141.18)
179.593 ms
13 i-92.sggs01.telstraglobal.net (202.84.219.173) 186.449 ms *
185.213 ms
14 unknown.telstraglobal.net (210.57.38.6) 235.656 ms i-
91.sggs01.telstraglobal.net (202.84.244.41) 183.212 ms 184.192 ms
15 unknown.telstraglobal.net (210.57.38.6) 235.380 ms a23-52-40-
67.deploy.static.akamaitechnologies.com (23.52.40.67) 184.498 ms
unknown.telstraglobal.net (210.57.38.6) 235.327 ms
root@srv1259587:~# ping -c 2 ebay.com
PING ebay.com (23.52.40.51) 56(84) bytes of data.
64 bytes from a23-52-40-51.deploy.static.akamaitechnologies.com
(23.52.40.51): icmp_seq=1 ttl=50 time=190 ms
64 bytes from a23-52-40-51.deploy.static.akamaitechnologies.com
(23.52.40.51): icmp_seq=2 ttl=50 time=190 ms
--- ebay.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 190.111/190.150/190.190/0.039 ms
root@srv1259587:~#
Ok, now you have a LOT of useless info ;-) You're welcome! ;-)
------------------------------
Message: 3
Date: Fri, 24 Jul 2026 21:35:06 -0700
From: rusty carruth <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="UTF-8"
Oh, look! Google has a traceroute! https://gsuite.tools/traceroute
traceroute to www.amazon.com (23.214.210.134), 30 hops max, 60 byte
packets
Hop Host IP Time (ms)
1 dgw1-wan-uk-lon1.ipv4.upcloud.com 83.136.248.1 0.103
ms
2 172.17.254.8 172.17.254.8 0.212 ms
3 172.17.252.17 172.17.252.17 0.206 ms
4 172.17.255.2 172.17.255.2 0.213 ms
5 195.66.224.168 195.66.224.168 0.995 ms
6 195.66.224.168 195.66.224.168 1.107 ms
7 *
No answer any more.
------------------------------
Message: 4
Date: Fri, 24 Jul 2026 21:39:11 -0700
From: David Schwartz <[email protected]>
To: rusty carruth <[email protected]>, Main PLUG discussion list
<[email protected]>
Subject: Re: what do these trace routes say?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
This isn?t GD hosting.
And there?s very little here to diff.
It?s a pattern I don?t know how to read.
The FIRST stop is my Cox modem.
The LAST stop (where it?s shown) is my host, and in a couple of cases, eBay and
Amazon.
It?s the steps in between, and the fact that one particular IP, 100.120.100.80,
seems to be blocking traffic.
Try your own traceroutes on random domains and see what shows up. Does this one
(100.120.100.80) ever appear?
All of the stops are 2-3 ms, but the 100.120.x.y routes take 10x the time and
two of them cause timeouts for a lot of my HTTP requests.
I these nodes are NOT owned by Cox ? they seem to be set up by some unknown
company and referred to as ?shared resources?.
The problem is NOT my Cox modem, it?s NOT my CPE, it?s NOT the destination
server ? it?s something at one specific IP that shows up in the route a lot of
my web traffic takes to get to my hosting provider. (They?re located in
Atlanta, GA.)
The net effect is, I run queries to my code on my hosting account, and I get
timeouts ? because of some specific IP my traffic goes through that just seems
to block it.
It?s just strange, and I don?t know what to do about it.
-David Schwartz
On Jul 24, 2026, at 9:09 PM, rusty carruth <[email protected]> wrote:
I don't suppose you could attach these as text? I'm much better with
'diff' on the computer than 'diff' using my wetware... :-)
But, yeah, Don't get me started on GoDaddy's "support"... Wasted over
3 hours doing stuff that couldn't possibly have fixed the problem.
On Fri, 2026-07-24 at 12:23 -0700, David Schwartz via PLUG-discuss
wrote:
I?ve been having some intermittent problems reaching my hosting
server for a couple of months now, and of course everybody says it?s
not on their end and it does not seem to be on my end either.
Someone suggested I run Tracert and see what it says and I found this
stuff.
------------------------------
Message: 5
Date: Fri, 24 Jul 2026 22:13:07 -0700
From: David Schwartz <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
I just tried a traceroute to my previous host and got the same problem:
traceroute webhostingworld.net <http://webhostingworld.net/>
traceroute to webhostingworld.net <http://webhostingworld.net/>
(184.154.212.196), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.395 ms 1.158 ms 0.898 ms
2 ip70-171-233-2.tc.ph.cox.net <http://ip70-171-233-2.tc.ph.cox.net/>
(70.171.233.2) 2.793 ms 2.995 ms
ip70-171-233-3.tc.ph.cox.net <http://ip70-171-233-3.tc.ph.cox.net/>
(70.171.233.3) 1.739 ms
3 100.120.101.106 (100.120.101.106) 4.021 ms 3.672 ms 3.059 ms
4 100.120.100.80 (100.120.100.80) 2.645 ms 1.301 ms 2.070 ms
5 * * *
6 * * *
7 *^C
/Users/thetoolwiz
There?s that same 100.120.101.106 ?> 100.120.100.80 where it stops.
I kept blaming them, but they never suggested I try a traceroute.
I wonder if they?re in Atlanta?
GeoIP just says US, North America (probably since they?re an ISP)
-David Schwartz
On Jul 24, 2026, at 9:47 PM, David Schwartz <[email protected]> wrote:
Interesting ? you don?t seem to be getting any of the 100.120.x.y stops in your
routes. I get them consistently from my Win box and sometimes from my Mac, even
though both computers are attached to the same router via a local LAN on
192.168.0.1.
-David Schwartz
On Jul 24, 2026, at 9:31 PM, rusty carruth via PLUG-discuss
<[email protected]> wrote:
On Fri, 2026-07-24 at 21:09 -0700, rusty carruth via PLUG-discuss
wrote:
I don't suppose you could attach these as text? I'm much better with
'diff' on the computer than 'diff' using my wetware... :-)
But, yeah, Don't get me started on GoDaddy's "support"... Wasted
over
3 hours doing stuff that couldn't possibly have fixed the problem.
Not being fully satisfied with my answer, I decided to run 'traceroute'
on Linux Mint.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260724/dce6cced/attachment-0001.htm>
------------------------------
Message: 6
Date: Fri, 24 Jul 2026 22:53:47 -0700
From: Arun Khan <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<CAHhM8gAUbCgingHP2NY=7JgHhzmKML06zjR=mcldqlivqua...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Fri, Jul 24, 2026 at 10:13?PM David Schwartz via PLUG-discuss <
[email protected]> wrote:
I just tried a traceroute to my previous host and got the same problem:
traceroute webhostingworld.net
traceroute to webhostingworld.net (184.154.212.196), 64 hops max, 40 byte
packets
1 192.168.0.1 (192.168.0.1) 1.395 ms 1.158 ms 0.898 ms
2 ip70-171-233-2.tc.ph.cox.net (70.171.233.2) 2.793 ms 2.995 ms
ip70-171-233-3.tc.ph.cox.net (70.171.233.3) 1.739 ms
3 100.120.101.106 (100.120.101.106) 4.021 ms 3.672 ms 3.059 ms
4 100.120.100.80 (100.120.100.80) 2.645 ms 1.301 ms 2.070 ms
5 * * *
6 * * *
7 *^C
/Users/thetoolwiz
It?s the steps in between, and the fact that one particular IP,
100.120.100.80 [1], seems to be blocking traffic.
but your traceroute shows the 100.x.x.x devices responded so why do you
think they are blocking your ip traffic?
[1] The 100.x.y.z is CGNAT (Carrier Grade NAT) i.e. private IP space for
ISPs, Global scale network infrastructure providers (Tailscale) etc.
I have found 'traceroute' not that useful - not because it is a bad tool
but because many nodes in the path do not respond and it fails.
Try tcptraceroute / tcptraceroute6 to your destination host and port e.g. '
www.example.org 443'
Let us know what you discover as the root cause of the intermittent failures
--
Arun Khan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260724/9419da5f/attachment-0001.htm>
------------------------------
Message: 7
Date: Fri, 24 Jul 2026 23:03:15 -0700
From: Arun Khan <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<CAHhM8gAMciW1=mpbbs5jv-njccz43bgzkfw_7v+nd-h-g+8...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Here is the result for www.ebay.com 443 (NOTE: replace 443 with a port for
a service that you know it is running)
$ tcptraceroute www.ebay.com 443
Selected device enp1s0f0, address 10.9.8.101, port 51637 for outgoing
packets
Tracing the path to www.ebay.com (23.209.84.155) on TCP port 443 (https),
30 hops max
1 10.9.8.1 0.396 ms 0.392 ms 0.428 ms
2 10.1.61.1 0.590 ms 0.401 ms 0.531 ms
3 et-7-0-11-3.edge2.Phoenix1.Level3.net (4.18.107.185) 2.072 ms 1.409
ms 1.372 ms
4 4.4.65.18 1.469 ms 1.692 ms 2.061 ms
--snip--
8 a23-209-84-155.deploy.static.akamaitechnologies.com (23.209.84.155)
[open] 1.843 ms 1.609 ms 1.624 ms
Assuming it is running a web server listening on port 443 (did get a result)
$ tcptraceroute akashicdata.com 443
Selected device enp1s0f0, address 10.9.8.101, port 49233 for outgoing
packets
Tracing the path to akashicdata.com (67.222.30.106) on TCP port 443
(https), 30 hops max
1 10.9.8.1 0.412 ms 0.369 ms 0.396 ms
2 10.1.61.1 0.504 ms 0.497 ms 0.463 ms
3 et-7-0-11-3.edge2.Phoenix1.Level3.net (4.18.107.185) 8.005 ms 13.609
ms 2.577 ms
-- snip --
10 ae5.er2.atl10.us.zip.zayo.com (64.125.21.53) 63.241 ms 60.185 ms
60.178 ms
11 64.125.41.223.IDIA-391521-001-ZYO.zip.zayo.com (64.125.41.223) 73.401
ms 60.427 ms 60.391 ms
12 64.74.203.34 60.429 ms 60.223 ms 60.405 ms
13 106-30.semidedi11-ga.privatesystems.net (67.222.30.106) [open] 60.357
ms 60.267 ms 60.228 ms
$ tcptraceroute webhostingworld.net 443
Selected device enp1s0f0, address 10.9.8.101, port 56935 for outgoing
packets
Tracing the path to webhostingworld.net (184.154.212.196) on TCP port 443
(https), 30 hops max
1 10.9.8.1 0.249 ms 0.333 ms 0.246 ms
2 10.1.61.1 0.555 ms 0.489 ms 0.463 ms
3 et-7-0-11-3.edge2.Phoenix1.Level3.net (4.18.107.185) 7.244 ms 3.697
ms 11.401 ms
4 * * *
5 be3408.ccr32.phx01.atlas.cogentco.com (154.54.28.145) 2.453 ms 2.410
ms 2.411 ms
6 be5473.ccr22.elp02.atlas.cogentco.com (154.54.166.69) 11.170 ms
10.944 ms 10.723 ms
7 be3846.ccr32.dfw01.atlas.cogentco.com (154.54.165.29) 38.444 ms
38.634 ms 38.491 ms
8 be5384.ccr32.oma02.atlas.cogentco.com (154.54.31.94) 52.916 ms 53.135
ms 53.038 ms
9 be5068.ccr42.ord01.atlas.cogentco.com (154.54.166.74) 53.359 ms
53.343 ms 53.399 ms
10 be8184.rcr61.ord14.atlas.cogentco.com (154.54.42.82) 53.788 ms 54.135
ms 53.821 ms
11 hu0-0-0-11.nr61.b052926-0.ord14.atlas.cogentco.com (154.24.49.214)
55.752 ms 55.615 ms 55.971 ms
12 64.125.109.115.IDIA-394227-011-ZYO.zip.zayo.com (64.125.109.115)
53.928 ms 53.662 ms 53.683 ms
13 cr1.io85.cr28.ord6.us.as32475.net (173.236.76.7) 54.194 ms 54.188 ms
54.165 ms
14 * * *
15 ord6.us.as32475.net (173.236.76.65) 54.684 ms 54.663 ms 54.640 ms
16 whw.webhostingworld.net (184.154.212.196) [open] 54.427 ms 54.359 ms
54.552 ms
Looks like your web hosting node is reachable.
--
Arun Khan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260724/c1b3795e/attachment-0001.htm>
------------------------------
Message: 8
Date: Fri, 24 Jul 2026 23:08:27 -0700
From: Arun Khan <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<CAHhM8gBpriNyEOBKLCVpzCSMWSPMcO=jxsonaooryhimi5n...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
And here is the tcptraceroute to my VPS. I am not running a web server
(80,443) but ssh is (22).
Note the last line for both traces closed for 443 and open for 22.
$ tcptraceroute vps1.theitbox.biz *443*
Selected device enp1s0f0, address 10.9.8.101, port 56857 for outgoing
packets
Tracing the path to vps1.theitbox.biz (172.93.53.69) on TCP port 443
(https), 30 hops max
1 10.9.8.1 0.256 ms 0.184 ms 0.265 ms
2 10.1.61.1 0.560 ms 0.340 ms 0.341 ms
3 et-7-0-11-3.edge2.Phoenix1.Level3.net (4.18.107.185) 4.715 ms 2.026
ms 1.823 ms
4 * * *
5 HIVELOCITY.ear1.Dallas1.Level3.net (4.71.220.242) 56.093 ms 55.988 ms
55.938 ms
6 * * *
7 * * *
8 * * *
9 vps1.theitbox.biz (172.93.53.69) *[closed]* 59.858 ms 56.568 ms
56.576 ms
$ tcptraceroute vps1.theitbox.biz *22*
Selected device enp1s0f0, address 10.9.8.101, port 33817 for outgoing
packets
Tracing the path to vps1.theitbox.biz (172.93.53.69) on TCP port 22 (ssh),
30 hops max
1 10.9.8.1 0.443 ms 0.387 ms 0.277 ms
2 10.1.61.1 0.526 ms 0.365 ms 0.298 ms
3 et-7-0-11-3.edge2.Phoenix1.Level3.net (4.18.107.185) 2.013 ms 2.505
ms 1.658 ms
4 * * *
5 HIVELOCITY.ear1.Dallas1.Level3.net (4.71.220.242) 56.213 ms 56.333 ms
91.366 ms
6 * * *
7 * * *
8 * * *
9 vps1.theitbox.biz (172.93.53.69)* [open] * 56.880 ms 57.521 ms 56.863
ms
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260724/5a9a6251/attachment-0001.htm>
------------------------------
Message: 9
Date: Sat, 25 Jul 2026 09:41:41 -0700
From: "Snyder, Alexander J" <[email protected]>
To: Main PLUG discussion list <[email protected]>
Subject: Re: what do these trace routes say?
Message-ID:
<CAAqYjtNQqkjLd3z+Q7BF1R=iu2phdhywwuvzl51vw7hz4og...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I have COX Business, and I was getting hourly drops in communication ....
My MS-Teams video calls would drop, several laptops would all drop in the
last 10- minutes of the hour .... Rebooting the modem helped, but it did
not solve.
With the help of A.I., I was able to discover a known issue on my modem
firmware (Hitron CODA56), where it would "lose" the upstream signal from
Cox, so it would do non-destructive reset, and that cycle is what I saw as
a disconnection -- but it's a logic flaw that causes it to "think" it lost
the connection and so the recycle .... So, like you, I was blaming COX and
they said it wasn't them .... It wasn't until it happened while I was
working with Claude and so I pointed Claude at this issue, which it
"resolved" in like 15 minutes.
COX Business only approves a couple of modems .... So I upgraded to the
Netgear CM3000 .... been rock solid ever since.
Also, for "real" info on issues like this, use nmap to generate a TCP Dump
(pcap), which you can then investigate with WireShark.
If you need any help for any of that, let me know. Happy to assist!
--
Thanks,
Alexander
Sent from my Google Pixel Pro 10 XL
On Fri, Jul 24, 2026, 12:23 David Schwartz via PLUG-discuss <
[email protected]> wrote:
I?ve been having some intermittent problems reaching my hosting server for
a couple of months now, and of course everybody says it?s not on their end
and it does not seem to be on my end either.
Someone suggested I run Tracert and see what it says and I found this
stuff.
I called Cox and of course they want to send someone out to test all of MY
HOME LAN after determining it?s NOT my router. I just want someone there to
look at these. They don?t seem interested until they?re ruled-out my CPE.
This is intermittent. It shows up as random time-outs while I?m running
stuff on my server. But it happens from the same IPs all the time, which
are clearly on the Cox side of my router. But whois shows these IPs are
?shared resources?. I have no idea what that means.
These are screenshots (images) of some Traceroutes I ran on my Win box and
my Mac, both connected to the same router that goes to my Cox router/modem
(via wire).
-David Schwartz
---------------------------------------------------
PLUG-discuss mailing list: [email protected]
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260725/f939e77f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2026-07-24_11-48-58.png
Type: image/png
Size: 219129 bytes
Desc: not available
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260725/f939e77f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2026-07-24_11-47-19.png
Type: image/png
Size: 231876 bytes
Desc: not available
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260725/f939e77f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2026-07-24_11-47-19.png
Type: image/png
Size: 231876 bytes
Desc: not available
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260725/f939e77f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2026-07-24_11-48-58.png
Type: image/png
Size: 219129 bytes
Desc: not available
URL:
<http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20260725/f939e77f/attachment-0003.png>
------------------------------
Subject: Digest Footer
_______________________________________________
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
------------------------------
End of PLUG-discuss Digest, Vol 253, Issue 10
*********************************************