Like Tree2Likes
  • 1 Post By PDLM
  • 1 Post By shri

HKBN latency

Reply
  1. #1

    Join Date
    Oct 2008
    Posts
    28

    HKBN latency

    Hi,

    Pls can someone with HKBN (preferably FTTH,1000M), do me a favour and do a ping and traceroute to www.google.com.hk
    I know their overseas bandwidth may not be the best, but I'm mainly interested in HK connectivity only.

    Thanks!

    Last edited by jimlit; 13-11-2010 at 07:16 PM.

  2. #2

    Join Date
    Jun 2005
    Location
    Hong Kong
    Posts
    23,207

    They have a committed performance pledge (money back if not achieved, I believe) of 3ms on that specific site and for the last two quarters have been achieving 2ms. Details here: HKBN

    Last edited by PDLM; 13-11-2010 at 07:31 PM.
    jimlit likes this.

  3. #3

    Join Date
    Oct 2010
    Posts
    34

    Edit - post irrelevant. Just saw you want to know bout HK only.

    Last edited by thejae; 13-11-2010 at 08:11 PM.

  4. #4

    Join Date
    Aug 2005
    Location
    Singapore
    Posts
    2,578
    Quote Originally Posted by PDLM:
    They have a committed performance pledge (money back if not achieved, I believe) of 3ms on that specific site and for the last two quarters have been achieving 2ms. Details here: HKBN

    Yeah sure..but it is impossible to get out of a contract or get any refund with these guys. I would avoid dealing with HKBN as you will regret it later.

  5. #5

    Join Date
    Dec 2002
    Location
    θ–„ζ‰Άζž—
    Posts
    45,390
    Code:
    PING www.l.google.com (64.233.189.104) 56(84) bytes of data.
    64 bytes from hkg01s01-in-f104.1e100.net (64.233.189.104): icmp_seq=1 ttl=55 time=3.73 ms
    64 bytes from hkg01s01-in-f104.1e100.net (64.233.189.104): icmp_seq=2 ttl=55 time=3.56 ms
    64 bytes from hkg01s01-in-f104.1e100.net (64.233.189.104): icmp_seq=3 ttl=55 time=3.68 ms
    64 bytes from hkg01s01-in-f104.1e100.net (64.233.189.104): icmp_seq=4 ttl=55 time=3.59 ms
    Code:
    traceroute to www.google.com.hk (64.233.189.104), 30 hops max, 40 byte packets
    <snip>
     3  059148235017.ctinets.com (59.148.235.17)  0.677 ms  0.672 ms  0.891 ms
     4  061238168061.static.ctinets.com (61.238.168.61)  1.370 ms  1.594 ms  1.577 ms
     5  061238224153.static.ctinets.com (61.238.224.153)  1.560 ms  1.549 ms  1.529 ms
     6  061244232070.static.ctinets.com (61.244.232.70)  1.490 ms * 061244232070.static.ctinets.com (61.244.232.70)  1.403 ms
     7  061244232237.static.ctinets.com (61.244.232.237)  1.472 ms  1.695 ms  1.923 ms
     8  061244232026.static.ctinets.com (61.244.232.26)  1.399 ms  1.631 ms  1.615 ms
     9  72.14.196.85 (72.14.196.85)  3.088 ms  3.079 ms  3.070 ms
    10  209.85.241.56 (209.85.241.56)  3.046 ms  3.037 ms  2.996 ms
    11  66.249.94.6 (66.249.94.6)  3.705 ms  3.693 ms  3.677 ms
    12  hkg01s01-in-f104.1e100.net (64.233.189.104)  3.690 ms  3.673 ms  3.688 ms
    This is on a different type of fiber connection to what goes into homes, so it may not be applicable.

    We use a 100Mbps fiber connection from them to host a few sites.
    Last edited by shri; 13-11-2010 at 09:39 PM.
    jimlit likes this.

  6. #6

    Join Date
    Oct 2008
    Posts
    28

    Thanks for the response guys. Pretty impressive ping times.