# Is GeoIP2 planned to be included by default in NGINX?

**URL:** <https://community.nginx.org/t/is-geoip2-planned-to-be-included-by-default-in-nginx/10794>\
**Category:** General Discussion\
**Created:** [September 1, 2026, 10:28pm UTC](https://community.nginx.org/t/is-geoip2-planned-to-be-included-by-default-in-nginx/10794 "2026-09-01T22:28:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chanu](https://avatars.discourse-cdn.com/v4/letter/c/b782af/32.png) [@Chanu](https://community.nginx.org/u/Chanu)\
**Post date:** [September 1, 2026, 10:28pm UTC](https://community.nginx.org/t/is-geoip2-planned-to-be-included-by-default-in-nginx/10794/1 "2026-09-01T22:28:07Z")

</div>

> <https://github.com/nginx/nginx/pull/1655>
>
> Introduce \`ngx\_http\_geoip2\_module\` and \`ngx\_stream\_geoip2\_module\` backed by the …maintained \`libmaxminddb\`
> 
> \## Problem
> 
> The legacy database format reached End-of-Life in 2022. MaxMind stopped updating \`GeoIP.dat/GeoIPCity.dat\` (the legacy binary format \`ngx\_http\_geoip\_module/ngx\_stream\_geoip\_module\` consume via \`libGeoIP\`).
> 
> \## Solution
> 
> Introduce \`ngx\_http\_geoip2\_module\` and \`ngx\_stream\_geoip2\_module\` backed by the maintained \`libmaxminddb\` (MaxMind GeoIP2 C library) and MMDB database format.
> 
> \## Testing
> 
> Describe how you tested the change (manual testing, automated tests,
> regression tests, etc.).
> 
> \- \[x\] Manual Testing
> \- \[x\] Functional Testing (\[nginx-tests\](https://github.com/nginx/nginx-tests))
> 
> \*\*Closes:\*\* #1460
> 
> \## Checklist
> 
> Before submitting this PR, please confirm:
> 
> \- \[x\] I have read the \[CONTRIBUTING\](https://github.com/nginx/nginx/blob/master/CONTRIBUTING.md) guidelines
> \- \[x\] I have added tests (if applicable) to validate my changes
> \- \[x\] All existing tests pass
> \- \[x\] I have updated documentation where necessary
> \- \[x\] My branch is rebased on the latest master
> \- \[x\] This PR targets the master branch from my fork
> \- \[x\] My commit message follows NGINX standards (imperative mood, clear
> subject, references related issue if applicable, and contains only
> relevant changes)
> 
> \## Release Notes
> 
> If this change affects users, please add a short note here describing
> the impact for release documentation.

Once this pull request is merged, will we no longer need to dynamically compile the [GeoIP2 module](https://github.com/leev/ngx_http_geoip2_module)?

---

<div class="post-metadata">

**Author:** ![ac000](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/ac000/32/207_2.png) [@ac000](https://community.nginx.org/u/ac000)\
**Post date:** [September 2, 2026, 12:18am UTC](https://community.nginx.org/t/is-geoip2-planned-to-be-included-by-default-in-nginx/10794/2 "2026-09-02T00:18:02Z")

</div>

Correct.

---

<div class="post-metadata">

**Author:** ![system](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/system/32/19_2.png) [@system](https://community.nginx.org/u/system)\
**Post date:** [September 4, 2026, 12:18am UTC](https://community.nginx.org/t/is-geoip2-planned-to-be-included-by-default-in-nginx/10794/3 "2026-09-04T00:18:05Z")

</div>

Closed on September 4, 2026, 12:18am UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.