5 ms·

FWIW and YMMV To Japan from HK 9 hops. Latency ~75ms. Bandwidth ~ 2.2MB/sec. To Fremont from HK 14 hope, Latency ~155ms. Bandwidth ~ 1.1MB/sec

by latch 15y ago

codexon 15y ago
Just curious, is Japan a good place for serving Russia and Australia?
- oohmeplums 15y ago
  From my iiNet DSL2+ connection in Perth, Australia to tokyo1.linode.com, I get 204ms ping and 14 hops, and from a Telstra fibre connection, I get 174ms and 15 hops. That compares to about 250ms and 12 hops on iiNet, and 210ms and 14 hops on Telstra to fremont1.linode.com. A little bit quicker, I think.
  - jacques_chester 15y ago
    Yes, it's faster than Fremont. I moved to Dallas a few weeks ago after the third Fremont outage; now I wish I'd known this was coming down the pipeline. ... maybe I'll move again. It'd shave 50-60ms.
- ajtaylor 15y ago
  Our linode is currently in London (I didn't set it up...), but I'm probably going to request a move to the Tokyo datacenter in the next week. Ping times to Tokyo (136 ms) are literally half what they are to London (297 ms) and still better than Fremont (208 ms). Seems like a no-brainer to try moving it.
  - getsat 15y ago
    Where are you located? Your ping times don't mean much without a reference point.
    - shimon_e 15y ago
      Based on those times I'd say he is in Russia or very close to an Australia-Japan peering exchange.
    - ajtaylor 15y ago
      I'm in Sydney, Australia.
- nl 15y ago
  It's not great for Australia. Most ISPs will route to Japan sensibly, but a few try and save money and route via the US (note that this is the same as hosting with Amazon in Singapore).
itsnotvalid 15y ago
Thanks. isn't that seems to be a choice now for HK devs wanting a quality service for hosting?
- latch 15y ago
  I'd say the other option is EC2/AWS/Amazon with their presence in both Tokyo and Singapore. But the choice between Linode or AWS tends to come down to other things (Linode is cheaper and I'd say simple/more predictable...AWS is more complex and offers way more "cloud" services).

FWIW and YMMV To Japan from HK 9 hops. Latency ~75ms. Bandwidth ~ 2.2MB/sec. To Fremont from HK 14 hope, Latency ~155ms. Bandwidth ~ 1.1MB/sec

by latch 15y ago

FWIW and YMMV To Japan from HK 9 hops. Latency ~75ms. Bandwidth ~ 2.2MB/sec. To Fremont from HK 14 hope, Latency ~155ms. Bandwidth ~ 1.1MB/sec

codexon 15y ago

Just curious, is Japan a good place for serving Russia and Australia?

oohmeplums 15y ago
From my iiNet DSL2+ connection in Perth, Australia to tokyo1.linode.com, I get 204ms ping and 14 hops, and from a Telstra fibre connection, I get 174ms and 15 hops. That compares to about 250ms and 12 hops on iiNet, and 210ms and 14 hops on Telstra to fremont1.linode.com. A little bit quicker, I think.
- jacques_chester 15y ago
  Yes, it's faster than Fremont. I moved to Dallas a few weeks ago after the third Fremont outage; now I wish I'd known this was coming down the pipeline. ... maybe I'll move again. It'd shave 50-60ms.
ajtaylor 15y ago
Our linode is currently in London (I didn't set it up...), but I'm probably going to request a move to the Tokyo datacenter in the next week. Ping times to Tokyo (136 ms) are literally half what they are to London (297 ms) and still better than Fremont (208 ms). Seems like a no-brainer to try moving it.
- getsat 15y ago
  Where are you located? Your ping times don't mean much without a reference point.
  - shimon_e 15y ago
    Based on those times I'd say he is in Russia or very close to an Australia-Japan peering exchange.
  - ajtaylor 15y ago
    I'm in Sydney, Australia.
nl 15y ago
It's not great for Australia. Most ISPs will route to Japan sensibly, but a few try and save money and route via the US (note that this is the same as hosting with Amazon in Singapore).

itsnotvalid 15y ago

Thanks. isn't that seems to be a choice now for HK devs wanting a quality service for hosting?

latch 15y ago
I'd say the other option is EC2/AWS/Amazon with their presence in both Tokyo and Singapore. But the choice between Linode or AWS tends to come down to other things (Linode is cheaper and I'd say simple/more predictable...AWS is more complex and offers way more "cloud" services).