HTTP Status Monitoring
Verifies every endpoint returns the expected HTTP status code on every check. Catching a sudden 500 or 404 in seconds — not hours — is the difference between a quick fix and a support firestorm.
Always-on endpoint monitoring
Know before your users do.
PulseQuay watches your endpoints around the clock — HTTP status, TLS health, certificate expiry, and content integrity — so you catch problems the moment they happen, not when a customer calls.
Everything your stack needs monitored
Every check type runs on a configurable schedule — as often as every 60 seconds. Here is what PulseQuay watches and why it matters.
TLS Certificate Validity
Confirms your certificate chain is valid and trusted before each check completes. A broken TLS handshake silently blocks every HTTPS visitor; automated checks catch it before it cascades.
Certificate Expiry Alerts
Tracks the days remaining on your TLS certificates and fires an alert at a configurable threshold. Expired certs kill conversion; a timely warning lets you renew on your schedule, not in a panic.
Body Content Verification
Checks that the response body contains an expected string — confirming real content is served, not a 200 OK from a cached error page. Critical for detecting silent regressions that status codes alone will never reveal.
Regex Pattern Matching
Validates response bodies against a regular expression for fine-grained content checks. Useful for dynamic pages where exact string matching is too fragile to maintain.
DNS & TCP Connectivity
Resolves the domain and opens a TCP connection before attempting HTTP, isolating network-level failures from application errors. DNS misconfiguration is one of the most common causes of silent downtime.
Latency Tracking
Records round-trip response time on every check and surfaces trends in your history. Rising latency is an early warning of capacity problems — act before it becomes an outage.
Multi-Checker Distribution
Route checks through multiple checker agents in different networks or regions. True availability measurement requires observing your service from more than one vantage point.
Self-hosted checkers
Run checks from wherever you need
PulseQuay supports two checker modes. A pull checker is a lightweight Docker container you expose on a URL — PulseQuay dispatches signed check tasks to it and reads the result. A push checker runs entirely outbound — it fetches its target list from PulseQuay on a schedule and pushes results back, with no open port or inbound firewall rule required.
Check your internal network
Public checkers can only reach public URLs. A checker deployed inside your VPC or office network can monitor internal APIs, staging environments, and services that are intentionally not exposed to the internet — all from the same PulseQuay dashboard.
Control the vantage point
Latency and availability look different depending on where the request originates. Place a checker in the same region as your users — or your database — and get measurements that actually reflect their experience, not a generic cloud location.
You own the infrastructure
Outbound traffic stays on your machine. The checker never receives your credentials — it only receives signed check tasks and reports results back. Register it in the UI in under a minute, paste the generated secret, and the checker is live.
Push mode — no open ports
A push checker initiates every connection itself. It fetches its target list from PulseQuay on a configurable interval and pushes check results back — making it ideal for firewalled networks, NAT environments, or anywhere inbound connections are not practical.
Simple, transparent pricing
Credits are reserved per target based on how often it is checked. Faster checks cost more credits; slower checks stretch your plan further.