It might be your IP. It might not be your devices.
Many ISPs block or limit incoming connections to residential IPs. The ISP doesn't want home users standing up services that might end up with high volumes of incoming traffic. They might route the incoming traffic to their own services instead. So, in these cases, although the traffic is sent to the IP assigned to your home, the connection is not to your home.
Some ISPs in the past have even set up fake or deceptive P2P nodes so that when people try to connect to residential IPs, they connect to the ISP so that the ISP can collect data and punish the "pirates". So, these IPs end up on abuse lists and open lists of available IP to connect to because the ISP wants them advertised.
It might be your devices
I consider it unlikely that an entire swath of an ISP has open proxies on their residential customer's networks, but it would not be out of the question if there is a common vulnerability in the ISP's routers.
If this is the case, then the proxy would more likely be on the router and not on devices within the customer's networks.
One more step
So, while you have done a lot of investigation into these IPs, you need to go just one step further. You need to see if your router is seeing the traffic.
- connect to
<neighbor IP>:8080 from your IP and check that router's logs for the traffic
- if you try to connect to your own IP from inside your own network, you might get inconclusive results
- check the router for any proxy settings or services set up on port 8080 or port forwarding to that port
- check the traffic within your network with a packet capture tool, like Wireshark, to look for proxy traffic on that port
- try to scan the IP with a network scanner to learn more about it
- you might see different hardware/device results on different ports on the same IP, which will be an indication that traffic to different ports are going to different destinations
- factory reset the router and try to connect
This data gathering will help you narrow down what is actually going on.