Getting served by wrong nodes causing high latency

Pings:

C:\Users\jarno>ping cit gg

Pinging cit gg [104.26.10.216] with 32 bytes of data:
Reply from 104.26.10.216: bytes=32 time=132ms TTL=58
Reply from 104.26.10.216: bytes=32 time=132ms TTL=58
Reply from 104.26.10.216: bytes=32 time=134ms TTL=58
Reply from 104.26.10.216: bytes=32 time=133ms TTL=58

Ping statistics for 104.26.10.216:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 134ms, Average = 132ms

C:\Users\jarno>ping cit2 net

Pinging cit2 net [104.18.43.178] with 32 bytes of data:
Reply from 104.18.43.178: bytes=32 time=96ms TTL=56
Reply from 104.18.43.178: bytes=32 time=96ms TTL=56
Reply from 104.18.43.178: bytes=32 time=97ms TTL=56
Reply from 104.18.43.178: bytes=32 time=96ms TTL=56

Ping statistics for 104.18.43.178:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 97ms, Average = 96ms

C:\Users\jarno>ping cloudflare net

Pinging cloudflare net [104.16.208.90] with 32 bytes of data:
Reply from 104.16.208.90: bytes=32 time=9ms TTL=60
Reply from 104.16.208.90: bytes=32 time=8ms TTL=60
Reply from 104.16.208.90: bytes=32 time=9ms TTL=60
Reply from 104.16.208.90: bytes=32 time=9ms TTL=60

Ping statistics for 104.16.208.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms

The are all domains served by Cloudflare. The above three are both using a different CDN location.
fl=21f249
h=cit gg
ip=145.129.xxx.xxx
ts=1584547877.784
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
colo=LHR
http=http/1.1
loc=NL
tls=TLSv1.2
sni=plaintext
warp=off

fl=11f234
h=cit2 net
ip=145.129.xxx.xxx
ts=1584547805.646
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
colo=EWR
http=http/1.1
loc=NL
tls=TLSv1.2
sni=plaintext
warp=off

fl=20f323
h=cloudflare com
ip=145.129.xx.xxx
ts=1584547864.951
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
colo=AMS
http=http/2
loc=NL
tls=TLSv1.3
sni=plaintext
warp=off

Is there anything that can explain this? It doesn’t seem to matter which DNS server I use, even with 1.1.1.1 I get the same issue.
I’m located in the Netherlands, so I assume that I should be served by the AMS node instead of a node in London (with 96 ms latency!!) or Newark.

It wouldn’t be a DNS issue, as the IP addresses for that domain should be the same worldwide.

I find it strange why doesn’t happen with all Cloudflare IP’s.
So what should I do? If I ring up my ISP, they will suggest to restart the router (which probably won’t help a bit).