repo.typesafe.com/typesafe/releases is currently not being proxyed, but a large number of artifacts come from there and could benefit from proxying. repo.typesafe.com is on AWS, so might not actually make a difference, so needs benchmarking.
=> dig repo.typesafe.com
; <<>> DiG 9.7.6-P1 <<>> repo.typesafe.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11687
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;repo.typesafe.com. IN A
;; ANSWER SECTION:
repo.typesafe.com. 3600 IN CNAME typesafe.jfrog.org.
typesafe.jfrog.org. 300 IN CNAME cloud22.jfrog.org.
cloud22.jfrog.org. 300 IN CNAME ec2-23-21-39-75.compute-1.amazonaws.com.
ec2-23-21-39-75.compute-1.amazonaws.com. 600236 IN A 23.21.39.75
;; Query time: 55 msec
;; SERVER: 204.14.152.2#53(204.14.152.2)
;; WHEN: Fri Jan 25 14:37:37 2013
;; MSG SIZE rcvd: 155
repo.typesafe.com/typesafe/releases
is currently not being proxyed, but a large number of artifacts come from there and could benefit from proxying.repo.typesafe.com
is on AWS, so might not actually make a difference, so needs benchmarking.