CDN performance unexplicably terrible

When installing packages via the [Fastly-provided CDN](http://permalink.gmane.org/gmane.linux.distributions.alpine.devel/3149), performance is terrible from Europe, whereas the reverse is true when accessing via an AWS instance in us-east-1.

Here are some timings:

From my workstation, in Europe:

```
$ docker run -it gliderlabs/alpine:3.3 time apk add --update --repository http://nl.alpinelinux.org/alpine/v3.3/community/ --repositories-file /dev/null go
fetch http://nl.alpinelinux.org/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
(1/1) Installing go (1.5.3-r0)
Executing busybox-1.24.1-r7.trigger
OK: 177 MiB in 12 packages
real 0m 29.71s
user 0m 0.79s
sys 0m 6.31s

$ docker run -it gliderlabs/alpine:3.3 time apk add --update go
fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
(1/1) Installing go (1.5.3-r0)
Executing busybox-1.24.1-r7.trigger
OK: 177 MiB in 12 packages
real 14m 14.96s
user 0m 0.75s
sys 0m 8.38s
```

From an AWS instance, in us-east-1:

```
$ docker run -it gliderlabs/alpine:3.3 time apk add --update --repository http://nl.alpinelinux.org/alpine/v3.3/community/ --repositories-file /dev/null go
fetch http://nl.alpinelinux.org/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
(1/1) Installing go (1.5.3-r0)
Executing busybox-1.24.1-r7.trigger
OK: 177 MiB in 12 packages
real 3m 0.32s
user 0m 2.27s
sys 0m 0.95s

$ docker run -it gliderlabs/alpine:3.3 time apk add --update go
fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
(1/1) Installing go (1.5.3-r0)
Executing busybox-1.24.1-r7.trigger
OK: 177 MiB in 12 packages
real 0m 35.05s
user 0m 2.11s
sys 0m 0.78s
```

When connecting from an AWS instance in Europe, performance is pretty good, which leads me to believe this has to do with residential internet rather than geographical location. So, since you mentioned a partnership with Fastly, I figured this might be the right place to ask: is there anything I can do to help understand / troubleshoot this (though I understand it's entirely possible that you or Fastly might be unable to fix this).

Thanks!