Bitcoin Forum
May 15, 2024, 01:48:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Technical Support / Re: Your IP network is currently pending review. ( Bitcoin Core ) on: March 29, 2024, 02:44:55 AM
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.
2  Bitcoin / Bitcoin Technical Support / Re: Your IP network is currently pending review. ( Bitcoin Core ) on: March 12, 2024, 06:49:32 AM
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.
3  Bitcoin / Bitcoin Technical Support / Your IP network is currently pending review. ( Bitcoin Core ) on: March 11, 2024, 10:36:18 AM
I have a Bitcoin Core version v26.0.0 node installed.
I am using bitnodes.io to check my node and am getting "Your IP network is currently pending review." for days
I have (In: 44 / Out: 10) connections shown on

When I use internet provider A bitnodes.io verify it OK
When I use internet provider B bitnodes.io says "Your IP network is currently pending review."

internet provider B tracert is

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 think the 2nd hop is the problem as internet provider A path does not go through a private address router.
  2    23 ms    21 ms    20 ms  10.2.0.1
  
Any ideas as to why this is not working with internet provider B
  
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!