Blocked Access but not my IP

[SleeplessinDC]

I tried to go to a page in my blog and got the following message. It refers to an IP address that isn't mine! I looked it up and it is in the Netherlands. How is this happening?

Access has been blocked.

Your IP [62.212.66.99] is registered in the Stop Forum Spam or Project Honey Pot database.
If you feel this is incorrect please contact them

Protected by: AVH First Defense Against Spam

[Peter]

Can you do a test for me,

go to http://blog.avirtualhome.com/avhfdas-test.php
and let me know what IP address shows up.

Thanks in advance.

[Peter]

What site did you visited when this happened? And does it happen everytime you visit this site?

[cetaylor]

I also have the same problem.  This afternoon my blog started refusing me access, citing a blacklisted IP that was not my own.  But I have partially figured out what is going on.  AVH First Defense Against Spam is including my local whitelist as if it were part of the blacklist.

My own IP is specifically cited in the local whitelist (it is actually the only item on the local whitelist at all).  When I disable the AVH local whitelist, I am no longer blocked and can access the site normally.  If I enable the whitelist, then I get the "Your IP has been blocked" message.

Something is happening in the caching, I suspect.  Here are the current stats:

12937   Total of IP's in the cache      
12794   Total of IP's classified as clean      
143       Total of IP's classified as spam

IPs remain the cache for 7 days.

[Peter]

Thanks for the extra info, I'll look into it.

[cetaylor]

One extra data point for you.  Not long after I posted that last message, I started getting the same error even with the whitelist disabled.  I disabled the entire plugin and still got the error, which is when I started wondering whether it might be simply WP SuperCache serving up bad old static data.  I purged WP SuperCache's cache too (don't want to be served up old pages with that error), and then re-enabled AVH First Defense.

At this point I don't know if it was truly AVH causing the issue or another sort of caching error involving WP SuperCache, but right now AVH is enabled (with APIs + local white/blacklists enabled, too) and WP SuperCache is active too.  And the error is gone.