Uptime monitoring

Know when a site stops answering.

BitterPing checks the URLs you choose and emails you when one goes down—and when it comes back. It works with public websites, API health checks, and heartbeat endpoints.

Ask for access See exactly what it checks
Checks
Every 1–60 minutes
Alerts
One email down, one on recovery
History
Status code and response time

How it works

Small monitoring, on purpose.

BitterPing does not install an agent or ask you to configure an observability stack. It makes a scheduled request, records the result, and sends an email only when the state changes.

01

Add a URL

Choose a public website, API health check, or heartbeat endpoint and set its interval.

02

Let it run

Each check records the HTTP status and response time. A timeout, connection error, or 500-level response counts as down.

03

Hear about changes

You receive one email when the endpoint goes down and another when a later check confirms recovery.

Plans

Start with the URLs that matter.

Every plan includes one-minute checks, email alerts, and recorded check history. The only practical difference is how many endpoints you can watch.

Starter $9/mo Up to 5 monitors
Pro $29/mo Up to 50 monitors
Enterprise $99/mo Up to 500 monitors

Access is currently set up with us, so there is a person on the other side if the endpoint or alert path needs a closer look.

Ask for access

The boundary

A heartbeat is useful. It is not the whole diagnosis.

A successful check means the URL answered. It does not prove that every page, purchase, background job, or third-party integration is working.

What BitterPing knows

Whether the configured URL answered, how long it took, what status it returned, and when that state changed.

What it does not know

Why a service failed or whether a complete user workflow still works. Those require logs and product-level tests.

Questions

Before you point it at production.

What can BitterPing monitor?

Any public HTTP or HTTPS URL that responds to a HEAD request, including websites, API health checks, and heartbeat-style status endpoints.

When is an endpoint considered down?

A 500-level response, connection error, or ten-second timeout is treated as a failure. A later response below 500 marks it as recovered.

Will it keep emailing while a site is down?

No. Alerts follow state changes: one when the monitor changes from up to down, and one when it changes back to up.

Can it monitor a private URL?

Not by default. The endpoint must be publicly reachable by the BitterPing checker. Ask us before using a URL that requires credentials or network access.

Five important URLs are enough to start.

Talk to a person