# Request: Fly IP ranges

**URL:** <https://community.fly.io/t/request-fly-ip-ranges/127>\
**Category:** General\
**Created:** [August 18, 2020, 5:19am UTC](https://community.fly.io/t/request-fly-ip-ranges/127 "2020-08-18T05:19:59Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![greg](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/greg/32/2119_2.png) [@greg](https://community.fly.io/u/greg)\
**Post date:** [August 10, 2021, 1:44pm UTC](https://community.fly.io/t/request-fly-ip-ranges/127/14 "2021-08-10T13:44:57Z")

</div>

Thinking about this, yes, IP-allow lists certainly aren’t _perfect_ (as a determined attacker could go via fly, in theory, as discussed).

But the big appeal of them is they remove that one more _thing_ to deal with, at my end (that _inevitably_ decides to stop working at 2am). Whether its an additional vm gateway through which all requests pass, a software process, proxy, etc. It’s _something_ which then needs monitoring and redundancy. As without that thing working, no database access. Big problem.

So personally I’d +1 for IP lists.

(And also given that a certain rival provides the option of assigning an external IP to an app to solve this problem. And I don’t want to give them any more money 🙂 )

---

_[View the full topic](https://community.fly.io/t/request-fly-ip-ranges/127)._