use GIT_CURL_VERBOSE=1 GIT_TRACE=1 git <command> will print out full trace. you can also try other environment variables from https://git-scm.com/book/tr/v2/Git-Internals-Environment-Variables
In my experiences, this is usually caused by MTU discovery issue. On Thu, Feb 23, 2017 at 7:40 AM, Bob Evans <b...@fiberinternetcenter.com> wrote: > Hello NANOGers, > > I have one customer that claims that 2 out of 17 downloads using the git > command on github's service are slow and poor on our network when compared > to others. > > However, when not using the git command , but using a simple web page link > to a large zipped file from github, its always nice and fast. Using the > git command 8% of the time being slow is unacceptable. Github just doesnt > responds lethargically at best. BTW, have you seen how many hex digits a > github ticket number is ? > > Of course Github says try a different ISP...Customer tries to tell me > comcast is better ! What ! I dont believe it. No help from Github NOC - we > have asked and asked... And we peer with Github and for some reason they > do not transmit the Prefixes of the IP range that the customer uses for > the git command. github.com resolve IPv4 is not in the prefix list. So > the exit is transits. > > I need more clues. Is it the resources the git command uses when checking > files for dates etc ? > > Thank You > Bob Evans > CTO > > > > > >