Not being able to load amiga.org from home?

[GreggBz]

Being a sys admin at a local ISP I am OHH so familar with this problem.
You see, ARIN just released the 72.0.0.0/8 netblock amongst others that have long been reserved, held, by ARIN.

Unfortunately, these subnets particularly 72.0.0.0/8 are still apearing on several stale bogon lists. I'd ask you guys if your ISP just switched over to a new ip range, if so then I'd say that's the problem. See what your IP adress is, punch it into www.networksolutions.com - the whois page, and that should give you the range your isp uses.. Amiga.org might then look at it's hosting company and see what their BOGON list looks like.

[GreggBz]

Following is a successfull tracert to www.amiga.org (68.90.68.66)

  4     5 ms     5 ms     5 ms  0.so-1-1-0.XL1.PHL1.ALTER.NET [152.63.39.122]
  5     9 ms     9 ms     9 ms  0.so-6-0-0.XL1.DCA5.ALTER.NET [152.63.38.149]
  6     9 ms     9 ms     9 ms  0.so-6-0-0.BR1.DCA5.ALTER.NET [152.63.43.169]
  7    10 ms    10 ms    10 ms  204.255.168.14
  8    11 ms    11 ms    11 ms  sl-bb23-rly-6-0.sprintlink.net [144.232.20.151]
  9    11 ms    11 ms    11 ms  sl-bb21-rly-9-0.sprintlink.net [144.232.14.133]
 10    25 ms    24 ms    25 ms  sl-bb21-atl-6-0.sprintlink.net [144.232.20.176]
 11    25 ms    25 ms    25 ms  sl-bb24-atl-9-0.sprintlink.net [144.232.12.30]
 12    25 ms    26 ms    26 ms  sl-bb25-atl-15-0.sprintlink.net [144.232.12.10]
 13    43 ms    43 ms    43 ms  sl-bb22-fw-15-0.sprintlink.net [144.232.8.21]
 14    45 ms    45 ms    45 ms  sl-bb27-fw-12-0.sprintlink.net [144.232.11.33]
 15    43 ms    43 ms    43 ms  sl-st20-dal-1-0.sprintlink.net [144.232.9.136]
 16    46 ms    46 ms    46 ms  sl-sbcint-3-0.sprintlink.net [144.228.250.110]
 17    46 ms    46 ms    46 ms  ex2-p2-0.eqdltx.sbcglobal.net [151.164.242.42]
 18    47 ms    47 ms    47 ms  bb2-p12-0.dllstx.sbcglobal.net [151.164.42.18]
 19    46 ms    45 ms    46 ms  bb1-p9-0.dllstx.sbcglobal.net [151.164.40.205]
 20    60 ms    60 ms    59 ms  bb1-p3-0.stlsmo.sbcglobal.net [151.164.189.33]
 21    61 ms    61 ms    61 ms  ded3-ge7-3-0.stlsmo.sbcglobal.net [151.164.14.253]
 22    60 ms    60 ms    60 ms  Southwest-Executive-Personal-Computers-1058478.cust-rtr.swbell.net [64.218.64.126]
 23    63 ms    63 ms    63 ms  cpanel1.betterbox.net [68.90.68.66]

Users that are unable to access the site might try:
tracert 68.90.68.66 - see where it dies. Assuming you are coming from a geographically simalar location, find out what the next hop should be by compairing to the above. The IP of  that next hop, would indicate the troublemaker.

Well.. after that, you would need to get in touch with the admin for that router/firewall. Your ISP's subnet is probabbly blocked there. Of course, getting in touch with that person might be a hurdle, whois information these days is not allways good. Secondly, admins for major internet routers tend not to respond to single end user complaints. But if your ISP calls - they might respond to that!