# MaxMindDB needs update

**URL:** https://meta.discourse.org/t/maxminddb-needs-update/108295
**Category:** Feature
**Tags:** maxmind
**Created:** [February 4, 2019, 9:01am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295 "2019-02-04T09:01:50Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [February 4, 2019, 9:01am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/1 "2019-02-04T09:01:50Z")

</div>

The version of MaxMindDB being shipped with discourse seems to have got outdated (it reports my IP from an incorrect city/state) whilst, checking the same IP against their GeoIP2 demo, It reports the Correct State/City.

The effect for the same is visible here on meta Under the `recently used devices` section.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 4, 2019, 9:04am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/2 "2019-02-04T09:04:49Z")

</div>

Should we update this @nbianca?

---

<div class="post-metadata">

### Author: ![nbianca](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nbianca/32/157984_2.png) [@nbianca](https://meta.discourse.org/u/nbianca)
#### Post date: [February 4, 2019, 9:14am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/3 "2019-02-04T09:14:35Z")

</div>

I’m planning to add an auto-update job for MaxMindDB.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 4, 2019, 9:14am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/4 "2019-02-04T09:14:56Z")

</div>

It’s probably fine for now to update it in each release.

---

<div class="post-metadata">

### Author: ![nbianca](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nbianca/32/157984_2.png) [@nbianca](https://meta.discourse.org/u/nbianca)
#### Post date: [February 4, 2019, 9:21am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/5 "2019-02-04T09:21:03Z")

</div>

That’s what we do now (we ship MaxMindDB with the Docker image), but doesn’t seem to be good enough because the MaxMindDb updates more often than our image.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [February 4, 2019, 9:22am UTC](https://meta.discourse.org/t/maxminddb-needs-update/108295/6 "2019-02-04T09:22:13Z")

</div>

We want a new image shortly anyway, for the new redis and a bunch of gem updates