Setting up service web checks - HTTP and TCP

You can monitor remote public services via HTTP and TCP. This allows you to see if the URL or IP is responding to requests as you'd expect, and within the expected response time. Checks are performed every 5 minutes.

You should also review our best practices for service check alerts.

Check types

You can choose different check types depending on what kind of request you want to test:

  • HTTP
    This issues an HTTP request (GET, POST, DELETE or PUT) on port 80 or 443 (depending on whether you use an HTTP or HTTPS URL) and expects a web server to respond. It replicates a user browsing to the URL so measures full page load time. It can include custom headers and HTTP basic auth, as well as a body of content to send.

  • TCP
    This opens a TCP socket on the specified port to check that a connection can be established and content read from the socket. A custom string can be sent with the connection prior to the read operation.

Adding a web check

  1. Click the Services icon on the left then click the + Service button in the top right.


  2. Give the check a name, choose whether you want it to be checked over HTTP or TCP, select the IP version to use (we support both IPv4 and IPv6), add the URL and then finally select the locations you want to monitor from.


  3. Click the Save button and after a few minutes the check will start executing.
  4. Click to view the check map and then click the Alerting tab to add alerts for the check e.g. response time or status is down. See also best practices for service check alerts. Note that we automatically add two alerts for services created via the UI, as can be seen below. These alerts are NOT automatically added for services created via the API.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Monday  —  Friday.

10am  —  6pm UK.

Dedicated Support.