# custom network visibility

**URL:** <https://community.fly.io/t/custom-network-visibility/21120>\
**Category:** General\
**Tags:** machines, flyctl, login-only\
**Created:** [August 3, 2024, 6:26am UTC](https://community.fly.io/t/custom-network-visibility/21120 "2024-08-03T06:26:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Pravin1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/pravin1/32/37205_2.png) [@Pravin1](https://community.fly.io/u/Pravin1)\
**Post date:** [August 3, 2024, 6:28am UTC](https://community.fly.io/t/custom-network-visibility/21120/2 "2024-08-03T06:28:21Z")

</div>

Hm interesting, I found this on a related topic, is this still the case, can anyone from FlyIO confirm?

> [@Inspecting a fly app's --network setting](https://community.fly.io/t/inspecting-a-fly-apps-network-setting/14163/2):
>
> There are no ways that i’m aware off. You will have to do that book keeping on your end.  
> fwiw, it should be relatively easy to expose on our end so if I have some time today, I can look that.

---

_[View the full topic](https://community.fly.io/t/custom-network-visibility/21120)._