Yes, that is probably a temporary issue with the API server, we decided to include a new option to allow the users to integrate the plugin event monitor to your own SIEM so if the communication with the Sucuri API server fails the logs are still saved in your own system; this is going to be available in the next version from a new panel in the settings named “Log Explorer”, you can previous with the development archive [1].
And I am discussion with the Sucuri development team to see if it is a good idea to add another feature to allow the decentralization of the API calls, so you can add a self-hosted service or send the logs elsewhere. This helps in cases where the admin of the website is concerned about the privacy of the data that is being sent to Sucuri, or in case that we shutdown the API server you can still use the plugin without the need to modify the code.
Not saying that Sucuri is going to shutdown that API, but the idea to decentralize the API calls sounds good to me. It is still a proposal and I am reviewing this with my team, so is not going to happen soon.
[1] https://downloads.wordpress.org/plugin/sucuri-scanner.zip
Thank you.
I’ve even wrote a plugin to keep track of your work:
https://wordpress.org/plugins/svn-updater/
And I’m subscribed to Sucuri Scanner’s development log by RSS.
Marking as resolved; by the way, we moved our development to GitHub [1] so your “SVN Updater” plugin will stop download the bleeding edge changes, you may want to point it to the new repository if you want to continue receiving the development updates or keep it pointed to the subversion repository for the stable changes.
Again, thanks for your help so far.
[1] https://github.com/Sucuri/sucuri-wordpress-plugin