Interesting, I didn't know traceroute used UDP by default. Just did some testing with the best traceroute tool, mtr[0], and using the -u flag for UDP seemed to give the worst results. -t for TCP seemed OK. I never thought about the difference between how TCP and ICMP packets are handled. [0] https://bitwizard.nl/mtr/. - Source: Hacker News / 6 months ago

It's possible what you had was 2 devices transmitting packets at the same time resulting in a collision Given that you were doing a slowloris attack I would consider this success (or failure) in other words the attack worked. Here are a few other things you might find useful. Source: over 1 year ago

A VPN is good because it is encrypted and hard to find your IP. Even a router will use DHCP and change your IP but if the router is in your own home that is a dead giveaway. This and other tools like that can help to see all the relay points (collision domains) in the route. Source: over 1 year ago

You might narrow it down by using traceroute How the ISP chooses to identify their collision domains is entirely up to the ISP. If you get lucky maybe the wifi name is "Jones family 123 main st" or something to connect the IP to a person. Source: over 1 year ago

Is this a localhost api or remote? You could test using this or this to see if the network is the problem. You can test the database from the command line as well. Source: over 1 year ago

Good place to learn another another good place but somewhat advanced this tutorial trace that website and the http protocol. Source: over 1 year ago