UpDownTracker
Monitoring network
Why you may see our requests
UpDownTracker customers configure checks of individual public websites and APIs. Separate probe nodes make those requests. Scheduled Standard checks start at five-minute intervals; manual checks and optional website-health observations can add requests.
Current traffic
Standard HTTP/HTTPS checks observe availability, expected text or static tracking code. Redirects are bounded and each destination is revalidated. HTTPS certificate observations make a TLS connection without an HTTP User-Agent. Active Tracking uses an isolated Chromium browser with bounded egress; a page can load resources from other public domains.
Traffic identity and source addresses
Standard requests carry an UpDownTracker/1.0 User-Agent with this page and the traffic class. Active Tracking keeps a Chromium-compatible User-Agent with an identifiable UpDownTracker token. The token contains no customer or monitor ID. Public source IPs appear only for explicitly published active or draining nodes; the registry may currently be empty. Check the current feed before allowlisting an address.
Limits and reports
The service is intended for authorized individual targets. IP and port-range scanning, vulnerability scanning, brute force and exploitation are prohibited. TCP, ICMP and general DNS monitor products are not active. If traffic is unwanted, report it; we can suspend a monitor, account or destination while investigating.