Skip to content

← All news

Two new monitors: WebSockets and domain blocklists

The two newest monitor types watch for failures that every other check on a site stays green through.

WebSocket

Your chat, your live dashboard, your price feed and your game lobby are WebSockets, and they fail while the page loads, the API answers, the certificate is good and the port is open. The socket never opens, or it opens and closes again a moment later, and to a user that is a screen that quietly stops updating.

An HTTPS monitor cannot stand in for this. A WebSocket starts as an HTTP request that asks to upgrade, and a server that answers a plain request with an error is behaving correctly, so an HTTPS monitor would report a healthy server as down.

  • It completes the upgrade handshake.
  • It keeps the socket for a moment to see that it stays open.
  • If you give it an expected message, and optionally something to send first, a feed that is connected but has stopped publishing is a failure instead of a green row.

Domain blocklists

Your site can be up from every continent, with DNS and the certificate fine, and still reach nobody who runs a pi-hole, AdGuard Home, NextDNS or a router with ad blocking on, because your name is on a list those resolvers load every night. Your logs show fewer requests rather than blocked ones, so nothing you own can tell you.

The monitor checks your domain against the lists those resolvers use. Each list is fetched once a day for everybody who watches a domain, and your name is looked up in the file we already hold, so a listing reaches you the next morning instead of through a customer who could not get in. It does not choose the lists for you, on purpose: every list added is another source of a listing you can do nothing about.

Both are on the plans that include every monitor type. The free plan has websites, DNS, TCP and ping.

Read more