Sometimes you may end up in a situation where Freshping sends out a downtime alert but when you check by yourself, your site is up and running. You might think that it is a false alert.
No, not all of these are false alerts.
There are many reasons which might have caused this, here’s what we see happening with few of our customers.
- Micro downtimes: Sometimes your site might have been down for few seconds, by the time you receive alert and verify, your service might be already up. This could be because of many reasons. Example: Shared infrastructure, micro downtime on provider side, Application pool getting recycled on the server (during some lean hours) everyday at the same time.
- SSL Errors: many a times we have also seen our customer's configured SSL certificate work in chrome browser but not in all browsers.
Beyond all this before alerting you additional steps that we take to confirm downtime:
Extra confirmation when your site is down or responding slowly: Freshping pings your site for every one minute, once pinged Freshping waits for site response, if the site is slow i.e takes more time than industry standards(more than 10seconds) to load, Freshping then polls your site from a second (backup) test location. We do this backup location testing to ensure if the issue is with your website or any network issue between your website & the first location. Only when the second location also confirms downtime, we send you a down alert.
Exact error message when your site reports errors: We log your actual error reported by your site as ssl error, 5xx error, 4xx error & this is not a false alert. This is what your server had responded back with. When you see one of these error messages you can be rest assured that it's an actual downtime.
If you still think, beyond all this, your alert is a false one, we take false alert very seriously, email us at firstname.lastname@example.org with your false-alert email copy & we will look into our logs & tell you what exactly happened.