Pingward
Log inStart free
Uptime monitoring for people who ship

Know before your users do.

Pingward checks your endpoints as often as every 60 seconds, confirms the failure, and alerts you within seconds — by email, Telegram, webhook or push.

Start free

100 monitors · free · no credit card

Monitors5
Example data
  • Up

    Marketing site

    acme.com

    99.99% uptime128 ms
  • Up

    API prod

    api.example.com/health

    99.97% uptime212 ms
  • Down

    Checkout

    checkout.example.net

    98.41% uptimetimeout
  • Pending

    Docs

    docs.example.org

    ——
  • Paused

    Background worker

    worker.example.dev/ping

    99.90% uptime—

Illustrative example. Not live data.

How it works

A check, a confirmation, an alert.

No agents to install and no configuration language to learn. Point Pingward at a URL and it runs the loop for you, around the clock.

01
We check

Every monitor gets an HTTP GET or HEAD request on your schedule. A check passes when the status code lands in your expected range — 2xx–3xx by default — and, if you set one, when the response body contains your keyword.

60 s – 1 h
02
We confirm, then open an incident

One bad request is not an outage. Pingward waits for consecutive failures — two by default, configurable from one to five — then opens an incident that records the first error and how many checks failed.

2 failures
03
You get alerted

The incident fans out to every alert destination you have switched on. When the next check succeeds the incident resolves, and a recovery alert goes out with the outage duration.

down + recovery

Alerts

Four ways to hear about it.

Alerts fire on both the down and the recovery transition, to every destination you have switched on — each one covers all of your monitors. Every delivery attempt is recorded, so you can see what actually reached you.

Email

Down and recovery emails with the monitor name, the URL, the error and how long the outage lasted.

Telegram

Tap a one-time deep link to connect the Pingward bot once; after that alerts arrive as chat messages.

Webhook

A JSON POST to your endpoint, signed with your account's HMAC-SHA256 secret so you can verify it is us.

Push

Native push notifications to the Pingward mobile app for iOS and Android.

POSThttps://hooks.example.com/pingward
{
  "event": "down",
  "monitor": {
    "name": "API prod",
    "url": "https://api.example.com/health"
  },
  "incident": {
    "started_at": "2026-08-18T14:03:00Z",
    "first_error": "HTTP 503",
    "checks_failed_count": 2
  }
}

X-Pingward-Signature: hmac-sha256

Alerting is not metered. Switch a destination on in Settings and it covers every monitor on the account, including the ones you add later.

Status pages

Tell your users first.

Every account gets a public status page, so the people asking “is it just me?” can answer it themselves.

  • One public page per project at /s/your-slug — visitors never need an account.
  • Overall state, per-monitor state, 90 days of daily uptime bars and recent incidents.
  • Only the monitors you attach are shown, under display names you choose; raw URLs stay private unless you opt in.
  • One public status page per account.
/s/acme
Example page
All systems operational
Website100.00%
API99.91%
Checkout99.74%
90 days ago → todayUpDown

No incidents in the last 7 days.

FAQ

Questions worth answering.

Straight answers about what Pingward does today.

Point it at a URL. Forget about it.

Your first monitor, free, in about two minutes.

Start freeLog in