4 ms·
➜ curl -i https://api.exchange.coinbase.com HTTP/1.1 404 Not Found Server: cloudflare-nginx Set-Cookie: AWSELB=7541......;PATH=/ It loo
by nmjohn 11y ago
➜ curl -i https://api.exchange.coinbase.com
HTTP/1.1 404 Not Found
Server: cloudflare-nginx
Set-Cookie: AWSELB=7541......;PATH=/
It looks like they are hosted on AWS and only provide access via cloudflare.
Given that, I don't think offering paid access to be closer is really relevant.
The closest you can get physically would be to find the availability zone - however your traffic is still going to be routed through cloudflare, so you might be better being closer to the cloudflare servers handling your requests.
- jsmthrowaway 11y agoCloudflare will respond to a ping, but a request will pass through. Clever folks will realize that finding which AWS region(s) host(s) the ELB is trivial with curl --trace-time and ping, since you can deduce the RTT from Cloudflare's proxy through to the ELB. You also know geographical Route 53 and other tricks aren't in use, because you automatically lose that information through Cloudflare. I'm fairly confident it's in us-east-1 based on a quick glance.
- cobrabyte 11y agoYeah, it's mentioned in their API docs... AWS US-East https://docs.exchange.coinbase.com/#colocation https://docs.exchange.coinbase.com/#colocation
- erichurkman 11y agoThere's nothing preventing them from also opening up direct traffic to those paying for 'close' access that does not flow through CloudFlare or setting up for-pay servers in in their same availability zone(s), maybe through a direct VPN for paying customers, bypassing as much of the public internet as possible.