# Bandwidth utilization comparison thread

**URL:** <https://forum.storj.io/t/bandwidth-utilization-comparison-thread/7960>\
**Category:** FAQ\
**Tags:** monitoring, bandwidth, web-dashboard, multiple-nodes\
**Created:** [July 4, 2020, 7:08am UTC](https://forum.storj.io/t/bandwidth-utilization-comparison-thread/7960 "2020-07-04T07:08:19Z")\
**Posts on this page:** 1\
**Showing post:** 800

<div class="post-metadata">

**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\
**Post date:** [October 6, 2020, 7:42am UTC](https://forum.storj.io/t/bandwidth-utilization-comparison-thread/7960/800 "2020-10-06T07:42:20Z")

</div>

> [@No ingress on 1.12.3](https://forum.storj.io/t/no-ingress-on-1-12-3/9532):
>
> So I noticed that over 12 hours ago my complete ingress just stopped. Not even 1B/s occasionally, it was a flat line at 0 and the dashboard for today had 0B. (But there was the typcial repair ingress and egress was fine too, just no normal ingres) All my 3 nodes were on 1.12.3, minimum required version is 1.9.0. A restart of the nodes didn’t solve that. As soon as I updated to 1.13.3 I got ingress again. As 1.12.3 was still well above the minimum required version, this shouldn’t have happene…

Well yeah in case of these weird situations I guess you could get a bit more ingress while slow docker updates are stuck. Still, this behaviour has to be a bug that should be fixed.

---

_[View the full topic](https://forum.storj.io/t/bandwidth-utilization-comparison-thread/7960)._
