Cloudfront domain Request timed out

0

From last few days I am facing this issue, I think it's network issue

Cloudfront giving very slow response, my assets load very slow, so I have traceroute and following is result of it I have replace subdomain with dummy text because I don't want to expose my cloudfront subdomain in public.

C:\Users\jigs>tracert MYCLOUDFRONTSUBDOMAIN.cloudfront.net

Tracing route to MYCLOUDFRONTSUBDOMAIN.cloudfront.net [108.159.80.52] over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1 2 2 ms 2 ms 2 ms 116.74.88.1 3 3 ms 2 ms 2 ms 100.74.116.1.hathway.com [116.74.100.1] 4 15 ms 14 ms 16 ms 136.232.18.13.static.jio.com [136.232.18.13] 5 28 ms 25 ms 31 ms 172.16.92.145 6 26 ms 33 ms 31 ms 172.16.92.145 7 32 ms 25 ms 31 ms 99.82.178.202 8 29 ms 28 ms 24 ms 52.95.65.213 9 21 ms 21 ms 21 ms 52.95.67.57 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 30 ms 32 ms 21 ms server-108-159-80-52.bom78.r.cloudfront.net [108.159.80.52]

Trace complete.

Can anyone tell what is the issue? and how can I fix it?

  • A few questions before going further:

    1. Are you trying it from within a corporate network?
    2. If yes, are you going via a corporate proxy?
    3. Have you tried reaching out to your Distributions domain from outside the corporate network, like from your home network?
已提問 1 年前檢視次數 218 次
1 個回答
0

Unfortunately this doesn't really tell us anything about the problem. It's not uncommon for internet routers to be configured not to respond to ICMP. You can see that the CloudFront cache host responds to all three ICMP requests with reasonable response times.

Take a look at this blog post for an overview of how to approach performance testing with CloudFront.

AWS
專家
Paul_L
已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南