Skip to content

Pingflare

Uptime monitor with multi-step API checks and a public status page, built on Workers and D1

Pingflare Edit Monitor screen: a two-step health check script in the visual builder with status and JSON assertions

Every minute, a Cron Trigger runs Pingflare's health checks, writes the results to D1 and feeds a public status page with 90-day uptime bars and incidents. Checks can chain several requests and assert on status codes, response times, JSON paths and headers. Alerts go to Slack, Discord, webhooks or browser push.

You build checks in a visual editor, without writing code. A multi-step check can log in, extract a token and then call an API, with assertions at each step. Severity rules mark a service as degraded or down. The public page at /status groups monitors and carries incident updates. Each monitor has its own alert routing. The installable PWA turns alerts into native push notifications on a phone. The dashboard uses email and password sessions with admin, editor and viewer roles. Pingflare is a SvelteKit app built into one Worker, with Workers Static Assets and a D1 database. The every-minute Cron Trigger authenticates with a CRON_SECRET.

Built for: Small teams and self-hosters who want uptime checks and a status page inside their own Cloudflare account

What you can use it for

  • Monitor APIs and websites every minute from Cloudflare's network
  • Publish a status page with incident updates for a small service
  • Test a login flow end to end with a multi-step script
  • Get Slack or Discord alerts when a service degrades or goes down

Deploy

  • One-click · main path

    Branch main

  • CLI

    Branch main

    Replace database_id in wrangler.toml with the ID that wrangler d1 create prints before building, as the README's manual setup says.

    git clone https://github.com/isala404/pingflare.git
    cd pingflare
    bun install
    bunx wrangler login
    bunx wrangler d1 create pingflare-db
    bun run build && bun run deploy
    openssl rand -hex 32 | bunx wrangler secret put CRON_SECRET

The Deploy button prompts for CRON_SECRET and runs D1 migrations. Then open the Worker URL and create the admin account.

What it needs to run

  • D1 databasespingflare-db

Good to know

The repository has 24 commits from one contributor, made between November 18 and December 26, 2025, and none since. On Workers Free, the limit of 50 subrequests per cron invocation caps Pingflare at about 25 monitors. Checks run at most once a minute.

Cost on Cloudflare

Likely fits the free plan

The README says Pingflare works within the Workers Free plan, up to the monitor cap. The every-minute check uses one of the account's 5 Free Cron Triggers, and each run gets 10 ms of CPU. Check results are written to D1, which allows 100,000 rows written per day on Free.

Source

The estimate is based on Cloudflare’s documented limits and the app’s configuration. What you pay depends on your usage and plan.

Where this comes from

Listing history

  • Oct 2, 2026 · Pingflare listed
  • UptimeFlare status page reporting all systems operational, with daily uptime bars and response-time charts

    Serverless uptime monitor and status page with HTTP, TCP and keyword checks, deployed through GitHub Actions

    Deploy
    Manual
    License
    Apache-2.0
    GitHub stars
    3.9k stars
    Last commit
  • CF-Server-Monitor dashboard in light theme (Chinese UI), with per-server CPU, RAM, disk, traffic and latency bars

    Server monitoring with a reporting agent on each machine, a live dashboard, seven-day history and offline alerts

    Deploy
    One-click
    License
    MIT
    GitHub stars
    2.4k stars
    Last commit
  • Uptimer public status page with website and server monitors, 60-day availability bars and latency of the last 60 checks

    Uptime monitor and status page with HTTP and TCP checks, incidents and webhook alerts, on Workers, Pages and D1

    Deploy
    Manual
    License
    MIT
    GitHub stars
    481 stars
    Last commit