IP database workflow
IP Geolocation Propagation Tracker
Track an IP prefix across common geolocation databases with browser-saved provider status, observation timestamps, and direct links to live lookup tools.
Saved in this browser
Track one geolocation change without a spreadsheet.
The tracker stores only in the visitor’s browser. No prefix or observation status is submitted to LogicWeb.
Database checklist
Record what each provider shows.
Open the provider, perform its lookup, then record the observation here. Status changes are timestamped in this browser.
Progress is stored locally in this browser only.
What propagation means
IP geolocation is database data, not GPS.
An IP prefix does not physically contain a city or country. Providers infer location from registry data, operator submissions, routing signals, commercial observations, and their own models. Different databases can update on different schedules.
- Use a representative routed IP from the prefix when a provider does not accept CIDR input.
- Confirm WHOIS/SWIP and any supported geofeed or correction process.
- Expect providers to disagree temporarily after a change.
- Do not promise a database update time you do not control.
- For production applications, test the actual database your application or customer uses.
IP operations toolkit
Keep working with the address space.
Use the other LogicWeb tools for pricing, planning, routing, and deployment.
Need a page for a specific prefix or workload? Browse the IP leasing guides.
From planning to production
Need a lease with geolocation updates included?
LogicWeb publishes IPv4 /24 through /18 and IPv6 /48, /32, and /29 lease options with routing and registry support.