Please show the output of curl -vv https://repo.hex.pm/installs/1.0.0/rebar3-3.5.1 > /dev/null. This will show how your request is routed on our CDN which can help us check if there’s an issue on that end.

-bash-4.2$ curl -vv https://repo.hex.pm/installs/1.0.0/rebar3-3.5.1 > /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* About to connect() to repo.hex.pm port 443 (#0)
*   Trying 151.101.18.2...
* Connected to repo.hex.pm (151.101.18.2) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* 	subject: CN=f2.shared.global.fastly.net,O="Fastly, Inc.",L=San Francisco,ST=California,C=US
* 	start date: Apr 01 11:41:33 2019 GMT
* 	expire date: Sep 07 16:10:08 2019 GMT
* 	common name: f2.shared.global.fastly.net
* 	issuer: CN=GlobalSign CloudSSL CA - SHA256 - G3,O=GlobalSign nv-sa,C=BE
> GET /installs/1.0.0/rebar3-3.5.1 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: repo.hex.pm
> Accept: */*
>
< HTTP/1.1 200 OK
< x-amz-id-2: wavqIHujgDuq+pIuwOtF+m/vnv83EXetJsLjOWAe6cY6Ays+9bfG0ciNUGOszvGHeKitIYQfBS4=
< x-amz-request-id: 1F6B6834269AABF2
< Last-Modified: Tue, 26 Jun 2018 18:09:35 GMT
< ETag: "3010208afbe695b2fb5b3b6b2d14d74a"
< Cache-Control: public, max-age=604800
< x-amz-meta-surrogate-key: installs
< x-amz-version-id: Xm1RMZiLIOgaasL6jDO9V9f3J7IMk2fE
< Content-Type: binary/octet-stream
< Server: AmazonS3
< Content-Length: 707955
< Accept-Ranges: bytes
< Date: Thu, 18 Jul 2019 13:15:46 GMT
< Via: 1.1 varnish
< Age: 233877
< Connection: keep-alive
< X-Served-By: cache-iad2123-IAD, cache-lcy19241-LCY
< X-Cache: HIT, HIT
< X-Cache-Hits: 1, 1
< X-Timer: S1563455746.090896,VS0,VE1
<
{ [data not shown]
* SSL read: errno -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
 32  691k   32  223k    0     0  1136k      0 --:--:-- --:--:-- --:--:-- 1145k
* Closing connection 0
curl: (56) TCP connection reset by peer

You are going through the LCY POP and the hash of the object stored there is the same as in all other POPs so since we haven’t had any other reports of issues my guess is that this is a local issue for you. Verify that you do not have any caching proxies that may have cached an old object.

423370×1114 153 KB