# Updates on Test Data

**URL:** <https://forum.storj.io/t/updates-on-test-data/26034>\
**Category:** Announcements\
**Created:** [April 30, 2024, 3:36pm UTC](https://forum.storj.io/t/updates-on-test-data/26034 "2024-04-30T15:36:45Z")\
**Posts on this page:** 1\
**Showing post:** 503

<div class="post-metadata">

**Author:** ![jtolio](https://storj.bcdn.literatehosting.com/letter_avatar/jtolio/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtolio](https://forum.storj.io/u/jtolio)\
**Post date:** [May 30, 2024, 4:24pm UTC](https://forum.storj.io/t/updates-on-test-data/26034/503 "2024-05-30T16:24:32Z")

</div>

> [@Toyoo](#):
>
> Indeed. If I understand correctly, now satellite penalizes you for each lost race with less traffic, regardless of origin of that traffic. So if you operate a node in, let say, South America, if you fail too many connections from Europe, you will get not just less uploads from Europe, but also from South America as well.

Just wanted to reply to this - this is only kind of true.

It is true that the Satellite is now going to keep track of recent success rates in a system-wide data structure (a speed profile, I guess), but we actually have many of these speed profiles to choose from. We are going to be choosing which speed profile to use based on where the request is coming from.

Right now, this functionality isn’t enabled, so yes, your description is true /this week/.

Our next step is to have every region’s S3 gateway (where most of our traffic comes from anyway) get their own speed profile (once I can figure out why [https://review.dev.storj.io/c/storj/edge/+/13309](https://review.dev.storj.io/c/storj/edge/+/13309) isn’t passing the build). And then after every gateway region is handled, then we’ll explore what we can do for remaining native integrations.

---

_[View the full topic](https://forum.storj.io/t/updates-on-test-data/26034)._