From time to time (about 2 or 3 times a week) we get emails from Kinsta stating “We detected an error on your site” with a link to the Live environment log. Unfortunately there are many routine errors in the logs that I suspect are caused by hackers probing the site for vulnerabilities, so I’m unable to see why exactly we are getting these emails. The logs are just too noisy to see which error the Kinsta email is referring.
I don’t see any evidence that the site is not working properly by browsing it as a normal visitor and the log doesn’t provide enough information to replicate and troubleshoot the problem.
Is this normal to get these emails from Kinsta?
Can I tell the rest of the team that we don’t need to be so concerned about them?
Hi @dsmithrzf ! 
Welcome back to the Kinsta community.
Typically, notifications regarding error messages detected on the site while the site is not completely down simply mean that an HTTP 500 error code was detected in the site’s access logs. If you’re not sure where an error occurred on the site, you can contact our support team via chat and we can help take a look.
In many cases, this can be resolved by updating plugins (if necessary) or, if it’s caused by something such as a request to a WordPress file that shouldn’t be accessed directly (wp-settings.php for example), we can set a block in the server to block that file from external access, which will prevent triggering the error.
It’s not generally a good idea to ignore error notifications; instead, we recommend trying to locate the main cause of those notifications and work to eliminate that instead to cut down on false positives.
If you have any other questions as well, please let us know.
This is actually a pretty common situation with Kinsta, so you don’t need to panic. Those emails usually mean that a temporary HTTP 500 error was detected in your logs, not that your whole site went down. In many cases, these errors are triggered by bots or hackers scanning your site and trying to access files that shouldn’t be accessed directly, which creates a lot of noise in the logs.
If your website is working normally when you browse it, there’s a good chance these alerts are not affecting real users. However, it’s still not a good idea to completely ignore them. Even though many of the errors are harmless, some could point to plugin issues, outdated code, or misconfigurations that should be cleaned up.
What you can do is try to match the time of the email with entries in your logs to see what request caused the error. Updating your plugins, themes, and WordPress core can also help reduce these alerts. In some cases, blocking suspicious requests to sensitive files on the server can stop repeated errors from bots.
So you can tell your team that these alerts are fairly normal and not always critical, but they shouldn’t be dismissed entirely. It’s better to treat them as warning signals and investigate when possible to keep the site stable and secure.