Can I get a confirmation of the location of the node #4? The ASN AS60117 is showing as either Romania or Netherlands depending on the site I use to check it (for example https://www.whatismyip.com/asn/60117/). Or if anyone knows an easier way to determine it besides latency math?
@SocksAreComfortable said:
Can I get a confirmation of the location of the node #4? The ASN AS60117 is showing as either Romania or Netherlands depending on the site I use to check it (for example https://www.whatismyip.com/asn/60117/). Or if anyone knows an easier way to determine it besides latency math?
@SocksAreComfortable said:
Can I get a confirmation of the location of the node #4? The ASN AS60117 is showing as either Romania or Netherlands depending on the site I use to check it (for example https://www.whatismyip.com/asn/60117/). Or if anyone knows an easier way to determine it besides latency math?
If you just want to check whether it's in RO or NL, you can simply enter your IP into https://bgp.tools, and look what the upstreams are, in my case on node 2 the only upstream is "TNGNET B.V.", which, according to PeeringDB is only present in two NL datacenters.
Theoretically they could be tunneling it to NL, but that can be disproved with latency tests, and IMHO latency tests are the most reliable ones, even though others (such as the aforementioned) may give some clues/indications.
@SocksAreComfortable said:
Can I get a confirmation of the location of the node #4? The ASN AS60117 is showing as either Romania or Netherlands depending on the site I use to check it (for example https://www.whatismyip.com/asn/60117/). Or if anyone knows an easier way to determine it besides latency math?
its 2ms to Virmach AMS and 33ms to hosteroid BUC
Fair enough. Was hoping there was a trick besides latency math lol.
@lukast__ said:
Theoretically they could be tunneling it to NL, but that can be disproved with latency tests, and IMHO latency tests are the most reliable ones, even though others (such as the aforementioned) may give some clues/indications.
Nice, hadn't seen that site before. Seems that node 4 is the same as node 2 based on my IP.
LOL so doing some latency tests now out of curiosity (and because I apparently have 3 different VPS in Amsterdam now because reasons)...starting to think two of mine are in the same datacenter:
Comments
Involucrated disks ?
blog | exploring visually |
Involucrated disks which can not be replaced due to Chia cryptocurrency?
Stop the planet! I want to get off!
Can I get a confirmation of the location of the node #4? The ASN AS60117 is showing as either Romania or Netherlands depending on the site I use to check it (for example https://www.whatismyip.com/asn/60117/). Or if anyone knows an easier way to determine it besides latency math?
its 2ms to Virmach AMS and 33ms to hosteroid BUC
I bench YABS 24/7/365 unless it's a leap year.
If you just want to check whether it's in RO or NL, you can simply enter your IP into https://bgp.tools, and look what the upstreams are, in my case on node 2 the only upstream is "TNGNET B.V.", which, according to PeeringDB is only present in two NL datacenters.
Theoretically they could be tunneling it to NL, but that can be disproved with latency tests, and IMHO latency tests are the most reliable ones, even though others (such as the aforementioned) may give some clues/indications.
cpu_logger | Recommended providers: Layer7, dataforest (Avoro/PHP-Friends), @host_c
Fair enough. Was hoping there was a trick besides latency math lol.
Nice, hadn't seen that site before. Seems that node 4 is the same as node 2 based on my IP.
LOL so doing some latency tests now out of curiosity (and because I apparently have 3 different VPS in Amsterdam now because reasons)...starting to think two of mine are in the same datacenter:
rtt min/avg/max/mdev = 0.020/0.036/0.131/0.010 ms