# Traffic sharing for same ip

**URL:** <https://forum.storj.io/t/traffic-sharing-for-same-ip/28774>\
**Category:** FAQ\
**Tags:** bandwidth, multiple-nodes\
**Created:** [December 11, 2024, 7:11am UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774 "2024-12-11T07:11:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alpharabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alpharabbit/32/1129_2.png) [@alpharabbit](https://forum.storj.io/u/alpharabbit)\
**Post date:** [December 11, 2024, 7:11am UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/1 "2024-12-11T07:11:19Z")

</div>

I have 4 nodes sharing one ip. All nodes running on the same server using docker and have identical HDDs. I would expect them having more or less equal ingress. But for some reason one node having constantly like 3x the ingress of the other nodes. I don’t know how the node selection works but in alphabetical order of node id this node is the first one. Could this be the reason?

---

<div class="post-metadata">

**Author:** ![edo](https://storj.bcdn.literatehosting.com/letter_avatar/edo/32/6_22734026db12803ebb3e059622ac3534.png) [@edo](https://forum.storj.io/u/edo)\
**Post date:** [December 11, 2024, 9:14am UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/2 "2024-12-11T09:14:32Z")

</div>

Hey @alpharabbit ,

What you’re seeing is a common observation when running multiple nodes behind one IP. It’s unlikely that the alphabetical order of the node ID plays a role—traffic differences usually happen due to:

1. **Node Age/Vetting:** Older or fully vetted nodes get more traffic. If one node is further along in the vetting process, it will naturally receive more ingress.
2. **Random Selection:** Storj uses a random but weighted selection process, which can lead to traffic variation even among identical nodes.
3. **Shared IP Behavior:** All nodes behind the same IP are treated as part of one “bucket,” so traffic isn’t perfectly split.

This variation is normal and tends to balance out over time. You might find this related post helpful: [4 nodes on one server, but one node is getting 50% of the data the other nodes are getting](https://forum.storj.io/t/4-nodes-on-one-server-but-one-node-is-getting-50-of-the-data-the-other-nodes-are-getting/28230).

Make sure all nodes are healthy (check logs for missed uploads) and keep monitoring their performance. Over weeks or months, things should even out more.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [December 12, 2024, 1:56am UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/9 "2024-12-12T01:56:32Z")

</div>

I would add to the list from @edo:  
4. The node reputation (the online, audit and suspension scores)  
5. Success rate calculated for the customer location and your nodes

---

<div class="post-metadata">

**Author:** ![alpharabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alpharabbit/32/1129_2.png) [@alpharabbit](https://forum.storj.io/u/alpharabbit)\
**Post date:** [July 23, 2025, 1:12pm UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/10 "2025-07-23T13:12:16Z")

</div>

And the solution is… Only one node is vetted at US1. 🙄

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [July 23, 2025, 2:07pm UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/11 "2025-07-23T14:07:54Z")

</div>

are they very young?

---

<div class="post-metadata">

**Author:** ![alpharabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alpharabbit/32/1129_2.png) [@alpharabbit](https://forum.storj.io/u/alpharabbit)\
**Post date:** [July 23, 2025, 3:56pm UTC](https://forum.storj.io/t/traffic-sharing-for-same-ip/28774/12 "2025-07-23T15:56:59Z")

</div>

The nodes are one year old and all should have been vetted long ago. [Bug in new Vetted Date](https://forum.storj.io/t/bug-in-new-vetted-date/30344)
