Solved

your advice on Internet latency  between Europe and ASIA ( Singapore)

Posted on 2014-11-28
5
848 Views
Last Modified: 2014-11-28
Hi to all of you.
I need your advice for the following situation:
In our HQ office located in Italy Europe, we have 20 people accessing an Amazon EC2 instance in Singapore Region.
My colleagues are using Microsoft remote desktop to work on a legacy 64bit application.
Colleagues  are complain that the “user experience” is not the same of having the application here in the office … and the support team of the legacy application states that the network latency between the office and the EC2 instance is slow.

I contacted our Internet service provider (pipponet) and provided a tracert from both directions (see below) and  the answer is: that the latency reported is acceptable between Europe and ASIA (Singapore) and it is  intrinsic in the connections between international carriers. It cannot be improved ( I asked also the possibility to change the routing to reach the EC2, no way. )

My questions are :
1) do you think this latency is acceptable or not?
2) is really an Intrinsic value this type of latency ?
2) What can I do to improve the latency without changing the Region of the EC2 Instance?

Thank you
Carlettus


PS: I made a change of our providers name and ip addresses of both ends for security




1)    TRACEROUTE FROM HQ officeHQ to Singapore AWS machine

c:\>tracert 48.59.218.154
 
Tracing route to ec2-48-59-218-154.ap-southeast-1.compute.amazonaws.com [48.59.218.154]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  172.19.7.1
  2    <1 ms    <1 ms    <1 ms  172.19.7.3
  3     1 ms    <1 ms    <1 ms  93-154-94-2.ip.pipponet.it [93.154.94.2]
  4     5 ms     1 ms     1 ms  81-208-53-1.ip.pipponet.it [81.208.53.1]
  5     3 ms     1 ms     3 ms  10.1.153.69
  6    17 ms     6 ms     5 ms  10.254.1.1
  7     2 ms     4 ms     1 ms  10.254.1.97
  8     2 ms     2 ms     2 ms  10.254.12.6
  9     1 ms     1 ms     2 ms  89.97.200.190
10     6 ms     5 ms     8 ms  89.97.200.33
11     3 ms     4 ms     1 ms  ge4-0.roma4.rom.seabone.net [195.22.192.73]
12   361 ms   360 ms   361 ms  xe-11-0-0.singapore2.sin.seabone.net [93.186.133.20]
13   364 ms   366 ms   364 ms  p38895.sgw.equinix.com [202.79.197.87]
14   359 ms   354 ms   359 ms  203.93.223.4
15   365 ms   366 ms   365 ms  203.93.223.23
16   356 ms   356 ms   355 ms  203.93.223.231
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
 
Trace complete.
 

 
2)     TRACEROUTE FROM Singapore AWS machine TO HQ office
 
 
tracert 93.154.94.1
 
Tracing route to 93-154-94-1.ip.pipponet.it [93.154.94.1]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ec2-175-41-128-234.ap-southeast-1.compute.amazon
aws.com [175.41.128.234]
  2    <1 ms    <1 ms    <1 ms  203.93.223.144
  3     1 ms     2 ms     1 ms  203.93.223.16
  4    <1 ms    <1 ms    <1 ms  203.93.223.3
  5     1 ms     1 ms     1 ms  6762.sgw.equinix.com [202.79.197.111]
  6   359 ms   359 ms   358 ms  ge2-0.roma4.rom.seabone.net [213.144.177.187]
  7   449 ms   449 ms   450 ms  fastweb.roma4.rom.seabone.net [195.22.192.74]
  8   350 ms   350 ms   350 ms  89.97.200.30
  9   360 ms   360 ms   360 ms  93-154-94-1.ip.pipponet.it [93.154.94.1]
 
Trace complete.
0
Comment
Question by:carlettus
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 12

Expert Comment

by:andreas
ID: 40470234
From my workplace connection (german scientific network) I have a turnaround time in the traceroute of 342ms for the IP 175.41.128.234. So it really seems this service has bad connectivity. My traceroute looks totally different from yours.

  6    14 ms    14 ms    14 ms  cr-tub1-hundredgige0-1-0-0-7.x-win.dfn.de [188.1.144.185]
  7    19 ms    19 ms    19 ms  be4193.rcr11.b015814-1.ham01.atlas.cogentco.com [149.6.142.101]
  8    18 ms    18 ms    19 ms  be2460.ccr42.ham01.atlas.cogentco.com [154.54.38.241]
  9    29 ms    29 ms    28 ms  be2187.ccr42.ams03.atlas.cogentco.com [154.54.74.125]
 10   107 ms   106 ms   107 ms  be2488.ccr42.lon13.atlas.cogentco.com [154.54.39.110]
 11   107 ms   107 ms   107 ms  be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85]
 12   111 ms   111 ms   111 ms  be2151.mpd22.dca01.atlas.cogentco.com [154.54.40.73]
 13   121 ms   122 ms   122 ms  be2171.ccr42.atl01.atlas.cogentco.com [154.54.31.109]
 14   137 ms   136 ms   136 ms  be2173.ccr22.iah01.atlas.cogentco.com [154.54.29.118]
 15   173 ms   173 ms     *     be2066.ccr22.lax01.atlas.cogentco.com [154.54.7.54]
 16   173 ms   173 ms   174 ms  be2179.ccr23.lax05.atlas.cogentco.com [154.54.41.82]
 17   172 ms   173 ms   173 ms  tata.lax05.atlas.cogentco.com [154.54.11.194]
 18   340 ms     *      340 ms  if-6-20.tcore2.LVW-Los-Angeles.as6453.net [64.86.252.65]
 19     *        *      344 ms  if-7-2.tcore2.SVW-Singapore.as6453.net [180.87.15.25]
 20   340 ms   340 ms   340 ms  180.87.15.206
 21   345 ms   344 ms   343 ms  203.83.223.58
 22   342 ms   341 ms   342 ms  ec2-175-41-128-234.ap-southeast-1.compute.amazonaws.com [175.41.128.234]
 23  203.83.223.74 Target network not reachable
0
 

Author Comment

by:carlettus
ID: 40470245
Hello,
thank you for your reply but as I wrote :

PS: I made a change of our providers name and ip addresses of both ends for security

I only need your advice on the data I wrote on my message.
Ciao
0
 
LVL 12

Accepted Solution

by:
andreas earned 500 total points
ID: 40470252
without a proper trace from another location its hard to tell if your provider has a chance to increase the round trip time. But if the ip adress was only chqanged in the last byte it should be no problem. As geoip indicates the Target IP of your trace sample is in singapore too it can very well be the same provider/route for the given IP and the IP you have problems with.

But you might trace it yourself e.g. from other internet connections instead to see where the slowdown comes from.

If all providers you can test with show a similar turn around time it would be difficult to do something about it.

But all in all connections from europe to SE-Asia are in general quite laggy. Im suffering similar problems between HongKong and Germany.
0
 

Author Comment

by:carlettus
ID: 40470359
Hello,
thank you , I only made the change to the last octet of the IP address.

As you said I made some test using an online tool at http://traceroute.monitis.com/ . The results is the same  ~ 360ms

I think I have al the info .
Thank you for sharing your trace .
Bye
CArlettus
0
 

Author Closing Comment

by:carlettus
ID: 40470361
b
0

Featured Post

Ready to trade in that old firewall?

Whether you need to trade-up to a shiny new Firebox or just ready to upgrade from whatever appliance you're using now, WatchGuard has the right appliance for you! Find your perfect Firebox today with appliance sizing tool!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
WARNING:   If you follow the instructions here, you will wipe out your VTP and VLAN configurations.  Make sure you have backed up your switch!!! I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

635 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question