This is the console and we're doing the Inter-Region Latency testing. Let's go ahead and find where that is. You click on the main menu, you go down to networking, and select here the last option under networking, Inter-Region Latency. Remember that we're testing resources going from Melbourne to our Phoenix area. To find that, you can either click here. Actually it's better to do it in the top row, so I find Phoenix right here, and then I search for Melbourne. As you can see, here it is, right here. It's 181 milliseconds, and it will give you all the results for every single region connecting either to Phoenix in this case. Right here you can see the latency to Amsterdam, this is Brazil, and here's Melbourne which is the one that we want. The same thing for Melbourne, here, you can see the sample was to go to Sydney. Sydney should be around here, so you find it in Sydney, and then you find Melbourne. It should be right here, and it makes sense, it's going within the same country, 13 milliseconds. But when you're going from Phoenix to Melbourne, it's a little bit longer, the distance, so it's 181 milliseconds. Let's see if that's real. What I did is create resources in both regions and we can use these resources where the network is [inaudible]. This is the correct training compartment. You should see the Melbourne going to Phoenix. If I change this to Phoenix, then you will see that for Phoenix, we're going to Melbourne, and that connection is already established, I already created the routes. As you can see in Phoenix, I have another VCN that is completely isolated. But this the one that we care about, PhoenixVCN, going all the way to Melbourne. I created two compute instances. Let's go ahead and take a look. One in each region. I'm going to ping from Melbourne into the private IP address. I have my Phoenix compute instance. Let's go ahead and copy this, so it's 172.29.0.62 and the compute instance in Melbourne, I actually need the public IP address of it, so I can SSH into it. Open this, run the connection. Now, I don't know if you remember the IP address of [inaudible] but Phoenix, 172.29.0.62. The reason why we're doing this is so we can verify that those numbers are accurate. You can see it's very close, within five milliseconds of it at 176. The numbers that you get from the Inter-Region Latency, they represent the overall backbone infrastructure. They're not specific to your own account, your own tenancy. Here it is a 180, that's the published ones, but when you actually test them, it's a little bit better on your own environment. This concludes the lab. Thank you very much.
