New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I actually had to unplug my hardware probe.
I was wondering why I had DNS resolve problems.
The prob was sending out thousands of DNS queries, within minutes we got 12k.
You might wanna rate limit things.
Please PM me your probe's dashboard link and any other details you have, e.g. source of the data. I'll check and open a GitHub issue to handle this
Shouldn't be that much unless you have small cache and local recursive resolver re-queries most requests
It is sadly, I first run into hitting the pihole limit of 1000 queries.
Then I run into another issue, getting rate limited by public resolvers and so on.
In the end, applications fail to work on your local network because of this.
Jin Maek, what’s the progress of the project? Any data commercialization plans?
We're a small team so it's not moving as fast as I would like to but we keep releasing new features and improvements.
The next big release is going to be CDN and DNS rankings and performance data.
That should attract the attention of bigger companies who might be willing to sponsor the development of the project or donate to get credits to run their own tests.
We decided to run an experiment and use AI to generate an overview of the changes we made in July and previous months as I think it was difficult for users to follow our progress across all the repos https://blog.globalping.io/whats-new-july-2026/
What do you think? Useful? Acceptable use of AI?
Two quick questions:
The IPs that I reported a few months ago for being recorded as ZA while actually being in RO still show ZA. Should I submit another report?
Is it pointless to have more than one probe on multiple servers that go through the same gateway?
I think that's acceptable. I'd rather the AI just collect the information and not write everything itself, but that's not a big deal.
What if the geofeed is wrong or a lie? Most databases will only care about the geofeed. I couldn't even get IPFire to change a dozen locations even after submitting proof, they just told me to go back to the providers and ask them to fix the geofeed.
Unfortunately there's not much we can do right now. There's a task to improve the flow of locations and self setting them. But until we implement it, we're stuck reviewing the reports only to ensure our algorithm works correctly and report fixes to DBs.