Skip to content

Wrong routing rules in data center

0

Dear community, Pls advice how it possible to resolve routing issue. i hide sensitive information. compare 7-8-9 hops. time extremely increased in my case. Thanks in advance! my routing:

7 35 ms 36 ms 35 ms 101.203.88.52 8 * * * Request timed out. 9 135 ms 139 ms 128 ms 150.222.90.13 10 * * * Request timed out. 11 154 ms * 148 ms 15.230.160.13 12 * 151 ms 152 ms 52.95.31.219 13 147 ms 128 ms 134 ms 52.95.31.208 14 144 ms 134 ms * 15.230.129.3 15 * 136 ms 129 ms 15.230.154.157 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out.

healthy person routing:

4 25 ms 25 ms 25 ms 101.203.89.105 5 31 ms 32 ms 31 ms 101.203.89.180 6 34 ms 33 ms 33 ms 52.93.251.189 7 27 ms 29 ms 26 ms 52.93.66.63 8 * * * Request timed out. 9 27 ms 27 ms 27 ms 15.230.161.51 10 33 ms 32 ms 33 ms 52.93.72.242 11 32 ms 35 ms 33 ms 52.93.72.253 12 38 ms 35 ms 32 ms 15.230.129.45 13 27 ms 27 ms 28 ms 15.230.154.193 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out.

1 Answer
0

Looking at the IP addresses, the 52.93.x.x and 52.95.x.x addresses belong to Amazon, but the 15.230.x.x addresses belong to another provider. It would appear the whatever application is hosted in AWS is redirection traffic (somehow) to another provider.

It's not clear what you're trying to do here, what the application is or what the intended end result is. More detail is required to assist - just looking at the latency numbers isn't enough without know what is happening under the hood.

AWS
EXPERT
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.