Howdy, Stranger!

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


Traceroutes (Asia) - Page 2
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.

Traceroutes (Asia)

2»

Comments

  • WilliamWilliam Member
    edited October 2017

    Congratulations to a practically singlehomed HE link. Anything above 1.5$/Mbit for it in Asia is overpriced, and considering this ends in US it better be free.

  • SplitIceSplitIce Member, Host Rep

    @William thats the intention. It's a HE test IP.... I'm seeing how many people have HE peering/transit.

  • randvegetarandvegeta Member, Host Rep

    @SplitIce said:
    @William thats the intention. It's a HE test IP.... I'm seeing how many people have HE peering/transit.

    If it's available, is be surprised if they didn't have it. It's just too cheap to say no to :). I mean it's crap, especially in Asia, but it's getting better. More and more pops, more isps and hosts connecting... But for some places, they are still shit.

  • SplitIceSplitIce Member, Host Rep

    @randvegeta shit due to congestion or shitty routes? Which places?

  • randvegetarandvegeta Member, Host Rep

    @SplitIce said:
    @randvegeta shit due to congestion or shitty routes? Which places?

    A bit of both.

  • SplitIceSplitIce Member, Host Rep

    @Multi Thanks I've got atlas covered.

    And Australia in south east Asia? I know there are alot of Asians here but...

  • SplitIce said: @randvegeta shit due to congestion or shitty routes? Which places?

    As he said: Both. Sometimes one worse, sometimes the other.

    As sole transit for Asia, both in Asia and outside Asia for Asians, HE is utterly useless. It NEEDS to be combined with something of higher quality. HE, at the least, is good for Asian exchanges but anything more should be weighted strongly if worth the hassle.

  • SplitIceSplitIce Member, Host Rep

    @William: Opinionated as always :)

    Of course this is being combined with transit both Domestic and International.

    Although if I can get HE peering at a small additional fixed cost I'd rather use it where the route quality would be similar as the transit is quite expensive...

  • randvegetarandvegeta Member, Host Rep

    SplitIce said: Although if I can get HE peering at a small additional fixed cost I'd rather use it where the route quality would be similar as the transit is quite expensive...

    Yes this is obvious :-).

    I would describe HE.net bandwidth as like a beater car! Cheap, gets the job done, and useful in a pinch. But you don't want it to be your only car. It's the car you use when your main car is in the shop, or if you need to use the other car for something else.

    It's a great ADDITION to your network, and having it has been invaluable on certain occasions. Great for backups, and helping with load balancing, and cheap enough to not care too much about.

  • SplitIceSplitIce Member, Host Rep

    @randvegeta Arent analogies fun :) I guess my main concern is in regards to detrimental latency / loss that could result from having that route available. I'm sure there are other people like me looking to cut the cost and who have HE routes as well.

    Unfortunately to compound this HE have no communities for traffic engineering, it's either ON or OFF.

  • Chennai, India.

    Tracing route to clock.sjc.he.net [216.218.254.202] over a maximum of 30 hops:
    
    1     1 ms    10 ms    53 ms  domain.name.dlink.com [192.168.0.1]
    2   142 ms    32 ms    38 ms  100.97.112.1
    3    85 ms   153 ms   157 ms  113.193.5.185
    4    99 ms    60 ms    43 ms  125.17.180.57
    5     *       63 ms    95 ms  182.79.245.22
    6    79 ms    92 ms    84 ms  6939.sgw.equinix.com [27.111.228.81]
    7   255 ms   333 ms   153 ms  100ge13-2.core1.tyo1.he.net [184.105.64.254]
    8   459 ms   272 ms   398 ms  100ge4-1.core1.lax2.he.net [184.105.65.9]
    9   331 ms   489 ms   355 ms  100ge8-2.core1.pao1.he.net [184.105.81.237]
    10   290 ms   361 ms   291 ms  10ge1-2.core1.fmt1.he.net [184.105.213.65]
    11   250 ms   246 ms   289 ms  clock.sjc.he.net [216.218.254.202]
    
    Trace complete.
    
  • Taiwan Hinet residential

    traceroute to 216.218.254.202 (216.218.254.202), 30 hops max, 60 byte packets
     1  h254.s98.ts.hinet.net (168.95.98.254)  9.081 ms  8.892 ms  8.822 ms
     2  tyfo-3302.hinet.net (168.95.23.170)  9.320 ms  9.256 ms  9.192 ms
     3  tyfo-3016.hinet.net (220.128.9.198)  11.641 ms  11.578 ms tyfo-3015.hinet.net (220.128.8.198)  13.612 ms
     4  r4031-fo.ty.hinet.net (220.128.9.185)  10.067 ms r4031-fo.ty.hinet.net (220.128.8.189)  55.343 ms  55.281 ms
     5  r11-pa.us.hinet.net (211.72.108.45)  153.652 ms  153.588 ms r11-pa.us.hinet.net (211.72.108.233)  170.450 ms
     6  30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20)  170.858 ms  170.878 ms  170.767 ms
     7  10ge1-2.core1.fmt1.he.net (184.105.213.65)  185.539 ms  202.200 ms  187.112 ms
     8  clock.sjc.he.net (216.218.254.202)  159.066 ms  159.006 ms  158.924 ms
    
  • GTHostGTHost Member, Patron Provider

    There is any direct fiber from Taiwan to China? And does it work?

  • SplitIceSplitIce Member, Host Rep
    edited November 2017

    Yes there is multiple, CT by default, not CN2 though.

    CT at <60ms

  • shellshell Member
    edited November 2017

    isp biznetnetworks - jakarta indonesia - package biznet metronet (business)

      # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV  
     1 182.253.xx.x                       0%   10   2.6ms    10.4     2.5    60.4    17.3  
     2 182.253.187.145                    0%   10   2.9ms     3.2     1.4     7.2     1.4  
     3 182.253.187.102                    0%   10   3.6ms     4.5     3.1     6.6     1.2  
     4 182.253.187.174                    0%   10  14.8ms    15.7    14.5    17.9     1.2  
     5 as6939.singapore.megaport.com      0%   10  14.8ms    18.2    14.6    25.2     3.4  
     6 100ge13-2.core1.tyo1.he.net        0%   10  95.9ms    94.5    90.6    96.2     2.2  
     7 100ge8-1.core1.sea1.he.net         0%   10 190.9ms   190.5   189.1   191.2     0.7  
     8 100ge11-1.core1.sjc2.he.net        0%   10 191.1ms   190.9   189.6   191.4     0.5  
     9 10ge1-1.core1.fmt1.he.net          0%   10   205ms   197.9   195.6     205     2.8  
    10 clock.sjc.he.net                   0%   10 196.5ms   196.3   195.4   196.8     0.4 
Sign In or Register to comment.