Run checks every 30 seconds, 1 minute, 5 minutes, or up to 24 hours. Pick the cadence that fits your SLA requirements.
Expect any HTTP status code — not just 200. Define multiple accepted codes for redirects, paywalls, or maintenance pages.
GET, POST, PUT, PATCH, DELETE. Send a custom request body and headers to test authenticated endpoints and REST APIs.
Optionally follow HTTP redirects to the final destination, or flag a redirect as a failure if you need to catch unexpected 3xx responses.
Set a response time threshold in milliseconds. Beacony creates a "slow response" incident when your endpoint exceeds it — even if it returns 200.
Beacony requires consecutive failures before opening an incident. No false alerts from a single flaky check — configurable confirmation count.
For each HTTP/HTTPS check, Beacony records the full result — not just up or down. 90 days of response time and availability data are stored and visible in your dashboard and on your public status page.
90 days of response time and availability data, available in your dashboard and on your public status page.
Beacony requires consecutive failures before opening an incident — eliminating false positives from transient blips. Once confirmed, your alert arrives via email, Slack, webhook, or PagerDuty in under 60 seconds.
Yes. You can set custom request headers (including Authorization: Bearer tokens or API keys) and a request body. Beacony supports GET, POST, PUT, PATCH, and DELETE methods for REST and GraphQL APIs.
Use a keyword monitor alongside your HTTP check. Keyword monitoring scans the response body for a word or phrase, catching broken deployments that serve error content with a 200 status code.
Yes. Beacony fully supports HTTPS and validates the SSL certificate as part of each check. If the cert is expired or invalid, the monitor is marked DOWN immediately. You can also add a dedicated SSL certificate expiry monitor for advance warnings at 30, 14, 7, and 1 day.