Operations | Monitoring | ITSM | DevOps | Cloud

An escalation protocol is the written rule set that says when an incident moves from the person holding it to the next level, who that next level is, how they get contacted and how long they have to respond. It sits underneath the escalation policy (the why) and above the contact matrix (the who), and it is the document the on-call engineer actually reads at 3 AM.

ICMP has no port number. It is an IP-layer protocol, number 1 in the IP header, that sits beside TCP and UDP rather than on top of them, so ping does not use a port and there is no "ping port" to open. When a firewall form asks for one, select the ICMP protocol and the echo request type instead. This post covers where ICMP sits in the stack, which types and codes you will actually meet, how to allow it through Linux, Windows and cloud firewalls, and when a ping check is the wrong check.

The best SSL certificate monitoring tools are Hyperping (certificate checks inside a full uptime, on-call and status page workflow), TrackSSL (dedicated certificate inventory and change alerts), Xitoring (deepest published TLS analysis at the lowest price), UptimeRobot (largest free tier), Better Stack (certificate checks alongside logs, traces and incident response) and Oh Dear (whole-site health for agencies). I analyzed 26 tools and narrowed the list to these six.

Updated August 05, 2026 Keyword monitoring checks that a specific string is still present in a page or API response on every run, instead of trusting the HTTP status code. It catches the failures that uptime checks sleep through: a deploy that renders an empty template, a CMS entry someone unpublished, a checkout page serving "Something went wrong" with a perfectly healthy 200. In Hyperping, the simple version is a text body assertion on an HTTP monitor and takes about ten seconds to set up.