Can you guess what went wrong?
```
ping ec2.app-in-mum-49
```
Here is what I get:
PING ec2.app-in-mum-49 (23. xx. xxx .xxx) 56(84) bytes of data.
From 10.204.35.30 (10.204.35.30) icmp_seq=6 Time to live exceeded
From 10.204.35.30 (10.204.35.30) icmp_seq=6 Time to live exceeded
....
..
@nixCraft mtu issue. Pmtu blocked by some firewall.
@nixCraft I don’t think I’ve ever seen a route that actually exceeds 255 hops. So… routing loop?
@nixCraft is it a loop somewhere?

@nixCraft was the TTL too low from the beginning? (I remember the default to 1 times in the Intranet)

Then I had a SBC or router manipulating it to 1

And also funny: the default gw Magic
Default gw on switch1 is switch2 and
Default gw on switch2 is switch1.
(Can be extended to more switches of course)

@nixCraft Routing loop I'd assume? "mtr" up next?
@nixCraft
That's a routing loop. Your time to live (TTL) is being decreased until one router in the path sends a time out back to you.
@nixCraft DNS resolves OK; the echo responses are a duplicate (icmp_seq=6) – link level failure. Another host has the same IP? ARP table scrambled?
@nixCraft yamraj is coming to take you... it was nice knowing you.