In terms of speed, what are your values?

Node Operators
1

Hello, everyone,

Following the changes that will likely increase traffic to the fast node.

I wanted to know if it was possible to determine whether one node would win the race against another with a simple ping like this?

Does it make sense?

ping 185.244.226.3

my result:

64 bytes from 185.244.226.3: icmp_seq=2 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=3 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=4 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=5 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=6 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=7 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=8 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=9 ttl=53 time=10.8 ms
64 bytes from 185.244.226.3: icmp_seq=10 ttl=53 time=10.7 ms
64 bytes from 185.244.226.3: icmp_seq=11 ttl=53 time=10.7 ms

I have also made a Pingdom from Pingdom


- from: St.Petersburg, Russia
- TCP: dialed node in 105ms
- TCP: pinged node in 51ms
- TCP: total: 157ms
- QUIC: dialed node in 104ms
- QUIC: pinged node in 52ms
- QUIC: total: 156ms
- 
- from: OVH, France
- QUIC: dialed node in 72ms
- QUIC: pinged node in 23ms
- QUIC: total: 95ms
- TCP: dialed node in 81ms
- TCP: pinged node in 22ms
- TCP: total: 103ms

What do you think? Is it significant? If so, I would be curious to know what your ping is so we can compare.

And maybe we can find some useful things together.

2

185.244.226.3 Sorry but that this IP number mean to represent?

1 Like
3 
$ whois 185.244.226.3
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '185.244.226.0 - 185.244.226.7'

% Abuse contact for '185.244.226.0 - 185.244.226.7' is 'ops@storj.io'

inetnum:        185.244.226.0 - 185.244.226.7
netname:        STORJ-DE-FRA1
country:        DE
admin-c:        OA3075-RIPE
tech-c:         OA3075-RIPE
status:         ASSIGNED PA
mnt-by:         lir-us-storj-1-MNT
created:        2021-04-14T12:00:28Z
last-modified:  2021-04-14T12:22:53Z
source:         RIPE

role:           Operations
address:        3423 Piedmont Rd NE
address:        30305
address:        Atlanta
address:        UNITED STATES
phone:          +17348347084
nic-hdl:        OA3075-RIPE
mnt-by:         lir-us-storj-1-MNT
created:        2021-02-24T08:21:42Z
last-modified:  2021-02-24T08:21:43Z
source:         RIPE # Filtered

% Information related to '185.244.226.0/24AS211541'

route:          185.244.226.0/24
origin:         AS211541
mnt-by:         lir-us-storj-1-MNT
created:        2022-04-18T22:11:49Z
last-modified:  2022-04-18T22:11:49Z
source:         RIPE

% Information related to '185.244.226.0/24AS212238'

route:          185.244.226.0/24
origin:         AS212238
created:        2024-11-05T10:54:10Z
last-modified:  2024-11-05T10:54:10Z
source:         RIPE
mnt-by:         lir-us-storj-1-MNT

% This query was served by the RIPE Database Query Service version 1.118.1 (DEXTER)
4

Also see Explaining the Linksharing Service - Storj Docs

5

This is not a good measure because customers send their data directly to nodes, not to the satellites and then to you. Even then, distance is not a good metric; you need to incorporate peering and routing. i.e. some traffic may take non-intuitive routes to some peers.

3 Likes
6

Ping almost doesn’t matter, @Ambifacient is correct. You need mtr instead. But you would only check the route to the link sharing services, not the actual speed.