Following evaluation of the options concerned, Internode has taken the decision to invest in building a new international point of presence (PoP) site.

The new site will be in Tokyo, Japan.

This will be implemented as a 'breakout' of our existing capacity purchases from Australia via Japan to the USA on the AJC cable system.

Its not as simple as it might sound to do this - because getting from the coastal landing sites for AJC and other cable systems through to Tokyo is a bit of a challenge - its about 100 km's between the two, so the gigabit fibre patch leads need a little help :)

But... we're doing it - and indeed we are already well advanced on making it happen.

I won't provide a commit date on it because there are several components to making this work and we're trying to get them all done before we declare victory. We are expecting, however, that it should all be done within a month or two - again, we're already well advanced on much of it.

We'll be putting in an initial capacity breakout of the order of 622 Megabits per second, Sydney to Tokyo, which should be adequate for a start :)

What this will do:

- Add one more country to our network map

- Dramatically lower the latency of data flows between Australia and Japan (and onward to various other Asian destinations)

- Improve our redundancy and options in terms of gaining further transit connectivity to the world over time, and improve our global availability of access to the Internet for the same reason.

- Link us to a new market with new opportunities in it, for business and residential customers:

Business customers may find this boosts their ability to use Internode to reach Asian destinations efficiently; Residential customers should find this will improve performance for applications such as VoIP and online gaming into significant parts of Asia.

- Increase our global peering (we'll peer with Japanese Internet providers and content backbones such as Google Japan, etc etc).

We have a similar opportunity to establish a breakout into New Zealand, for largely similar reasons, and that option is currently being evaluated as well. Note that an NZ breakout is not a commitment at this time - only the Japan one is committed at this point.

There will be some media releases about this in due course, but I thought you might want to hear about it first, here :)

This is not a cheap exercise (to put it mildly) - but in all sorts of ways, its something we just had to do.

Regards,
Simon Hackett

You heard it first on the Washing Machine.

Nice work, the desire to expand the pretty map was clearly the driving force.

Good work, Simon. thanks for the heads up.

given the strength of the asian economies and the booms as china and india move out of the 3rd world economy it is probably a long sighted move.

Thats awesome! :D

Simon Hackett writes...

But... we're doing it - and indeed we are already well advanced on making it happen.

Another reason to add to the list on why Internode is going from strength to strength :)
Good news Simon!
Quick question: Would this reduce traffic latency to broader places like Europe?

Shafto writes...

Quick question: Would this reduce traffic latency to broader places like Europe?

Probably not. Long story short, most transit from Asia to Europe runs via the USA.

There are cable paths to Europe via the middle east, but there are various negatives about them (including the distance not being much different in the end), and such that sheer economics tends to drive most traffic the other way around the ball.

Shafto writes...

Quick question: Would this reduce traffic latency to broader places like Europe?

Not really - Europe via Northern Asia is very close to Europe via the US.

Until a new cable from Perth to Singapore or India comes up there's not going to be a great way of reducing it significantly.

Hey. This would sound great to get to in NZ

~Luke

Ahh I see, that makes sense.
Thanks for the replies Simon & Matthew.
I got a second opinion! ;)

Shame there is still no official support for Western Europe. :(
The NZ pop sounds good, lots lower ping for there game servers. :P

Binary Smells writes...

The NZ pop sounds good, lots lower ping for there game servers. :P

I'm interested in any high ping NZ servers so we can ensure any connectivity we do there works well.

Matthew Moyle-Croft writes...

I'm interested in any high ping NZ servers so we can ensure any connectivity we do there works well.

Fix = Find somone over there on dial up to host a server :D

Binary Smells writes...

Fix = Find somone over there on dial up to host a server :D

??

I'm trying to be serious - if there are specific servers or providers with higher latency than just AUS to NZ would imply, then I'd like to know what they are so that we can see if any connectivity will fix that.

Matthew Moyle-Croft writes...

if there are specific servers or providers with higher latency than just AUS to NZ would imply

Might be worth getting Kingsley to query that on the games forum (if you haven't already). I'm sure there will be a bunch of Unreal Tournament players just itching to give you some good targets (I seem to recall that had been a bit of a thorn on occasion). ;)

NZ Internet is **** Connections are **** too. We Need a new Company to provide a PoP

Simon Hackett writes...

We have a similar opportunity to establish a breakout into New Zealand, for largely similar reasons, and that option is currently being evaluated as well.

Awesome!

Note that an NZ breakout is not a commitment at this time - only the Japan one is committed at this point.

Please make this happen :)

Call me Bob writes...

Awesome!

Please make this happen :)

What's wrong with connectivity into NZ as it stands right now? I don't think that I've ever had any real problems with it.

Its rubbish. Slow. they say as fast as your line handles. Most places maxing it at 50kb to 300KB

If u lucky

Simon Hackett writes...

- Dramatically lower the latency of data flows between Australia and Japan (and onward to various other Asian destinations)


Awesome!
(last time I was in Japan, traceroute showed that I was being reached via a rather indirect path).

Awesome news.

Very happy to see this news/info :)

Lukeintosh writes...

Its rubbish. Slow. they say as fast as your line handles. Most places maxing it at 50kb to 300KB

Well, while we have no plans to become an ISP in NZ (thats a whole 'nuther kettle of prawns), we'd be more than happy to sell rocking global transit connections to ISPs currently in NZ that wanted one :)

bradp writes...

What's wrong with connectivity into NZ as it stands right now? I don't think that I've ever had any real problems with it.

Mostly it's ok. Though there are times when NZ traffic seems to take a route via the US.

Maybe when NZ wins another ANZAC test we may consider an ISP moving into NZ. :P

Simon Hackett writes...

This will be implemented as a 'breakout' of our existing capacity purchases from Australia via Japan to the USA on the AJC cable system

Can you explain a bit more on that.

damo81 writes...

Can you explain a bit more on that.

Internode's AJC links already travel through Japan, but from there they've currently only got connectivity to the US.

IE - Even though it's already landing in Japan, it's essentially just acting as a big link direct to the US, because that's the only place it's got to go.

Installing a new PoP in Japan means that once data hits that point - instead of just routing it automatically through to the US - they'll actually be able to route it onwards to other locations as well [IE - the rest of Asia].

niiiice :D

Call me Bob writes...

Mostly it's ok. Though there are times when NZ traffic seems to take a route via the US.

I've experienced this too, but I don't have any specific examples on hand.

Simon Hackett writes...

Well, while we have no plans to become an ISP in NZ (thats a whole 'nuther kettle of prawns)

Don't you mean 'a whole 'nuther kittle of fush' ??

:)

Lukeintosh writes...

Its rubbish. Slow. they say as fast as your line handles. Most places maxing it at 50kb to 300KB

not want ing to burst burst your bubble, but evur thurt ur just on sa shurt line? :-P

Matthew Moyle-Croft writes...

Until a new cable from Perth to Singapore or India comes up there's not going to be a great way of reducing it significantly.

I would have thought India would be more Viable, given that *MOST* of the Connectivity currently goes through Alexandrea (SP) where they had the cable cut recently, which disconnected 75% of India's connectivity.

Or how about India, via Singapore ?

Brian White writes...

Or how about India, via Singapore ?

Part of the issue is getting capacity going west from Australia.

Matthew, here's a New Zealand server i'ed love to see fixed, it's a Quake 3 server.

gamers.net.nz ultra freeze lpb
60.234.73.177:27965

Routing to it is fine, but we get routed back via the USA.
Internode have previously tried to fix this, but to no avail, as it was up to telstraclear (i think) to play ball, they didn't want to.

Michael Kratz writes...

Part of the issue is getting capacity going west from Australia.

I already thought there was a cable going from Perth to Singapore (SEA-ME-WE 3)?

Fantastic news. Anyone here who has setup intranet VPNs to Asia and witnessed the mayhem from last years earthquake will know what I mean. Quite often the best latency to China was when packets went through Japan (this was on Optus).

Businesses will pay a premium to make life easier dealing with Asia.

Mr B writes...

gamers.net.nz ultra freeze lpb
60.234.73.177:27965

Routing to it is fine, but we get routed back via the USA.

Seems perfectly fine to me.

Tracing the path to 60.234.73.177 on TCP port 27965, 30 hops max
1 lns4.mel6.internode.on.net (150.101.212.22) 14.264 ms 14.647 ms 14.778 ms
2 gi1-3.cor1.mel6.internode.on.net (150.101.212.158) 12.979 ms 15.349 ms 12.308 ms
3 gi5-2.cor3.mel4.internode.on.net (150.101.212.136) 25.853 ms 25.984 ms 27.534 ms
4 pos2-1.bdr1.syd6.internode.on.net ­ (150.101.120.122) 27.475 ms 25.705 ms 25.338 ms
5 Gi14-0-3-503.gw2.syd1.asianetcom.n­ et (150.101.197.34) 26.543 ms 25.406 ms 26.292 ms
6 po6-0.cr2.syd1.asianetcom.net (202.147.40.138) 26.291 ms 25.737 ms 25.570 ms
7 so-0-0-0-0.gw4.akl1.asianetcom.net­ (202.147.55.253) 50.439 ms 48.657 ms 53.399 ms
8 Orcon-Internet.gw4.AKL1.asianetcom­ .net (203.192.166.70) 50.688 ms 50.172 ms 50.929 ms
9 gi-5-8.dsw1.nct.orcon.net.nz (60.234.9.24) 51.422 ms 50.179 ms 50.913 ms
10 60.234.73.177 [closed] 51.928 ms 50.261 ms 50.732 ms

webby writes...

I already thought there was a cable going from Perth to Singapore (SEA-ME-WE 3)?

forum-replies.cfm?t=9104...479927#r14479927

Not enough capacity for us.

webby writes...

I already thought there was a cable going from Perth to Singapore (SEA-ME-WE 3)?

Its very old - and very full. No more room at the inn there (at any price).

There are some efforts underway to raise capital to build a new cable from Perth up into Asia. But its not happened yet.

Moar conectvitivy = good news (and well done, too!)

Time for some pwning of the Japanese over XBL :P

Download speed increases in general from jp hosts, will also be welcome

Mr B writes...

Routing to it is fine, but we get routed back via the USA.
Internode have previously tried to fix this, but to no avail, as it was up to telstraclear (i think) to play ball, they didn't want to.

Yes, that should be a good example of something that would become a non-issue if we built a breakout in New Zealand in our own right.

The reason the return traffic is heading via the USA is that BGP routing is not only complex, but its also quite dumb in some ways (ways that tend to increase its resilience, but which can be a problem at boundary points like this). The point is that the nearest Internode router on the return path, in the view of that system... is the one in the USA.

("Nearest" in BGP, long story short, tends to mean 'lowest number of router hops' - not shortest physical distance - which isn't measured or stored in BGP)

Obviously if we fielded a router in NZ, then that'd be the closest, and it would therefore tend to 'attract' the return packets properly back into itself.

Simon

Binary Smells writes...

The NZ pop sounds good, lots lower ping for there game servers.

Since when did NZ get more than a few cans connected by string? They only got leckky a couple of years ago. :-)

CypherOz writes...

Since when did NZ get more than a few cans connected by string? They only got leckky a couple of years ago. :-)

[OT]Umm, actually until internode rolled out ADSL2, their speeds were better than anything on offer here (Thanks Telstra). OT]

Brian White writes...

I would have thought India would be more Viable, given that *MOST* of the Connectivity currently goes through Alexandrea (SP) where they had the cable cut recently, which disconnected 75% of India's connectivity.

Or how about India, via Singapore ?

While it's all very fine suggesting "nice" places to go if there isn't any actual demand to pay for it then you've just burned a whole lot of money for no additional revenue. At the moment pricing of significant capacity into India would take your breath away, and it's cheaper to just bypass it onto Europe.

The broken cables also illustrate another problem in that if you want a reliable service then you're going to have to buy capacity on two systems to your ultimate destination. When crossing the Pacific you can do this just with SCCN since it has two paths on its figure of 8 system but that doesn't apply when heading to Europe. Of course both SMW4 and Flag failed simultaneously recently so if you had used both of them for your protection you would have still lost out anyway. SMW3's reliability is terrible compared to the other two but it managed to avoid the submarine back hoe that took out SMW4 and Flag.

in NZ would you plug into www.citylink.co.nz - or www.nzix.net ?

maybe on nodephone, dialing from AU to NZ could be a 18c "untimed national" call. :-)
How about a NZ DID?

MIAH

miah writes...

in NZ would you plug into www.citylink.co.nz - or www.nzix.net ?

We'd most likely peer at the Auckland exchange in line with our general peering strategy. We're still exploring what options exist and what we want to achieve in NZ, so beyond that I can't comment.

Matthew Moyle-Croft writes...

I'm interested in any high ping NZ servers so we can ensure any connectivity we do there works well.

This traceroute is good enough for me

Target Name: gpstore.com.au
IP: 202.89.36.243
Date/Time: 3/20/2008 10:53:36 AM

2 29 ms 29 ms 32 ms lns10.syd7.internode.on.net [150.101.197.27]
3 30 ms 29 ms 29 ms vl14.cor2.syd7.internode.on.net [150.101.120.83]
4 30 ms 30 ms 29 ms po3.bdr1.syd6.internode.on.net [150.101.199.232]
5 30 ms 30 ms 30 ms Gi14-0-3-503.gw2.syd1.asianetcom.n­ et [150.101.197.34]
6 31 ms 31 ms 30 ms po0-1.cr2.syd1.asianetcom.net [202.147.40.125]
7 53 ms 53 ms 53 ms so-0-0-0-0.gw4.akl1.asianetcom.net­ [202.147.55.253]
8 54 ms 54 ms 52 ms gi9-3.gw1.akl1.asianetcom.net [202.147.55.209]
9 55 ms 56 ms 55 ms MaximumInternet.gw1.akl1.asianetco­ m.net [202.147.41.66]
10 55 ms 54 ms 56 ms gi5-1.hsa1.alb.maxnet.net.nz [123.100.64.131]
11 58 ms 56 ms 55 ms gpstore.com.au [202.89.36.243]

Simon Hackett writes...

we'll peer with Japanese Internet providers and content backbones such as Google Japan

Google Japan?... how does that work out? i thought that you JUST peer with Google in the USA.

Another GSR12000 going in there also?

Great work once again!
Internode are getting bigger and better than ever :>

Cant wait to see Internode in 10+ yrs.
Rulers :> haha

Google Japan? I thought Yahoo/YahooBB was the only content provider in Japan.

This investment is mostly for the benefit of gamers right? What kind of latency can we expect playing games on servers in Japan, Korea and China? I think I can already get about 200ms now. Palying with the American and European community is usually too laggy and time difference is an issue too. It will also be good to bet decent download speeds from Japanese servers.

Any chance of a breakout from the AJC north through the Bering Strait, under the Arctic ice-cap, then down to Iceland, and into Europe?

Just hire an ex-soviet submarine, load it up with cable fed out of the missile tubes, rename it the SS Internode and you're away.

If you could get that done by June, I can read the Guardian website with slightly less latency.

As an added benefit, you'd get lower latency to the East coast.

And here's the kicker - open a "green" server colo in Iceland with natural cooling AND geothermal power!. No CO2 emmissions!

Mr Bubbles writes...

This investment is mostly for the benefit of gamers right?

No ... it's going to [positively] affect anything that's latency dependent, and that covers a lot more than just gaming.

VoIP is one big example, as well as people who have VPNs etc into Asian countries.

What kind of latency can we expect playing games on servers in Japan, Korea and China?

Try some traceroutes from another ISPs network to see [roughly] what you can expect.

einstein.dontexist.net/austrace

I think I can already get about 200ms now.

Not with Internode you won't be!

It will also be good to bet decent download speeds from Japanese servers.

There shouldn't be any problems with download speeds as they are right now. They're an example of something that's not adversely affected by higher latency.

LittleRascal writes...

Any chance of a breakout from the AJC north through the Bering Strait, under the Arctic ice-cap, then down to Iceland, and into Europe?

Better get-in-line.

Internode will undoubtedly consider it more important to run backhaul from Fawkner to Coburg exchange so that I can have ADSL2+. Sorry, ahem, so that all the good townsfolk connected to the Fawkner exchange can have ADSL2+. ;-)

And it's only 4 kms or so, unlike your undersea cable. And it doesn't require a submarine.

This is terrific news. Will improve streaming video where the remote server uses domestic (Japan) buffer sizes no end.

Now can Internode lead the market by making the link work faster than the speed of light so we can get sub 80mS ping times to Japan?

It's on the to-do list isn't it Simon?

Kevmeister writes...

Sorry, ahem, so that all the good townsfolk connected to the Fawkner exchange can have ADSL2+. ;-)

How many Polar Bears are there in Fawkner? At a guess, not many. Glaciers? I don't think so.

Never underestimate the importance of polar bears in undersea cable network design.

Mr Bubbles writes...

Google Japan? I thought Yahoo/YahooBB was the only content provider in Japan.

Err no. There's heaps of them in Japan.

I tell you what!

Great news XD

As for the SS Internode... Wishful Thinking LOL

I just had another great idea for the SS Internode.

A cable to Cape Town via Antarctica.

We go south from Hobart to McMurdo, then across the ice suspending the cable on indestructable Hill's Hoists, then north to Cape Town.

It would finally give everyone a reason to put capacity into Tasmania.

LittleRascal writes...

I just had another great idea for the SS Internode.

A cable to Cape Town via Antarctica.

We go south from Hobart to McMurdo, then across the ice suspending the cable on indestructable Hill's Hoists, then north to Cape Town.

A fine plan in all its glory but sadly the cost of backhaul from Tas to Vic scuttles the whole idea in one fell swoop.

Proudly brought to you (at exorbitant prices) by Telstra. Keep on smiling.

Just tell me this please....why was Simon Hackett not given the job as boss of Telstra?

Pretty sure this guy is the most innovative, and proactive business man in the telecommunications industry. He also is a straight shooter (yet still diplomatic), and (to the best of my knowledge) is an honest man with integrity.

He has surrounded himself with a knowledgable, and highly capable team, and together I can see no better team around.

Love reading what you have to say, and also what you and Internode do, Simon.

Congrats.

i like ya way of thinking ....dam clothes lines are indestructable

audifred writes...

Just tell me this please....why was Simon Hackett not given the job as boss of Telstra?

<snip>

You just answered your own question :)

Adam

Woohoo.

My Japanese MMOs will now play better!

good work, keep on expanding!

Hai Nyuu writes...

My Japanese MMOs will now play better!

I'm interested in any IPs you have of MMO servers.

does wow have any asian servers? or all in America?

battlenet connections should definately benefit

Hobbsy writes...

does wow have any asian servers?

Yes, in Korea and China.

or all in America?

Nope ... they've also got plenty of servers around Europe as well.

wowwiki.com/Realms_List

Matthew Moyle-Croft writes...

I'm interested in any IPs you have of MMO servers.

I play Gundam Tactics Online. I'll try and see if I can dig up the IP address for you tonight, though it's not a game that relies too much on latency.

So WoW performance should pick up a bit if people are willing to move realms. I assume that pings to Asia are around half that to the US?

Transfers to WoW Korea, China or Taiwan are impossible. For China and Korea, you might even need a Social Security number of some kind as when I tried to apply for Korean RO it asked me for it.

Hobbsy writes...

I assume that pings to Asia are around half that to the US?

LOL ... not quite.

Japan still pings about 150ms return from Sydney.

well it's still a small improvement.

audifred writes...

Just tell me this please....why was Simon Hackett not given the job as boss of Telstra?

They probably offered him the job, but he turned it down as he knows that some things are just not worth fixing :P

Hobbsy writes...

well it's still a small improvement.

It's a large improvement. At the moment it goes up past Japan, to the US then back to Japan. So probably around 15 to 20,000km further than it has to I believe + a couple of extra hops.

Speed of light is 299,792,458 meters per second. So to travel 20,000,000 meters would take 67ms. Now you incur this penalty there and back, so in terms of ping times it will equate to approximately 130ms.

For example, a Team Fortress 2 server from Japan (www.game-monitor.com/sea...=tf2&location=JP):

Pinged it from my home machine in Adelaide:
C:\Documents and Settings\Admin>ping 121.112.159.131

Pinging 121.112.159.131 with 32 bytes of data:

Reply from 121.112.159.131: bytes=32 time=326ms TTL=48
Reply from 121.112.159.131: bytes=32 time=327ms TTL=48
Reply from 121.112.159.131: bytes=32 time=327ms TTL=48
Reply from 121.112.159.131: bytes=32 time=326ms TTL=48

Ping statistics for 121.112.159.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 326ms, Maximum = 327ms, Average = 326ms

And now pinged from my web server (in the US):
C:\Documents and Settings\Administrator>ping 121.112.159.131

Pinging 121.112.159.131 with 32 bytes of data:

Reply from 121.112.159.131: bytes=32 time=173ms TTL=47
Reply from 121.112.159.131: bytes=32 time=176ms TTL=47
Reply from 121.112.159.131: bytes=32 time=176ms TTL=47
Reply from 121.112.159.131: bytes=32 time=173ms TTL=47

Ping statistics for 121.112.159.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 176ms, Average = 174ms

Now pinging that US server from my box:
C:\Documents and Settings\Admin>ping

Pinging *** * with 32 bytes of data:

Reply from ***: bytes=32 time=220ms TTL=114
Reply from ***: bytes=32 time=220ms TTL=114
Reply from ***: bytes=32 time=220ms TTL=114
Reply from ***: bytes=32 time=220ms TTL=114

Ping statistics for ***:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 220ms, Average = 220ms

So it'd take approximately 390ms to go from my box, to the US and back to Japan which is an extra 170ms. And note that the US box is in the middle of the US, where as Internode would connect to the West coast so that explains the extra 40ms from the calculated 130ms saving.

Also note that Australia is closer to Japan than the US is to Japan (slightly). So sub 150ms pings should be possible, especially from Sydney.

If I wanted to be more accurate I could have done trace routes and picked where they cross in LA to calculate the actual difference.

Cling Wrap writes...

Speed of light is 299,792,458 meters per second.

In a vacuum ...

Light only travels ~2/3 that speed through fiber optics.

So to travel 20,000,000 meters would take 67ms. Now you incur this penalty there and back, so in terms of ping times it will equate to approximately 130ms.

US <-> Japan takes around about 110ms round trip coast to coast.

Cling Wrap writes...

Also note that Australia is closer to Japan than the US is to Japan (slightly). So sub 150ms pings should be possible, especially from Sydney.


This is currently with iinet:

Pinging 121.112.159.131 with 32 bytes of data:

Reply from 121.112.159.131: bytes=32 time=136ms TTL=47
Reply from 121.112.159.131: bytes=32 time=136ms TTL=47
Reply from 121.112.159.131: bytes=32 time=136ms TTL=47
Reply from 121.112.159.131: bytes=32 time=136ms TTL=47

Ping statistics for 121.112.159.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 136ms, Average = 136ms

I am very :) at the moment :)

Cling Wrap writes...

Speed of light is 299,792,458 meters per second.

... in a vacuum. In glass it's about two thirds of that (more or less; varies slightly depending on the optical density of the glass)

- mark

Cling Wrap writes...

Also note that Australia is closer to Japan than the US is to Japan (slightly). So sub 150ms pings should be possible, especially from Sydney.

Yeah - cable station to cable station the latency is about 112ms.

So, ADSL2+ Low latency in Sydney to a host in Tokyo should be in the order of 130-140ms.

Can someone enlighten me as to what content we are currently pulling from Japan/Asia which doesn't fit the below categories:

1. connections to Asian offices (branches / HQ's etc)
2. Gaming Servers
3. People visiting web sites in their motherland etc

Just curious. I understand that Google has a fair amount of content delivered out of Japan, so is peering with them in Japan going to be better than bringing it across from the US?

Maybe im to ocker to know otherwise - just not sure what kind of interesting content comes from Japan (or Asia). What am I missing out on?

bradp writes...

Light only travels ~2/3 that speed through fiber optics.

I also made another mistake by doubling the distance and then doubling the latency when I should have just doubled one. Although coincidently my combination of errors ended up being pretty accurate in terms of real world performance.

Simon Hackett writes...

decision to invest in building a new international point of presence (PoP) site.

Well done Internode, keep up the excellent work!!!

©£ONeST@® writes...

This is currently with iinet:

This is what I get with 'Node on the Ulladulla NSW exchange.

>ping 121.112.159.131

Pinging 121.112.159.131 with 32 bytes of data:
Reply from 121.112.159.131: bytes=32 time=336ms TTL=49
Reply from 121.112.159.131: bytes=32 time=335ms TTL=49
Reply from 121.112.159.131: bytes=32 time=334ms TTL=49
Reply from 121.112.159.131: bytes=32 time=334ms TTL=49

Ping statistics for 121.112.159.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 334ms, Maximum = 336ms, Average = 334ms

>tracert 121.112.159.131

Tracing route to i121-112-159-131.s11.a023.ap.plala­ .or.jp [121.112.159.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ipcop.localdomain [192.168.0.1]
2 * 29 ms 30 ms lns10.syd7.internode.on.net [150.101.197.27]
3 29 ms 29 ms 29 ms vl14.cor2.syd7.internode.on.net [150.101.120.83]

4 186 ms 185 ms 186 ms gi0-3.bdr1.syd7.internode.on.net [150.101.197.46
]
5 185 ms 185 ms 185 ms pos2-0.bdr1.sjc2.internode.on.net ­ [203.16.213.41]
6 187 ms 187 ms 188 ms ge-3-7.r02.snjsca04.us.bb.gin.ntt.­ net [129.250.11.97]
7 213 ms 214 ms 214 ms ae-2.r21.snjsca04.us.bb.gin.ntt.ne­ t [129.250.4.9]
8 313 ms 336 ms 314 ms as-0.r21.tokyjp01.jp.bb.gin.ntt.ne­ t [129.250.5.82]
9 285 ms 286 ms 286 ms 129.250.11.54
10 287 ms 288 ms 287 ms 210.145.252.185
11 283 ms 284 ms 283 ms 221.184.4.10
12 323 ms 324 ms 323 ms 218.43.251.254
13 283 ms 283 ms 284 ms i210-225-225-222.s99.a049.ap.plala­ .or.jp [210.225.225.222]
14 328 ms 330 ms 329 ms 210.225.224.188
15 331 ms 349 ms 339 ms 58.95.254.138
16 334 ms 337 ms 335 ms i121-112-159-131.s11.a023.ap.plala­ .or.jp [121.112.159.131]

Trace complete.

FTTH Test Case writes...

2. Gaming Servers

Thats a big one for me.
With telstra it was a good sub 200 ms.
With Internode its a good 300 ms.

It will be nice to play with my friends in Japan again.

FTTH Test Case writes...

What am I missing out on?

I think it's important to understand that we have a large Asian population in Australia, who want to look at content in their first/native language. So you personally may not be missing out on a lot, it'll help our customers that do want faster access to that content.

audifred writes...

why was Simon Hackett not given the job as boss of Telstra?

Because then he'd be forced into making as much money as possible and not the most innovative, and proactive business man in the telecommunications industry.

Being CEO of Telstra is not as easy as some may think.

No doubt Simon is happy with where he is now.

Mark Newton writes...

... in a vacuum. In glass it's about two thirds of that (more or less; varies slightly depending on the optical density of the glass)

Damn that cursed Luminiferous aether!

Will you be selling private IP to japan for corp customers?

kemza writes...

Will you be selling private IP to japan for corp customers?

Sure - we've been focusing on building the POP itself, but certainly one of the reasons for doing so is to enable MPLS VPN services for corporate customers (we do this out of our US POPs already).

Would this improve transfer speeds from manufacturers in Taiwan and China or is that problem largely there own connections not being big enough?
EG near all computer hardware makers. The largest and most common that comes to mind is www.realtek.com.tw which normally has terrible speeds.

Will the new PoP site be in Equinix,Tokyo? or where

And will you be connecting to other networks in there?

damo81 writes...

Will the new PoP site be in Equinix,Tokyo?

Yes.

And will you be connecting to other networks in there?

Thats kinda the point :)

Simon Hackett writes...

Thats kinda the point :)

I knew that :)

Simon Hackett writes...

There are some efforts underway to raise capital to build a new cable from Perth up into Asia. But its not happened yet.

That'd be nice to see. I kinda like redundancy, and not being forced to route everything through the US.

As I understand it, we pay to connect to the US, the UK pays to connect to the US, and when we want to connect to the UK then we both have to pay while the US does not. Maybe I'm being petty or misunderstanding the system though :)

GregAlex writes...

That'd be nice to see. I kinda like redundancy, and not being forced to route everything through the US.

I kinda do, too. Thats one of the reasons for the investment in a PoP in Japan.

As I understand it, we pay to connect to the US, the UK pays to connect to the US, and when we want to connect to the UK then we both have to pay while the US does not. Maybe I'm being petty or misunderstanding the system though :)

Long story short, everyone else pays to reach the USA, in terms of international circuit costs.

At a deep level, the global Internet is subsidised, in the USA, by the rest of the world, as a result. Its one of the reason for better (Internet) deals there, although the gap in value terms progressively continues to close (as the relative cost of international circuits lowers over time).

Are you still going to keep the AJC links via japan to the USA

damo81 writes...

Are you still going to keep the AJC links via japan to the USA

of course, we want to keep the redundancy of having links to the US via two separate cable systems.

Wont purchasing more bandwidth cost more money meaning higher costs and more price increases

Brad Amm writes...

Wont purchasing more bandwidth cost more money meaning higher costs and more price increases

No ...

To get there right now they've got to pay for capacity into the US, and then from there to shunt the data back to Asia.

Every mbit that uses this new [direct] link, doesn't have to make that double trip, and is also 1 mbit less that's going to be taking up capacity on the direct US links.

Simon Hackett writes...

We'll be putting in an initial capacity breakout of the order of 622 Megabits per second, Sydney to Tokyo, which should be adequate for a start :)

so a 622Mb/s SYD - LAX1/SJC2 becomes
622Mb/s SYD - JPN1 and 622Mb/s JPN1 - LAX1/SJC2
Will the redundancy to Japan will be by LAX1/SJC2 and SXC?

p.s. I like the open and transparentness of the Internode Network, it gives me confidence in the network you are building, and helped me choose NODE for my ADSL,
SO, when will internode customers be able to see the cacti graphs
( like monitor.waia.asn.au/cact...d=143&rra_id=all )
for the complete network? i'm a graph watcher!!!

miah writes...

SO, when will internode customers be able to see the cacti graphs

They've got something even better.

nodemap.internode.on.net

miah writes...

SO, when will internode customers be able to see the cacti graphs


Sorry, but you won't. That data is commercially sensitive, and hence, won't be made public :)

Michael Kratz writes...

Sorry, but you won't. That data is commercially sensitive, and hence, won't be made public :)

You don't have to hide this, its a selling point. like your network map, its also commercial info, but you show that! and i'm the type that respect YOU for showing it - not many other ISPs do show, but i USE internode because you are open to discuss your network, ( - average people- who don't CARE about their networks use DODO or BIGPOND etc)

I'm not just any 'joe blow' member of the public, i'm a NODE customer, i have a commercial relationship with NODE, i'd look at signing a NDA. Easy to make it available to only NODE IP ranges or somthing!

do you mind WAIX publishing their cacti? maybe PIPE should publish their cacti ALSO !

Are the savings going to be passed onto the customer, which was brought up by Simon only a short time ago.

miah writes...

do you mind WAIX publishing their cacti? maybe PIPE should publish their cacti ALSO !

They already do.

You just need a login to the PIPE DB to see this - so you'll either be a carrier or a company with it's own IP space which you are advertising to the IX. In other words, the graphs are there, but they are not open to the general public.

But what does it really matter what the graphs and figures look like? You're buying a service from an ISP - and how it is bolted together is irrelevant unless you can suggest there is an issue causing some impact. Just the same as you don't expect graphs of utilisation of other utilities such as your street water supply, neighbourhood KWh usage from a power company, or delivery details of gas for your local service station....

Get on with enjoying the Internet service now and in the future as that is what you are buying, not wasting time looking for and thinking about things like utilisation graphs :->

miah writes...

You don't have to hide this, its a selling point. like your network map, its also commercial info, but you show that!

You missed the word "sensitive". Obviously that specific information is too sensitive to be given to the general public/competitors. The same that at work we are not permitted to give information to the public relating to actual stock levels at our store, we're allowed to tell them if we only have "a couple" of "plently" but not actual numbers.

Do you mean the network map?

damo81 writes...

Do you mean the network map?

No he means actual data flow through the network map, not what it's capable of.

sorry about the OT comments, back to the topic of
> Internode to establish PoP in Japan

Woohoo, this is great news!

Will this provide us with any advantages with Youtube streaming for example? or is youtube streaming from the US anyway?

webby writes...

Will this provide us with any advantages with Youtube streaming for example? or is youtube streaming from the US anyway?

Won't change Youtube.