Cloudflare support has directed me here. Cloudflare apparently uses IPInfo for IP information IPinfo is the IP geolocation data provider of Cloudflare - IPinfo Updates / Announcement - IPinfo Community.
IP 2600:1900:0:3a04::e01 in my Cloudflare security logs shows it is from Israel but a RIPEstat · 2600:1900:0:3a04::e01 said it is from Australia.
IPInfo check IP 2600:1900:0:3a04::e01, indicates this IP to be located in Israel: NetName: Google LLC, ANS: AS396982.
The AS396982 with prefix 2600:1900:40b0::/44 indicates: Prefix, Type, Percent, Country: 2600:1900:40b0::/44, IPv6, 100%, AU. This is Australia.
Cloudflare reported the country location for IP: 2600:1900:0:3a04::e01 to be located in Israel, within the Security-Events logs in my domain. I have deployed a project in Google Cloud Platform in the Australian region (only).
I have found more IPs in my logs that are showing country different to what a RIPEStat check is showing. And months ago, these same IPs in my logs were a match to an RIPEStat check.
It is important that Security-Events logs report the correct IP information so as to block (if needed) by country, if this is not accurate, this affects web APIs etc…
Which is correct? if IP is in Israel (reported by IPInfo) then Google Cloud Platform is pulling the wool (deployed in Australia only), or is the IP as reported be RIPE in Australia?
Hi there. I actually saw that post and wanted to reply but the thread was closed and locked.
I highly recommend giving this comment a read:
https://community.cloudflare.com/t/wrong-location-for-webs-speed-report/813757/8
Let me know your thoughts. Thank you.
20/8/2024 deployed web services to GCP Australian region only. All services communicating.
Cloudflare Geo-Blocking configuration allowing only AU IPs. I would expect that if we deploy our services to GCP in Australian region only, this would be obeyed.
Now, same web services in GCP Australian region only, services responding with 503. Cloudflare Geo-Blocking configuration allowing only AU IPs.
Same IPs now indicated by IPInfo (Cloudflare provider) are located in Israel, this is not allowed by Cloudflare Geo-Blocking configuration allowing only AU IPs. This means that Cloudflare configuration needs to change because of IPInfo IP information.
RIPE Stat and MaxMind check indicate IPs are located in Australia.
IPInfo check indicates IPs are located in Israel.
MaxMind check:
IPInfo check:
2600:1900:0:3a04::e01 IP Address Details - IPinfo.io
I will raise a ticket with engineering. Thank you.
The issue has been resolved. Please review. We have made some engineering fixes and can confirm, based on active measurements, that the IPv6 address is located in Australia.
Cloudflare Security→Analytics filter for IP: 2600:1900:0:3a04::100.
Same IP, same ASN: 396982 - GOOGLE-CLOUD-PLATFORM
One request at: Jul 30, 2025 8:33:25 AM the other at: Jul 30, 2025 8:33:36 AM.
Country: Australia then Israel, what? Isreal is blocked, Australia is not.
RIPE stat: RIPEstat · 2600:1900:0:3a04::100 indicates Australia.
We found complementary data to support our updated location data, which places it in AU instead of IL.
Please understand that RIPE Stat data is a self-published statement of the IP address location, which often differs from the actual location of the IP. So, we do not rely on it as a primary source for our data.
Thank you. If you have any feedback or questions, feel free to reach out to me.
“RIPE Stat data is self-published….location of the IP”. RIPE Stat uses Maxmind GeoLite as the Geolocation database. IP: 2600:1900:0:3a04::100 RIPE Stat has it in Australia.
Your statement “IP address location, which often differs from the actual location” pertains to IPInfo as well as described.
If you have read my last post you will see that the IP is different.
Two requests only 11 seconds apart in my Cloudflare Security→Analytics logs.
Country: Australia then Israel, in the logs for the same IP: 2600:1900:0:3a04::100.
My apologies. They were IPv6 addresses and I assumed in both instances you were talking about the same IP address.
Please let me know if there are any unresolved issues remaining. We identified an issue in our data pipeline based on your feedback, and the data we are showing now should be very accurate. You can confidently trust it.
