Trace Root Is Not Reaching The Destination

Dear All,

We have hosted two different web sites in two different Amazone servers and both are located at Singapore region.
And clients are using web service request to download/upload the data. Now we are facing a strange problem,
while calling the web service there is a error like 'Not Able to Connect To Server' and this is happening only to one of the server.
When i tried trace root to the server, trace is reaching up to Amazone.com(203.83.223.237) from there continuously request time out is coming where as the trace is to the other server is reaching the destination passing through Amazone.com(203.83.223.237) .

Please find the attached screen shot for both the trace details.


Can anybody suggest a solution.
Trace_Details
dilipsjainAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zephyr ICTCloud ArchitectCommented:
It seems to be working from Dallas, Texas:
Tracing route to 54.254.159.223 [54.254.159.223]...
hop 	rtt 	rtt 	rtt 	  	ip address 	fully qualified domain name
1 	1 	2 	1 	  	208.101.16.73 	208.101.16.73-static.reverse.softlayer.com
2 	2 	0 	0 	  	66.228.118.157 	ae11.dar02.sr01.dal01.networklayer.com
3 	0 	0 	0 	  	173.192.18.252 	ae14.bbr01.eq01.dal03.networklayer.com
4 	2 	0 	0 	  	157.238.224.225 	ae-6.r07.dllstx09.us.bb.gin.ntt.net
5 	0 	0 	0 	  	129.250.2.173 	ae-2.r21.dllstx09.us.bb.gin.ntt.net
6 	39 	39 	39 	  	129.250.4.154 	ae-8.r23.snjsca04.us.bb.gin.ntt.net
7 	39 	40 	39 	  	129.250.2.182 	ae-0.r22.snjsca04.us.bb.gin.ntt.net
8 	* 	* 	* 	  		
9 	210 	210 	210 	  	129.250.7.19 	ae-1.r00.sngpsi05.sg.bb.gin.ntt.net
10 	209 	209 	209 	  	116.51.17.130 	ae-0.amazon.sngpsi05.sg.bb.gin.ntt.net
11 	209 	208 	208 	  	203.83.223.8 	
12 	212 	212 	212 	  	203.83.223.31 	
13 	220 	219 	219 	  	203.83.223.237 	
14 	210 	210 	210 	  	54.254.159.223 	ec2-54-254-159-223.ap-southeast-1.compute.amazonaws.com

Trace complete

Open in new window


Tracing route to 54.251.130.11 [54.251.130.11]...
hop 	rtt 	rtt 	rtt 	  	ip address 	fully qualified domain name
1 	0 	0 	0 	  	208.101.16.73 	208.101.16.73-static.reverse.softlayer.com
2 	0 	0 	0 	  	66.228.118.157 	ae11.dar02.sr01.dal01.networklayer.com
3 	0 	0 	0 	  	173.192.18.212 	ae6.bbr02.eq01.dal03.networklayer.com
4 	0 	0 	0 	  	157.238.224.229 	ae-11.r01.dllstx04.us.bb.gin.ntt.net
5 	0 	0 	0 	  	129.250.2.198 	ae-1.r21.dllstx09.us.bb.gin.ntt.net
6 	41 	40 	40 	  	129.250.4.154 	ae-8.r23.snjsca04.us.bb.gin.ntt.net
7 	40 	41 	40 	  	129.250.2.182 	ae-0.r22.snjsca04.us.bb.gin.ntt.net
8 	207 	214 	* 	  	129.250.3.49 	ae-2.r20.sngpsi05.sg.bb.gin.ntt.net
9 	218 	211 	218 	  	129.250.7.19 	ae-1.r00.sngpsi05.sg.bb.gin.ntt.net
10 	216 	219 	216 	  	116.51.17.130 	ae-0.amazon.sngpsi05.sg.bb.gin.ntt.net
11 	216 	216 	216 	  	203.83.223.8 	
12 	214 	223 	220 	  	203.83.223.31 	
13 	226 	220 	227 	  	203.83.223.237 	
14 	211 	211 	211 	  	54.251.130.11 	ec2-54-251-130-11.ap-southeast-1.compute.amazonaws.com

Trace complete

Open in new window


So maybe it's an ISP issue? Routing not propagated? ... Is it a continuous problem or is it coming and going?
Andy MIT Systems ManagerCommented:
Just done tracert's from here in the UK and both appear to be fine here too. As spravtek has said souns like an ISP/routing issue. I'd recommend speaking to Amazon and your ISP about it, get them talking to see if they can find the problem.
dilipsjainAuthor Commented:
Hi,

Thanks For the Reply.

This is a continuous problem and the problem is only with the clients who uses AirTel broad band connections.
As we discussed with the providers technical team, they are saying like request is reaching up to Singapore Amazone Server and that server is rejecting the request and they are stating that it is a amazone related issue.

But when do trace root to other server that is 54.251.130.11 with the same connection it is reaching there and this request also passing through the same Ip 203.83.223.237.

What may be the reason for this..?
Zephyr ICTCloud ArchitectCommented:
Still, might be an ISP routing issue, in this case AirTel so it seems ... Maybe try to contact the technical department of the provider?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
AWS

From novice to tech pro — start learning today.