BitterPing monitors HTTP/HTTPS URLs, health checks, and heartbeat-style endpoints, then emails you when they go down or recover.
See setup pathBitterPing monitors the URLs you care about and alerts you by email when they stop responding. You configure the check interval — from every minute to every hour — and BitterPing handles the rest. When a monitored endpoint goes down, you get an alert within one sweep cycle. When it recovers, you get another alert so you know the issue is resolved.
Every check records the HTTP status code and response time, giving you a historical view of your infrastructure's reliability. The dashboard shows uptime percentages and recent incidents at a glance, so you always know where you stand.
BitterPing is built for operators who need reliable monitoring without the complexity of enterprise observability platforms. No agents to install, no YAML to write, no dashboards to configure. Add a URL, pick an interval, and you are monitored. Alerts go through BitterPost for reliable email delivery.
In the Atlas operating model, BitterPing is heartbeat evidence for configured endpoints. It answers whether the URL you asked it to watch is responding now, when that changed, and what alert was sent.
HTTP reachability, response status, response time, state transitions, and down/recovery alert delivery for each monitor.
BitterPing does not replace BitterGrid deploy verification and does not prove full user workflows. Grid deploy truth and repo QA smoke remain separate evidence.
Enter a URL and choose a check interval. BitterPing starts checking immediately.
Email notification when a site goes down — and again when it comes back.
Uptime percentage, response times, and incident history in one dashboard.
Use a public site URL, API health check, or heartbeat-style URL that should return before the 10-second timeout.
Choose 1, 5, 10, 30, or 60 minute checks based on the service's operational importance.
Down and recovery emails are sent to the account contact through the BitterPost delivery path.
Pair BitterPing with deploy records and repo QA when you need release proof or workflow proof, not just endpoint heartbeat evidence.
Any public HTTP or HTTPS URL that can be checked with a HEAD request, including websites, API health checks, and heartbeat-style status endpoints.
Alerts are sent via email through BitterPost, our webhook-to-email relay. You receive one email when a monitor goes down and another when it recovers. No spam — just the events that matter.
HTTP 500 or higher, connection errors, and timeouts are treated as failures. When a failing monitor returns below 500 on a later check, it is marked as recovered.
No. BitterGrid proves build, release, deploy, and runtime health for a service. BitterPing watches the URLs you configure after they are reachable.
No. Use repo QA smoke tests for behavior proof. BitterPing is the operational heartbeat that tells you whether a monitored endpoint is currently responding.