# Slow transmission speed of new node

**URL:** <https://forum.storj.io/t/slow-transmission-speed-of-new-node/25695>\
**Category:** FAQ\
**Created:** [April 1, 2024, 5:10pm UTC](https://forum.storj.io/t/slow-transmission-speed-of-new-node/25695 "2024-04-01T17:10:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dr.Ko](https://storj.bcdn.literatehosting.com/letter_avatar/dr.ko/32/5_5575768a8748004e209b776fc1b2916d.png) [@Dr.Ko](https://forum.storj.io/u/Dr.Ko)\
**Post date:** [April 1, 2024, 5:10pm UTC](https://forum.storj.io/t/slow-transmission-speed-of-new-node/25695/1 "2024-04-01T17:10:54Z")

</div>

There is a large difference in transmission speed between nodes that have been started for about a week in other locations and existing nodes. It might be slow because the audit hasn’t finished yet.

I don’t think it was this slow in the beginning when I was running the two existing nodes, but could it be set up incorrectly?

 ![Screenshot_2](https://storj-s3.bcdn.literatehosting.net/original/2X/2/22b5fabaa803c4fbeaeebc47e62039df2f1e01c4.png)

---

<div class="post-metadata">

**Author:** ![Ambifacient](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/ambifacient/32/7815_2.png) [@Ambifacient](https://forum.storj.io/u/Ambifacient)\
**Post date:** [April 1, 2024, 5:16pm UTC](https://forum.storj.io/t/slow-transmission-speed-of-new-node/25695/2 "2024-04-01T17:16:28Z")

</div>

It was recently changed so that only 1% of ingress goes to new nodes.

> [@Release preparation v1.97](https://forum.storj.io/t/release-preparation-v1-97/25150):
>
> New release candidate is deployed on [QA Satellite](https://satellite.qa.storj.io/)Changelog General [e83f41e](https://github.com/storj/storj/commit/e83f41e) cmd/tools: add is-valid-sj1-blob utility [f506f64](https://github.com/storj/storj/commit/f506f64) cmd/tools/is-valid-sj1-blob: minor fixes [8211f85](https://github.com/storj/storj/commit/8211f85) \*/ui: avoid noembed [a62929f](https://github.com/storj/storj/commit/a62929f) certificate/authorization: reimplement gob-to-protobuf migration [396ffd4](https://github.com/storj/storj/commit/396ffd4) build: use [storj.io/common](http://storj.io/common) instead of [storj.io/private](http://storj.io/private)[713b18d](https://github.com/storj/storj/commit/713b18d) jenkinsfile: integration and back comp tests in parallel Satellite [68bb976](https://github.com/storj/storj/commit/68bb976) satellite/payments/stripe: reduce dependencies [4dbd4ef](https://github.com/storj/storj/commit/4dbd4ef) satellite/satellited…

---

<div class="post-metadata">

**Author:** ![Dr.Ko](https://storj.bcdn.literatehosting.com/letter_avatar/dr.ko/32/5_5575768a8748004e209b776fc1b2916d.png) [@Dr.Ko](https://forum.storj.io/u/Dr.Ko)\
**Post date:** [April 1, 2024, 5:22pm UTC](https://forum.storj.io/t/slow-transmission-speed-of-new-node/25695/3 "2024-04-01T17:22:48Z")

</div>

Wow, then the speed will be that low until the node is verified…!  
Recently, there may be a reason why the existing node has a lot of reception volume because there are many customers, but the reception volume that was flowing to the unverified node is merged into the existing node, so the speed seems to be better.

I think it means, “We’ll see if you can stand the test.” 🙂