Howdy, Stranger!

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


Any VPS providers in SG with direct peering to FLAGTEL (Reliance)?
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.

Any VPS providers in SG with direct peering to FLAGTEL (Reliance)?

I've been searching quite a bit but I haven't found any. I know that there is a location somewhere because apparently Valve has direct peering to them from their SG location. I have tried just about everyone I could think of.

Comments

  • ExpertVMExpertVM Member, Host Rep

    What is the ASN for Reliance?

  • yashauyashau Member
    edited January 2017

    @ExpertVM said:
    What is the ASN for Reliance?

    AS15412

    Edit: nvm I was using a wrong IP.

    But even if I'm getting 1ms to lg.expertvm.com via the GCX looking glass, I'm getting over 130ms to your LG but 60ms to the GCX SG looking glass IP. So over 60ms is being added after it reaches SG and reaching your site.

  • JarylWJarylW Member
    edited January 2017

    From i-83.net (SG). I suppose if you need ipv4 you could look at their parent company @quadhost

    Edit: noticed you edited and mentioned IP was wrong. You could try their lg. http://lg-tai-sg.quadhost.net/

    Thanked by 1quadhost
  • yashauyashau Member
    edited January 2017

    @JarylW said:
    From i-83.net (SG). I suppose if you need ipv4 you could look at their parent company @quadhost

    # traceroute 62.216.137.131
    traceroute to 62.216.137.131 (62.216.137.131), 30 hops max, 60 byte packets
     1  111.221.46.72 (111.221.46.72)  0.369 ms  0.359 ms  0.337 ms
     2  202.83.103.189 (202.83.103.189)  1.441 ms  1.395 ms  1.115 ms
     3  Singapore1.vqbn.com (132.147.112.67)  1.510 ms  1.312 ms  1.337 ms
     4  15412.sgw.equinix.com (27.111.228.12)  1.538 ms  1.535 ms  1.516 ms
     5  lo0.ejr03.sin001.flagtel.com (62.216.137.131)  2.132 ms  1.653 ms  1.922 ms
    

    Issue for me is that

    PING 62.216.137.131 (62.216.137.131) from xxx.xx.xxx.xxx: 56 data bytes
    64 bytes from 62.216.137.131: icmp_seq=0 ttl=58 time=60.286 ms
    64 bytes from 62.216.137.131: icmp_seq=1 ttl=58 time=58.017 ms
    64 bytes from 62.216.137.131: icmp_seq=2 ttl=58 time=58.253 ms

    Which is fine.. but

    PING 111.221.46.72 (111.221.46.72) from xxx.xx.xxx.xxx: 56 data bytes
    64 bytes from 111.221.46.72: icmp_seq=0 ttl=52 time=95.908 ms
    64 bytes from 111.221.46.72: icmp_seq=1 ttl=52 time=94.138 ms
    64 bytes from 111.221.46.72: icmp_seq=2 ttl=52 time=95.023 ms

    This makes absolutely 0 sense to me. Why does 35ms get added?

    And it gets weirder:

    7 62.216.135.226 27.471 ms
    62.216.128.73 60.827 ms 57.924 ms
    8 62.216.129.161 57.933 ms
    62.216.128.246 58.089 ms
    62.216.129.161 57.834 ms
    9 27.111.228.6 108.265 ms 94.194 ms 94.942 ms
    10 132.147.112.76 91.722 ms 124.410 ms 92.455 ms

    Traceroute shows nothing. Just a huge latency jump inside Equinix.

  • yashau said: Valve has direct peering to them from their SG location

    Valve runs their own backbone and is also present on SGIX, and by traffic levels they negotiated a private peering most likely.

    Thanked by 1vimalware
  • ExpertVMExpertVM Member, Host Rep

    @yashau PM me the traceroute detail and I will look at it.

  • yashauyashau Member
    edited January 2017

    @ExpertVM said:
    @yashau PM me the traceroute detail and I will look at it.

    Done. Thanks!

Sign In or Register to comment.