traceroute ends with two different public host IPs

Hello... can someone explain this traceroute? I understand the multiple hops along the path but do not understand how the trace ends with two completely different host public IPs.
I searched the Internet but either my search parameters are wrong or there's no relevant info available.
Any help greatly appreciated.
Thanks.

  4 65.19.113.249 [AS 6128] 4 msec 4 msec 4 msec
  5 64.15.0.109 [AS 6128] 20 msec
    64.15.0.33 [AS 6128] 20 msec
    64.15.0.109 [AS 6128] 20 msec
  6 64.15.3.150 [AS 6128] 12 msec 16 msec 16 msec
  7 213.248.68.33 [AS 6128] 32 msec 20 msec 24 msec
  8 213.155.130.2 [AS 6128] 20 msec 24 msec 20 msec
  9 213.155.134.133 [AS 6128] [MPLS: Label 349248 Exp 0] 36 msec
    213.155.137.23 [AS 6128] 44 msec 48 msec
 10 62.115.13.114 [AS 6128] 56 msec
    80.91.251.29 [AS 6128] [MPLS: Label 646865 Exp 0] 48 msec *
 11 200.230.220.5 [AS 6128] [MPLS: Label 16020 Exp 0] 160 msec
    80.91.246.186 [AS 6128] 48 msec
    200.230.220.5 [AS 6128] [MPLS: Label 16020 Exp 0] 168 msec
 12 62.115.13.114 [AS 6128] 60 msec
    200.230.158.25 [AS 6128] [MPLS: Label 16061 Exp 0] 156 msec 156 msec
 13 200.230.220.5 [AS 6128] [MPLS: Label 16020 Exp 0] 164 msec
    200.230.242.49 [AS 6128] 156 msec
    200.230.220.5 [AS 6128] [MPLS: Label 16020 Exp 0] 160 msec
 14 200.230.158.25 [AS 6128] [MPLS: Label 16061 Exp 0] 156 msec 164 msec
    201.90.13.74 [AS 6128] 160 msec
 15 189.16.122.245 [AS 6128] 168 msec *
    200.230.242.49 [AS 6128] 156 msec
cavacamiteAsked:
Who is Participating?
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.

rharland2009Commented:
What is the hostname you're performing the traceroute against?
0
cavacamiteAuthor Commented:
I'm tracing IP 189.16.122.245.
Thanks.
0
cavacamiteAuthor Commented:
Please note IP 200.230.242.49 does not exist anywhere on the network, nor does any ip in that range. Thanks.
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

rharland2009Commented:
Those are IP addresses from the public IPs that exist on the routers that your MPLS pipes traverse.
0
cavacamiteAuthor Commented:
Ok but my host IP 189.16.122.245 is one hop away from the MPLS edge router towards my network.
Carrier router outside 201.90.13.74 <> Carrier router inside 189.16.122.241 <> DMZ Switch 189.16.122.245.

In the traceroute 200.230.242.49 is one route in the 13th hop. Why does it show up again as the destination?
0
rharland2009Commented:
Not positive on that. I think it may have something to do with the encapsulation of the MPLS pipe and the TTL and other info being forwarded on, but I would check with Cisco on that (looks like a Cisco box to me).
0

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
cavacamiteAuthor Commented:
Ok thanks for your input. I will look into it. Not a production issue so a little low on the priority list.
0
rharland2009Commented:
No problem. Encapsulation can do strange things to TTLs.
0
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
Network Management

From novice to tech pro — start learning today.