Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Provider single homed to retn
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Provider single homed to retn

failhostingsfailhostings Member
edited July 2019 in General

Any providers in Eastern Europe who is single homed to retn? I'm looking for a vps for vpn with low latency to Japan the reason is this https://retn.net/2019/05/08/retn-added-tokyo-khabarovsk-route-to-its-network/.

Comments

  • TheRealDealTheRealDeal Member

    Not a clue. Have you tried Google?

    Thanked by 1RedSox
  • failhostingsfailhostings Member
    edited July 2019

    @TheRealDeal said:
    Not a clue. Have you tried Google?

    Not sure if you came to bully me on my own thread also but you know that you can't just Google providers who are singled homed to retn or such , right?

    Thanked by 1rm_
  • LearntoliveLearntolive Member

    @failhostings said:
    Any providers in Eastern Europe who is single homed to retn? I'm looking for a vps for vpn with low latency to Japan the reason is this https://retn.net/2019/05/08/retn-added-tokyo-khabarovsk-route-to-its-network/.

    https://www.vnet.sk/en/ ?

    Thanked by 1failhostings
  • NobodyInterestingNobodyInteresting Member

    You Google the providers name to find a test IP and look up the ASN for that IP and see who the upstreams are on bgp.he.net,
    OR you google the providers name and add "ASN" right after it, so you can find their ASN. After that - you google that AS number to find their upstreams on bgp.he.net.
    Google is your friend and usually has all the answers, you just have to know how to ask the question.

    Thanked by 4TheRealDeal failhostings emgh level6
  • failhostingsfailhostings Member
    edited July 2019

    @t0ny0 said:
    You Google the providers name to find a test IP and look up the ASN for that IP and see who the upstreams are on bgp.he.net,
    OR you google the providers name and add "ASN" right after it, so you can find their ASN. After that - you google that AS number to find their upstreams on bgp.he.net.
    Google is your friend and usually has all the answers, you just have to know how to ask the question.

    Yes I know about this but some providers use cloudflare and such or host their website on another network . > @Learntolive said:

    @failhostings said:
    Any providers in Eastern Europe who is single homed to retn? I'm looking for a vps for vpn with low latency to Japan the reason is this https://retn.net/2019/05/08/retn-added-tokyo-khabarovsk-route-to-its-network/.

    https://www.vnet.sk/en/ ?

    They seem to use retn but not single homed.

  • TheRealDealTheRealDeal Member

    Get a IP from a looking glass. Then do the tests don't work from the providers site. Some host there sites off-site so if there is a outage they can get the message across.

    Thanked by 3failhostings NobodyInteresting emgh
  • failhostingsfailhostings Member

    @TheRealDeal said:
    Get a IP from a looking glass. Then do the tests don't work from the providers site. Some host there sites off-site so if there is a outage they can get the message across.

    I do search myself too and you frist must find the provider to find a looking glass most of the time. I'm not being lazy I'm just asking for help to shorten my search. About bgp he net website some providers even use another name on their asn so its not that easy.

  • rm_rm_ IPv6 Advocate, Veteran
    edited July 2019

    failhostings said: you know that you can't just Google providers who are singled homed to retn

    I would agree that just by randomly googling you are unlikely to find such a thing. Mostly because it's nonexistent or rare to begin with, there's nobody who makes a point of single-homing on a provider*, usually hosts will add 2-3 upstreams at the first opportunity.

    *Unless it's Cogent -- but Cogent has their own massive hosting/colo DCs and rents out space including their own IP ranges (so naturally single-homed), which RETN either doesn't, or not on such scale and not as widely known to do.

    failhostings said: low latency to Japan the reason is this https://retn.net/2019/05/08/retn-added-tokyo-khabarovsk-route-to-its-network/.

    And I'm not sure if being single-homed on RETN in Europe guarantees you much. OK, my ISP uses RETN, and in this case the RETN route got picked (to Linode Japan). But after that:

     Host                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2a02:2698:8000::505                                 0.0%     6    0.7   0.8   0.6   0.9   0.0
 2. 2a02:2698:8000::1e02                                0.0%     6    0.8   0.7   0.6   0.8   0.0
 3. GW-ERTelecom.retn.net                               0.0%     5   27.9  27.3  26.7  27.9   0.0
 4. ae10-153.RT.M9P.MSK.RU.retn.net                     0.0%     5   26.9  28.3  26.9  30.3   1.7
 5. RT.IRX.FKT.DE.retn.net                              0.0%     5   60.0  60.2  60.0  60.3   0.0
 6. ix-ae-6-0.tcore2.fr0-frankfurt.ipv6.as6453.net      0.0%     5   60.2  67.2  60.1  91.5  13.7
 7. if-ae-9-2.tcore1.fnm-frankfurt.ipv6.as6453.net      0.0%     5   60.5  60.4  60.3  60.5   0.0
 8. if-ae-5-2.tcore1.av2-amsterdam.ipv6.as6453.net      0.0%     5   66.1  66.1  65.9  66.2   0.0
 9. if-ae-15-2.tcore1.pye-paris.ipv6.as6453.net         0.0%     5   72.7  73.4  72.7  76.0   1.2
10. if-ae-3-2.tcore1.l78-london.ipv6.as6453.net         0.0%     5   77.3  77.7  77.3  78.5   0.0
11. if-ae-15-2.tcore3.njy-newark.ipv6.as6453.net        0.0%     5  155.2 155.3 155.2 155.4   0.0
12. if-ae-1-3.tcore4.njy-newark.ipv6.as6453.net         0.0%     5  148.9 149.0 148.8 149.2   0.0
13. if-ae-12-2.tcore2.aeq-ashburn.ipv6.as6453.net       0.0%     5  162.0 163.4 162.0 168.2   2.6
14. if-ae-36-2.tcore2.lvw-los-angeles.ipv6.as6453.net   0.0%     5  217.5 217.5 217.1 217.9   0.0
15. if-et-53-2.hcore2.kv8-chiba.ipv6.as6453.net         0.0%     5  328.0 329.0 328.0 332.0   1.6
16. if-ae-24-2.tcore2.tv2-tokyo.ipv6.as6453.net         0.0%     5  329.2 329.5 329.2 329.7   0.0
17. if-ae-2-2.tcore1.tv2-tokyo.ipv6.as6453.net          0.0%     5  329.3 329.7 329.2 330.8   0.6
18. 2001:5a0:2200:300::62                               0.0%     5  301.8 302.1 301.8 302.2   0.0
19. 2400:8902:d::2                                      0.0%     5  302.3 305.0 302.3 312.3   4.8
20. 2400:8902::4b                                       0.0%     5  301.9 302.0 301.9 302.1   0.0

    The Japan location also needs to be single-homed on RETN for this to work. Actually for a while I had super low latency to this (going via RETN right to BBIX i think):

    But some time ago they ruined it, I don't know who, Linode or RETN themselves, now it's as on the trace above.

    Thanked by 1failhostings
  • failhostingsfailhostings Member
    edited July 2019

    @rm_ said:

    failhostings said: you know that you can't just Google providers who are singled homed to retn

    I would agree that just by randomly googling you are unlikely to find such a thing. Mostly because it's nonexistent or rare to begin with, there's nobody who makes a point of single-homing on a provider*, usually hosts will add 2-3 upstreams at the first opportunity.

    *Unless it's Cogent -- but Cogent has their own massive hosting/colo DCs and rents out space including their own IP ranges (so naturally single-homed), which RETN either doesn't, or not on such scale and not as widely known to do.

    failhostings said: low latency to Japan the reason is this https://retn.net/2019/05/08/retn-added-tokyo-khabarovsk-route-to-its-network/.

    And I'm not sure if being single-homed on RETN in Europe guarantees you much. OK, my ISP uses RETN, and in this case the RETN route got picked (to Linode Japan). But after that:

     Host                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
>  1. 2a02:2698:8000::505                                 0.0%     6    0.7   0.8   0.6   0.9   0.0
>  2. 2a02:2698:8000::1e02                                0.0%     6    0.8   0.7   0.6   0.8   0.0
>  3. GW-ERTelecom.retn.net                               0.0%     5   27.9  27.3  26.7  27.9   0.0
>  4. ae10-153.RT.M9P.MSK.RU.retn.net                     0.0%     5   26.9  28.3  26.9  30.3   1.7
>  5. RT.IRX.FKT.DE.retn.net                              0.0%     5   60.0  60.2  60.0  60.3   0.0
>  6. ix-ae-6-0.tcore2.fr0-frankfurt.ipv6.as6453.net      0.0%     5   60.2  67.2  60.1  91.5  13.7
>  7. if-ae-9-2.tcore1.fnm-frankfurt.ipv6.as6453.net      0.0%     5   60.5  60.4  60.3  60.5   0.0
>  8. if-ae-5-2.tcore1.av2-amsterdam.ipv6.as6453.net      0.0%     5   66.1  66.1  65.9  66.2   0.0
>  9. if-ae-15-2.tcore1.pye-paris.ipv6.as6453.net         0.0%     5   72.7  73.4  72.7  76.0   1.2
> 10. if-ae-3-2.tcore1.l78-london.ipv6.as6453.net         0.0%     5   77.3  77.7  77.3  78.5   0.0
> 11. if-ae-15-2.tcore3.njy-newark.ipv6.as6453.net        0.0%     5  155.2 155.3 155.2 155.4   0.0
> 12. if-ae-1-3.tcore4.njy-newark.ipv6.as6453.net         0.0%     5  148.9 149.0 148.8 149.2   0.0
> 13. if-ae-12-2.tcore2.aeq-ashburn.ipv6.as6453.net       0.0%     5  162.0 163.4 162.0 168.2   2.6
> 14. if-ae-36-2.tcore2.lvw-los-angeles.ipv6.as6453.net   0.0%     5  217.5 217.5 217.1 217.9   0.0
> 15. if-et-53-2.hcore2.kv8-chiba.ipv6.as6453.net         0.0%     5  328.0 329.0 328.0 332.0   1.6
> 16. if-ae-24-2.tcore2.tv2-tokyo.ipv6.as6453.net         0.0%     5  329.2 329.5 329.2 329.7   0.0
> 17. if-ae-2-2.tcore1.tv2-tokyo.ipv6.as6453.net          0.0%     5  329.3 329.7 329.2 330.8   0.6
> 18. 2001:5a0:2200:300::62                               0.0%     5  301.8 302.1 301.8 302.2   0.0
> 19. 2400:8902:d::2                                      0.0%     5  302.3 305.0 302.3 312.3   4.8
> 20. 2400:8902::4b                                       0.0%     5  301.9 302.0 301.9 302.1   0.0
>

    The Japan location also needs to be single-homed on RETN for this to work. Actually for a while I had super low latency to this (going via RETN right to BBIX i think):

    But some time ago they ruined it, I don't know who, Linode or RETN themselves, now it's as on the trace above.

    You have been very informative thank you, yes I understand that I won't be reaching any part of Japan internet via retn low latency but it still counts for the networks that does that routing or are also single homed to retn .

Sign In or Register to comment.