Live now· #7 this week
PingWise

PingWise

Quorum-based uptime monitoring that alerts only on confirmed outages

FreeDevOpsMonitoringOther2,094 impressions#7 this week4 comments

Maker links to DevHunt

Comments

>log in to comment
  • Aditya Goel· 4d ago

    The quorum makes sense for cutting false alarms, but what about outages that only hit one region? If a CDN edge or a cloud region fails in Asia, the site can be down for every customer in India while the US and EU probes still see it fine, so 14 of 20 never agree. Is there a separate per-region alert, or a way to say "tell me if every probe in this region fails" for markets that matter to a team?

    • Alex Kyrlis[maker]· 3d ago

      Fair point, but PingWise already solves it: 1. “Down” needs the wide agreement you describe. Next to it there is “Partial”: the site fails from some continents and works from the rest. It triggers when at least half of the probes on the *affected continent* fail, at least two of them, while fewer than a third fail elsewhere. Your example is exactly that: our Asia probes (Mumbai, Singapore, Tokyo, Fujairah) fail, the US and EU ones pass, and the monitor shows a partial outage with the list of which cities saw what. The panel always shows it. As an alert it’s a switch per monitor, “Alert on partial outages”, off by default so that people who only serve one region aren’t paged about a route on the other side of the world. Turn it on for the monitors where those markets matter. 2. You can also tell a monitor where its visitors are, for example Asia only, or leave it to us to pick (the platform choose automatically). Partial outages are then judged *on the probes in those regions*, so a failure where your customers are is the one you hear about, and one on the other side of the world isn’t. We’re also testing a stronger version, using globalping's network as a second layer after we detect an outage with our probes.

  • kris gu· 6d ago

    Our previous approach was to curl each node in two different regions separately, and only send an alert when both regions failed simultaneously—simple but still produced many false positives, because network jitter in a single region often affected multiple nodes at once. The threshold of 14/20 probes and requiring two consecutive consistent results to deem a downtime is solid, especially the detail of marking WAF challenges as blocked rather than down. I'm curious about one point: how long is the interval between the two consecutive consistent rechecks? If the recheck happens immediately after the first failure, brief jitter might cause both to be caught; extending the interval would slow down real alerts.

  • Alex Kyrlis[maker]· 13d ago

    I built PingWise to cut down false alarms by requiring agreement from probes on three continents and networks before marking a site down. It gives 650,000 free monthly credits and uses a quorum system that re‑checks failures before paging anyone. How do you currently verify outages across multiple regions before alerting your team?

Uptime monitoring confirmed from probes on three continents and three networks before anyone is paged. 650,000 free checks a month for the month you join and the three after it, then 200,000 a month for good. After that, one price: €5 per million checks, packs from €5. A site is marked down only when 14 of 20 probes, on at least three continents and three different networks, agree, twice in a row. If it fails in one region only, you see a partial outage with the cities that saw it, and you choose whether that alerts you. If it’s down, it’s down. If it isn’t, you sleep. Checks every 10 seconds if you want them: HTTP, keyword, TLS, ping, TCP, SMTP, DNS, SSH, IMAP, POP3, FTP, NTP, WebSocket, heartbeats for cron jobs, domain expiry, mail blacklists and SPF, DKIM and DMARC. Every alert carries what each probe saw. A WAF challenge is reported as blocked, never as down, and every check is cryptographically signed so a firewall can verify it is ours. Alerts to email, SMS, phone calls, Slack, Teams, Discord, Google Chat, Telegram, PagerDuty, push and signed webhooks, with acknowledge and escalation. Status pages on your domain, an API, and an MCP server so your AI assistant can ask which sites were down this week. For hosting providers: connect Enhance, cPanel/WHM or Plesk and every site is monitored as it is created, with one alert when a server goes down, not one per site. No card, no seats, no subscription unless you want one.

More DevOps tools →80 free dev tools →

  • Prepaid credits, no subscription tiers
  • Probes in 15 cities across 6 continents
  • Alert only when 10 of 15 probes on 3 continents agree
  • TTFB check for HTTP monitors
  • Multiple alert channels: email, Telegram, Slack, Discord, Teams, etc.
  • One alert per server outage, not per site

PingWise provides quorum-based uptime monitoring using a global fleet of probes that only alert when multiple locations agree an outage exists.

for
Site reliability engineers and DevOps teams needing reliable outage alerts
pricing
freemium
works withSlackTeamsDiscordTelegramPagerDutyntfyPushoverWebhooks

Key features

8 features of PingWise
  • Quorum alerts — Pages only when two-thirds of healthy probes across three continents and networks agree on an outage.
  • Global probe fleet — 15 dedicated servers in 15 cities on 6 continents check each target.
  • Multi-protocol checks — Monitors HTTP(S), TLS, TCP, SMTP, DNS, ping and custom heartbeats.
  • Partial outage detection — Shows regional failures instead of marking the whole site down.
  • Status pages — Public pages with custom branding, showing confirmed outages and history.
  • Alert integrations — Sends alerts to Email, Slack, Teams, Discord, Telegram, PagerDuty, ntfy, Pushover and webhooks.
  • Free credit tier — 650,000 credits each month with no card, seats or subscription required.
  • API & webhooks — REST API for monitors, incidents, groups and status pages, plus signed alert webhooks.

Use cases

  • Detect real outages across multiple regions without false alarms
  • Monitor API endpoints with custom headers and body
  • Track SSL certificate expiry and receive alerts
  • Watch cron job heartbeats to ensure scheduled tasks run
  • Provide customers with branded status pages

PingWise pricing

  • Free creditsfree650,000 credits per month · No card required · No subscription
  • 250k pack€5/packAdds 250,000 credits · Valid for 24 months
  • 1M pack€15/packAdds 1,000,000 credits · Valid for 24 months
  • 4M pack€40/packAdds 4,000,000 credits · Valid for 24 months
  • 15M pack€75/packAdds 15,000,000 credits · Valid for 24 months

PingWise vs alternatives

PingWiseBetter Stack
Best forQuorum-based uptime monitoringUptime monitoring with incident logs
PricingFreemiumSubscription
DevHunt upvotes80
LaunchedNov 2026—
  • PingWise vs Better Stack: Better Stack offers uptime monitoring with incidents and logs but uses different alerting rules and pricing models.

PingWise FAQ

Is there a free plan?+

Yes, every account receives 650,000 credits each month with no card, seats or subscription required.

How quickly are alerts sent after an outage?+

An alert is sent after the check interval plus about a minute for confirmation, e.g., ~2 min for 1-minute checks.

Will it work with sites behind Cloudflare?+

Yes, blocked Cloudflare challenges are reported as “blocked” and can be allowed via a rule or by connecting your Cloudflare account.

Can I publish status pages?+

Yes, you can create branded public status pages with custom domains, logos and colors.

Is there an API?+

Yes, a REST API with read-only and read-write keys is available, plus signed webhooks for alerts.

Where are the probes located?+

Probes run in 15 cities across Europe, Americas, Asia, Oceania and Africa, covering six continents.

Summarized by DevHunt from pingwise.com · Nov 2, 2026. Details may change; check the official site.