Diagnosing Latency Issues


#1

Sometimes customers might notice slow load times or latency on the network when attempting to retrieve assets. The short of it is it’s best to open a ticket with support@fastly as each case requires individual attention and investigation. However, to facilitate troubleshooting, please make sure your ticket includes the following information:

  1. The domain or asset you were attempting to retrieve
  2. Please access http://www.fastly-debug.com/ and send over the text block that’s generated. This may reveal any routing issues.
  3. Please run a traceroute or mtr to the host you were trying to access. This can reveal path latency and any packet loss.
traceroute < URL >

`mtr -rwc 20 <URL>`

4 . A output of a curl with response times.

curl -svo /dev/null <URL>  -w '\nLookup time:\t%{time_namelookup}\nConnect time:\t%{time_connect}\nApp Con time:\t%{time_appconnect}\nPreXfer time:\t%{time_pretransfer}\nRedirect time:\t%{time_redirect}\nStartXfer time:\t%{time_starttransfer}\n\nTotal time:\t%{time_total}\n'


Diagnosing fastly setup for amazon s3 bucket