My IP network is stuck in review (Bitcoin Core)

I've got a Bitcoin Core node running version v26.0.0. Lately, I've been checking my node status on bitnodes.io and it's been saying "Your IP network is currently pending review." for several days now. I've got (In: 44 / Out: 10) connections showing up. When I connect through internet provider A, everything checks out fine on bitnodes.io. But when I switch to internet provider B, it gives me that pending review message. Here’s the tracert I ran for internet provider B: tracert google.com Tracing route to google.com [142.250.70.142] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms [10.0.0.138] my router 2 23 ms 21 ms 20 ms 10.2.0.1 3 12 ms 14 ms 12 ms 59.154.38.153 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 54 ms 55 ms 49 ms hu0-2-1-0.33vspr01.optus.net.au [124.19.61.173] 9 50 ms 50 ms 51 ms 72.14.218.78 10 55 ms 51 ms 51 ms 142.250.234.131 11 56 ms 50 ms 55 ms 142.250.230.161 12 54 ms 51 ms 51 ms mel04s01-in-f14.1e100.net [142.250.70.142] Trace complete. I suspect the issue might be with that second hop, since the route from internet provider A doesn't go through a private address router like that. Any thoughts on what could be causing this with internet provider B?

Do you have a firewall at your router or your computer? Check if you've correctly portforwarded your port by going to canyouseeme.org and checking if port 8333 is reachable. If it is, then check what network your inbound peers are reaching you by looking at getnetworkinfo in your Bitcoin Core console/RPC.

I have 2 Internet providers, one works OK the other one says "Your IP network is currently pending review" everything is the same nothing is changes in the local network when it is swamped with the 2 Internet providers.

It's possible that the IP address range assigned by Internet provider B is flagged by bitnodes. io or other services due to previous activity or network behavior. This could result in your network being subject to additional scrutiny or review. If so, you need to contact Internet provider B's customer support.

This has to be one the dumbest pieces of advice I've read this year. Do you really think ISP B's customer support even know what a Bitcoin node is, let alone know about bitnodes? Most likely the customers of this ISP have their computers infected and being used for DDoS attacks. This is the only way I think could trigger a residential ISP's addresses to be reviewed for malicious activity.

Not an expert, but the private address 10.2.0.1 indicates that there might be a NAT device or private network within your ISP's infrastructure. Check canyouseeme.org as told by ranochigo and tell us what you see. According to what you've said, it should display "Error: I could not see your service on port 8333". Does it? You can enable incoming connections via Tor with -listenonion and completely bypass any such ISP or firewall limits. It will load in bitnodes.io as well.

This all of a sudden started to work a few days later I did send an email to bitnodes.io but got no reply, so it might have been coincidental that it started to work. Thanks to all those people that contributed.

Hello, can you tell me how you contacted bitnodes.io? I also have two ISPs and both are "pending review" with both ipv4 and v6, I have only ipv6 public. Thank you!

I'm not the OP but: Bitnode's contact information is in the bottom (number 10) of their Terms of Service, here: bitnodes.io/tos/ Or contact the owner's email in GitHub: github.com/ayeowch OP's last login was on March 29 after the issue was solved so he might not login again to see your post.