All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Chasing sub-20ms TTFB to Cloudflare protected API in Amsterdam
abramovich
Member
Hi everyone,
I'm currently testing different infrastructure options in Amsterdam to get the lowest possible latency to a specific API behind CF.
Based on my tests, the origin is almost certainly in DigitalOcean.
I've tested several VPS providers in the area. My current best result is around 27-35ms TTFB and 80+ from DO.
However, I've seen results from other setups hitting under 20ms, so I know there is room for improvement. It seems like a lot of providers have "sub-optimal" routing where the traffic leaves Amsterdam and comes back, even though both the source and the destination are in the same city.
I need a provider in Amsterdam that has the most direct/optimized peering with Cloudflare. I'm currently looking at DataPacket, HostKey, and NFOrce, but I'm open to any suggestions for niche or premium network providers.
Thanks!
Comments
An endpoint to test would be great. Any provider with direct peering to CF could probably easily top that.
for reference we Have peering to Cloudflare in the UK and just pinging our site which we put behind Cloudflare and this is what we get
PING ganderweb.co.uk (172.66.40.183) 56(84) bytes of data.
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=1 ttl=57 time=7.44 ms
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=2 ttl=57 time=7.54 ms
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=3 ttl=57 time=7.50 ms
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=4 ttl=57 time=7.54 ms
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=5 ttl=57 time=7.49 ms
64 bytes from 172.66.40.183 (172.66.40.183): icmp_seq=6 ttl=57 time=7.73 ms
TTFB != Ping
Also, since you are talking about an API (so none of the CDN bits of CF really apply), it would be important to know where the backend server actually is.
If the backend is in the US, you will never get 20ms in NL.
Feel free to take a peak at our Looking glass: https://am-nl-eu.lg.as40663.net/
For example, LowEndTalk is behind Cloudflare and this is what we get:
Unsure how that differs from API specific IPs though.
Just think it as cache miss.
Alice <-> CF <-> Bob
Alice <-> CF ≈ ping
So, the solution is to reduce ping e.g CF machine within the same datacenter and the closest to Bob.
If @abramovich gets around 20ms. That means the location must be 20ms away. So, that's western, north, central Europe
We have peering to Cloudflare directly in Amsterdam, 0.7ms max ping.