It’s most likely not a coincidence. 🙂
The number of blocked log in attempts recorded by the Protect module is incremented every time the module blocks a new IP after repeated failed login attempts, either via your site’s XML-RPC file or via the log in form.
That number is consequently different for each site, as the attempts will obviously be different for each site.
That said, there are 2 situations when that number may be similar for different sites:
- Coincidence: a bot may be targeting all your sites at the same time, thus incrementing the numbers at the same pace. That said, it would have to be a really big coincidence, as other bots would hit the sites as well and increment the numbers differently.
- Multisite: when Protect is enabled on one of the sites of your network, it’s enabled on all of them, and protects each one of your sites in the same way. If an IP is blocked on one site, it’s blocked on all of them. It’s important for Protect to treat each one of the sites in a multisite network as one entity, since gaining access to your superadmin account would give a hacker access to all the sites in the network. So when using Protect in a Multisite network, all Protect numbers for each site will be the same.
I hope this clarifies things a bit!
If, however, those 8 sites are not part of the same Multisite network, I would need to take a closer look at them to find out more. Could you post the URLs here?
If you want them to remain private, you can also contact us via this contact form:
http://jetpack.com/contact-support/
