DEV Community

loading...

Ping to dev.to (ASIA -> NYC) is faster than reasonable

Ande
I love JavaScript technologies and building APIs.
Updated on ・1 min read

I wondered why dev.to is so fast. I read all available posts there is about dev.to

Today, I pinged dev.to and response time was < 60ms. The server location showed NYC, fastly. I tried pinging linode, vultr, digital ocean NYC data-centers and non of them showed < 200ms. Mostly between 200-300ms. I even pinged my empty new fresh NYC server and it was still above 200ms.

To be extra sure if dev.to really has NYC servers, I pinged from one of my NYC server and dev.to has multiple NYC IPs and all ~1ms.

How come fastly or dev.to response so fast? Where no others can't. What I'm missing? Is fastly really that fast? It doesn't even reasonable to response from NYC when I'm far in asia

Discussion (2)

Collapse
marcellothearcane profile image
marcellothearcane

My guess is an edge CDN. Does dev.to use cloudflare?

Collapse
aslasn profile image
Ande Author • Edited

I know they use cloudnary along with fastly. After inspecting the http requests you can tell they use AWS and Heroku too.