Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_TIMED_OUT on code.jquery.com from the Philippines #95

Closed
vincejv opened this issue Jul 16, 2023 · 4 comments
Closed

ERR_TIMED_OUT on code.jquery.com from the Philippines #95

vincejv opened this issue Jul 16, 2023 · 4 comments
Labels

Comments

@vincejv
Copy link

vincejv commented Jul 16, 2023

In reference to #91
I'm having the same issue as the issue described above, my IP Block is 180.190.186.x.
ISP: Globe Telecom Philippines
Error in chrome/network tab is ERR_TIMED_OUT

Traceroute and Ping works fine

MTR for 69.16.175.42

 Host                                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 172.17.176.1                                                    0.0%     5    0.4   0.4   0.3   0.4   0.0
 2. 172.16.0.1                                                      0.0%     5    0.9   0.7   0.5   0.9   0.1
 3. 180.191.13.124                                                  0.0%     5    7.0  17.6   6.2  60.7  24.1
 4. 180.191.13.78                                                   0.0%     5   59.4  58.0  30.7 100.1  28.5
 5. (waiting for reply)
 6. (waiting for reply)
 7. 210.57.81.65                                                    0.0%     5   40.7  54.3  40.4 107.9  29.9
 8. 202.84.157.38                                                   0.0%     5   42.3  45.5  42.3  55.5   5.6
 9. 202.84.141.210                                                  0.0%     5  175.4 180.3 175.4 192.2   8.0
10. 202.84.247.17                                                   0.0%     5  177.8 177.3 176.9 177.8   0.4
11. 151.139.72.3                                                    0.0%     4  175.8 181.1 175.8 196.3  10.2
12. 151.139.72.14                                                   0.0%     4  174.0 173.6 173.0 174.0   0.4
13. 69.16.175.42                                                    0.0%     4  176.1 176.0 175.5 176.3   0.4

MTR for 69.16.175.10

 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 172.16.0.1                                                                0.0%    42    1.3   1.1   0.9   2.5   0.2
 2. 180.191.13.124                                                            0.0%    41    6.7  16.1   6.3  61.8  12.9
 3. 180.191.13.74                                                             0.0%    41   28.9  49.1  13.8 111.8  26.5
 4. (waiting for reply)
 5. (waiting for reply)
 6. 210.57.65.25                                                              0.0%    41   79.2  59.8  46.1 117.5  15.8
 7. 202.84.224.198                                                            2.4%    41   60.3  57.8  48.2  79.1   7.3
 8. 202.84.224.198                                                            0.0%    41  200.4 208.4 200.3 226.1   6.9
 9. 202.84.136.2                                                              0.0%    41  195.2 201.9 194.2 214.3   6.3
10. 202.84.247.17                                                             0.0%    41  194.7 200.9 193.3 225.3   7.2
11. 151.139.72.6                                                              0.0%    41  192.4 198.1 191.2 207.5   6.1
12. 151.139.72.14                                                             0.0%    41  191.6 196.7 190.3 203.9   5.8
13. 69.16.175.10                                                              0.0%    41  194.7 200.0 193.3 219.4   7.2
PING code.jquery.com (69.16.175.10) 56(84) bytes of data.
64 bytes from tlb.hwcdn.net (69.16.175.10): icmp_seq=1 ttl=50 time=194 ms
64 bytes from tlb.hwcdn.net (69.16.175.10): icmp_seq=2 ttl=50 time=196 ms
64 bytes from tlb.hwcdn.net (69.16.175.10): icmp_seq=3 ttl=50 time=194 ms
64 bytes from tlb.hwcdn.net (69.16.175.10): icmp_seq=4 ttl=50 time=194 ms
--- code.jquery.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 194.371/194.924/196.470/0.892 ms
PING code.jquery.com (69.16.175.42) 56(84) bytes of data.
64 bytes from hwcdn.net (69.16.175.42): icmp_seq=1 ttl=50 time=176 ms
64 bytes from hwcdn.net (69.16.175.42): icmp_seq=2 ttl=50 time=177 ms
64 bytes from hwcdn.net (69.16.175.42): icmp_seq=3 ttl=50 time=177 ms
64 bytes from hwcdn.net (69.16.175.42): icmp_seq=4 ttl=50 time=176 ms
^C
--- code.jquery.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 176.128/176.345/176.559/0.209 ms
@vincejv
Copy link
Author

vincejv commented Jul 17, 2023

Source IP: 180.190.186.170
ISP: Globe Telecom Philippines
ASN: AS4775
jQuery IPs: 69.16.175.10, 69.16.175.10
Latest date/time of experience: 2023-07-17T05:10:22Z

Packet dump and Chrome HAR
har_packetdump-code_jquery_org.zip

@Krinkle
Copy link
Member

Krinkle commented Jul 20, 2023

@vincejv I suspect there may be an routing problem with Globe Telecom Philippines to certain parts of the Internet. This is not something we can address.

The IPs are those of hwcdn.net and tlb.hwcdn.net (StackPath Highwinds) which is our CDN provider. Can you confirm that the issue also happens via curl on the command-line, and that it affects all three of our main CDN domains?

$ time curl -I 'http://code.jquery.com/color/jquery.color.svg-names-2.0.0.js'

And for example these unrelated websites that also happen to be Highwinds customers?

@vincejv
Copy link
Author

vincejv commented Jul 24, 2023

@vincejv I suspect there may be an routing problem with Globe Telecom Philippines to certain parts of the Internet. This is not something we can address.

@Krinkle would that be the case even if my MTR shows it can route to CDN without any issues?
MTR on my end seems like it can reach jQuery's CDN, tried both TCP, UDP and ICMP probes, no issues with MTR.

@Krinkle
Copy link
Member

Krinkle commented Jul 27, 2023

From talking with Vince in our Matrix channel, I believe this was likely the result of our CDN inadvertently blocking incoming requests from known Tor relays.

I'll raise this more generally with our (next) CDN provider, but for now this particular issue was solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants