UptimeBot will send alerts about a failed check to the dedicated Slack channel. So any issues with your website will be immediately visible to the members of that Slack channel.
A good idea would be to setup a separate channel for UptimeBot alerts, something like #project-name-downtime, and add several technical engineers there, who would be responsible for resolving any issues that may come up.
UptimeBot uses a distributed monitoring system to minimize false-positives.
Every time downtime is detected, subsequent requests are sent from remote servers located in different countries/continents to make sure that the problem exists.
Thus UptimeBot reports that your site is down in case the problem is confirmed by at least two separate monitoring servers.
Here is the example of how the downtime alert notification looks like:
The first alert is posted immediately as the incident is detected.
In case the incident is open for a long time and nobody has confirmed to be resolving it, UptimeBot will send follow-up alerts.
The second alert will be posted in 5 minutes, the third in half an hour since the opening of the incident.
Second and third alerts will include a channel wide mention to make sure that incident is visible:
Do you hit a snag with UptimeBot?
Don't hesitate to contact us.