Documentation

Everything you need to run Voltping. If something here is unclear, that's a bug — tell us.

Adding your first site

Paste a URL and save. That's the required part — everything else has a sensible default. We check it within a few seconds and every 60 seconds after that (every 30 seconds on Scale).

By default a monitor is up when the site answers with any status below 400. If you need something stricter, open Advanced options on the monitor form:

• Expected status — require an exact code, e.g. 200, or 301 for a redirect you want to stay in place.
• Keyword — require text to be present, or require it to be absent. Use "absent" to catch pages that return 200 while rendering an error.
• Slow threshold — above this, the site is marked slow rather than down. It shows amber on the dashboard and doesn't page you.
• Confirmations — how many consecutive failures open an incident. Two is the default and filters out most false alarms.

Monitor types

Alerts

Alert channels live in Settings → Alert channels. Mark one or more as default and every monitor uses them unless you attach specific channels to that monitor.

We alert on five events: a site going down, coming back up, an ssl_expiring or domain_expiring warning, and content_changed.

Expiry warnings fire once at 30, 14, 7, 3 and 1 days remaining — not every day for a month. Content-change alerts are limited to one per hour per monitor.

Webhooks

A webhook channel posts JSON to your endpoint. Set a signing secret and we add an X-Voltping-Signature header containing sha256= followed by the HMAC-SHA256 of the exact request body.

{
  "event": "down",
  "timestamp": "2026-08-14T02:11:07Z",
  "organisation": { "id": 12, "name": "Northgate Studio" },
  "monitor": {
    "id": 481,
    "name": "Northgate Dental",
    "url": "https://northgatedental.co.uk",
    "kind": "http",
    "state": "down",
    "client": "Northgate Dental",
    "status_code": 503,
    "response_ms": 1204
  },
  "incident": {
    "id": 90,
    "started_at": "2026-08-14T02:11:07Z",
    "duration_seconds": 0
  },
  "detail": "HTTP 503 Service Unavailable",
  "dashboard_url": "https://voltping.com/app/monitors/481"
}

Verify it in your handler by computing the same HMAC over the raw body and comparing in constant time. Never parse the JSON before you've checked the signature.

Status pages

Each status page has a slug and lives at https://voltping.com/status/your-slug. Choose which monitors appear and rename them for the public — visitors see "Website" rather than "prod-lb-01".

On the Agency plan and above you can serve a page from your own domain. Point a CNAME at us:

status.clientdomain.com.  CNAME  https://voltping.com.

then enter that hostname in the status page settings. Certificates are issued automatically. You can also hide all Voltping branding and password-protect a page for internal use.

Each page also publishes a badge at /status/your-slug/badge.svg and an RSS feed of updates at /status/your-slug/rss.xml.

Client reports

Go to Reports, pick a client and a month. You get a branded page with uptime, response times and every incident. Use your browser's Print to PDF to attach it to an invoice.

API

Create a key in Settings → API keys and read the API reference.

Our probe

Checks arrive with the user agent Voltping/1.0. If you run a WAF or rate limiter, allow it so your own monitoring doesn't get blocked.

We do not probe private network addresses. If a hostname resolves to a loopback, RFC1918, link-local or carrier-grade NAT address, the check fails with an explanation rather than reaching into a private network.