Home > Uncategorized > Temporally problems with APNIC IP allocations

Temporally problems with APNIC IP allocations

September 30th, 2012 Leave a comment Go to comments

Hey guys…we received a report that we are missing some IP ranges from APNIC allocations, especially from the New Zealand (NZ) . We will check this out and see why we are missing those ranges as we automatically parse APNIC official database files. Anyway, thanks for the report and your feedback Dave W. – we will definitely sort this problem out shortly!

Categories: Uncategorized Tags:
  1. October 14th, 2012 at 14:43 | #1

    You are also missing some assignments for China – I have a block in place that is missing 60.29.0.2, which is assigned to CNC group in China but is not in the china IP listing.

  2. Ipdeny
    October 23rd, 2012 at 09:09 | #2

    David – we pull all data from APNIC regarding China IP allocations. It looks like they are missing it…… Thanks for the report!

  3. November 2nd, 2012 at 14:05 | #3

    I recently updated and instead of over 20,000 blocks in my country list from two months ago, I now have only around 6,000.

    What happened?

  4. December 17th, 2012 at 05:00 | #4

    Hi we are getting a lot of spammers from Vietnam on our forum and have started using IP Deny data to filter them at registration time but none of them seem to be filtered – the latest one is 123.27.232.110. A quick google (http://projecthoneypot.net/ip_123.27.232.110) identifies this as a Vietnamese IP address but I don’t see a matching range in your Vietnam data. No disrespect intended but so far IP Deny simply hasn’t worked for us.

    Ian

  5. Jeremy
    June 6th, 2013 at 10:55 | #5

    I am finding other addresses that aren’t right: 101.119.18.13 is AU but shows up no where. 144.132.53.118 is AU. I can find others but something isn’t right here.

  6. David
    April 24th, 2014 at 12:42 | #6

    The US file is missing 192.159.67.0/24 and maybe more

  7. Ipdeny
    August 10th, 2014 at 23:35 | #7

    ARIN ip block generation has been fully fixed. Sorry for the delay!