Once you have those in place, there is little more you can do to help. There might be some marginal benefits in connecting with more peers at the cost of higher resources usage, especially bandwidth. Under normal circumstances, the default peers count from your clients should be good. Monitoring Internet quality with tools like those from pingman can help pinpoint the cause of some of these missed attestations if... Source: over 1 year ago

I'm attempting to use PingPlotter to find the problem but I'm fairly new with it - The Packet Loss is occurring on IP 192.168.1.1 while testing 8.8.8.8, pingman.com, google.com, akamai.com however it does not show any PL for www.google.com. Source: over 2 years 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