How to make an accurate Geo-IP database
summary
Claims a Geo‑IP built on real‑time BGP/ASN feeds and a global monitoring fabric that detects stale or misleading records; demonstrates traceroutes from DigitalOcean and Linode proving prefixes advertised in the US actually terminate in London. Uses a cross‑platform tool called Bastard Trace, a maintained reverse DNS and ASN database, and algorithms plus human labeling. Runs 300+ agents worldwide, exposes API and offline DB, and reports 80% coverage of ~46 million Russian IPs with 100% planned next month.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:02What is IPIP
- 3:23Current GeoIP issues
- 4:57Why its hard to make it accurate
- 6:47Example
- 7:58Locationbased services
- 10:15Typical use cases
- 12:42How to evaluate GeoIP database
- 13:17GeoIP query page
- 13:53Bastard trace
- 15:46Frequency
- 19:38Virtualize
- 25:11Insights
- 26:51DNS database
- 29:04IP address
- 29:32New service
- 29:55Russian IP status
- 31:20Roadmap
- 32:50Crossplatform
- 34:03Session Question
related talks
25mMeasuring the Internet with Python
59mCatching Malware En Masse: DNS and IP Style
29mUsing the Internet as Your Load-Balancer
28mGeolocation EXPLAINed
22mAPT Attribution and DNS Profiling
43mWho are the people in your neighborhood? Tracking 'Shady' CIDR blocks
16mA System to Detect Forged-Origin BGP Hijacks
23mNetBouncer: Active Device and Link Failure Localization in Data Center Networks