TCP and UDP port checks
Monitor public socket services without HTTP-specific settings.
1 min readThis guide covers Premium features. Premium is in early access and cannot be bought yet.
Choose a protocol when adding
TCP and UDP monitors watch a public host and port. A monitor’s kind is fixed when added: changing an HTTP monitor into a port monitor requires adding a new monitor.
Port checks require Premium and do not carry HTTP headers, response keywords, or certificate settings. Private-network destinations remain unavailable.
Choose what a UDP check proves
A UDP check can send a payload and require a reply. A reply requirement is useful for a protocol that answers the payload you provide.
Without requiring a reply, silence by itself does not prove that a service is responding. Read the UDP settings’ explanation and use a protocol-appropriate payload before relying on the result.
Review the result
Open the monitor’s details for socket results and response history. Failures and recoveries use the same confirmation policy as HTTP monitors: a second check after 30 seconds before changing incident state.