Imagine: an e-commerce store shows prices in euros to a Russian user — and they leave for a competitor. Or a site blocks content for a region where it's legal. Incorrect region detection can lose up to 30% of conversions. GeoIP solves these problems, but only with proper configuration. IP-based region detection is the foundation for content personalization, regional pricing, and analytics. The task seems simple, but there are many nuances: database accuracy, IPv6, proxies and VPNs, caching, data updates. We use proven solutions that have shown themselves in production on hundreds of projects. Integration pays off through increased revenue. We don't just install a database — we set up the entire pipeline: from getting the real IP behind a load balancer to caching results. Below is how it works in practice, with specific configs and code.
Comparison of GeoIP Databases
| Database | Price | Accuracy (Russian cities) | Latency | Update | Payoff |
|---|---|---|---|---|---|
| MaxMind GeoLite2 | Free | ~80% | <0.1 ms | Weekly | Pays off with conversion growth |
| MaxMind GeoIP2 City | Paid | ~85-90% | <0.1 ms | Weekly | Pays off with regional pricing |
| ip-api.com | Free (45 req/min) | ~75% | 50-200 ms | Real-time | Doesn't pay off due to latency |
Local MaxMind GeoLite2 database is 10x faster than HTTP APIs and independent of external services. For e-commerce with regional pricing, GeoIP2 City justifies the cost.
Why Local Database Faster Than API?
An HTTP request to ip-api.com takes 50–200 ms — with thousands of visitors, this causes noticeable delay on each response. A local MMDB database reads in <0.1 ms, creates no network calls, and works even during temporary issues with an external API. As a result, you reduce TTFB and improve Core Web Vitals.
Installing the GeoIP Database
apt-get install geoipupdate # Edit /etc/GeoIP.conf with your AccountID and LicenseKey geoipupdate # Add to crontab: 0 3 * * 3 /usr/bin/geoipupdate Integration in PHP (Laravel)
Service class for working with the database, caching, and private IP detection:
// app/Services/GeoIpService.php use GeoIp2\Database\Reader; use GeoIp2\Exception\AddressNotFoundException; use Illuminate\Support\Facades\Cache; class GeoIpService { private Reader $reader; public function __construct() { $this->reader = new Reader(config('geoip.database_path')); } public function lookup(string $ip): array { if ($this->isPrivateIp($ip)) { return $this->defaultResult(); } try { $record = $this->reader->city($ip); return [ 'country_code' => $record->country->isoCode, 'country_name' => $record->country->name, 'region_code' => $record->subdivisions[0]?->isoCode, 'region_name' => $record->subdivisions[0]?->name, 'city' => $record->city->name, 'latitude' => $record->location->latitude, 'longitude' => $record->location->longitude, 'timezone' => $record->location->timeZone, 'is_vpn' => false, ]; } catch (AddressNotFoundException) { return $this->defaultResult(); } } public function lookupCached(string $ip): array { return Cache::remember( "geoip:{$ip}", 86400, // 24 hours fn() => $this->lookup($ip) ); } private function isPrivateIp(string $ip): bool { if (str_starts_with($ip, '::1') || str_starts_with($ip, 'fc') || str_starts_with($ip, 'fd')) { return true; } return filter_var($ip, FILTER_VALIDATE_IP, FILTER_FLAG_NO_PRIV_RANGE | FILTER_FLAG_NO_RES_RANGE) === false; } private function defaultResult(): array { return [ 'country_code' => config('geoip.default_country'), 'region_name' => null, 'city' => null, 'timezone' => config('app.timezone'), ]; } } Middleware for detecting region and storing in session:
// app/Http/Middleware/DetectUserRegion.php public function handle(Request $request, Closure $next): Response { if (!$request->session()->has('geo')) { $ip = app(GeoIpService::class)->getClientIp($request); $geo = app(GeoIpService::class)->lookupCached($ip); $request->session()->put('geo', $geo); } View::share('userGeo', $request->session()->get('geo')); return $next($request); } How to Set Up Caching for High Traffic?
For sites with thousands of unique IPs per hour, we use Redis with a TTL of 24 hours. Caching by IP reduces database lookups dozens of times. The lookupCached method in the class above does this automatically. On regular projects, storing the result in the session on first visit is enough.
Configuring Real IP Behind a Proxy
Nginx and Cloudflare pass the original IP via headers. Trust only known ranges; for example, in Laravel 11 configure trusted proxies in bootstrap/app.php, specifying ranges 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. For Cloudflare, handle the CF-Connecting-IP header separately.
IPv6 Support
MaxMind GeoLite2 supports IPv6. In PHP, you need to supplement the private address check: the code is already included in the isPrivateIp method above.
Typical Mistakes in GeoIP Integration
- Ignoring private IPs — querying the database with local network addresses will return an error. Check via
isPrivateIp. - No caching — under high load, each request will read the MMDB file, increasing response time. Caching in Redis reduces load dozens of times.
- Incorrect proxy handling — if trusted proxies are not configured, the real IP will be detected incorrectly, nullifying all personalization.
Work Process and Cost
| Stage | What We Do | Result |
|---|---|---|
| Analytics | Study infrastructure, proxies, accuracy requirements | Database choice and strategy |
| Installation | Install database, set up updates, service code | Working GeoIP module |
| Integration | Middleware, caching, proxy handling | Automatic region detection |
| Testing | Verify with real IPs, VPN, IPv6 | Accuracy report |
| Documentation | Describe operation, support | Ready-made regulation |
What's Included
- Database selection — analyze load and accuracy requirements, recommend GeoLite2 or GeoIP2 City.
- Installation and configuration — deploy database, set up automatic updates.
- Module development — service class, middleware, caching.
- Proxy handling — configure trusted proxies for Nginx/Cloudflare.
- Testing — verify with real IPs, including IPv6 and VPN.
- Documentation — describe operation and support instructions.
Implementation timeline — from 2 to 5 business days depending on infrastructure complexity. Cost is calculated individually after analyzing the current architecture. Contact us for a consultation — we will evaluate your project and propose the optimal solution. Order turnkey GeoIP integration — get a ready-made solution with documentation and support. We guarantee accuracy and performance.







