Checked from 30 cities. Every 30 seconds.

Join the waitlist
$ npx pingvale init
30Check regions on six continents.
10sShortest check interval. 30 s on Team.
4sMedian time from failed check to your phone ringing.
41→1Alerts folded into one incident in the outage below.
Monitors

Watch every endpoint from where users are.

A check fails only when two regions agree. Then a third region retries before anyone is paged.

    Check types
  • HTTP and API assertions
  • Multi-step browser flows
  • SSL and domain expiry
  • Cron heartbeats
Monitors· 5 of 64
AllFailingPaused
MonitorTypeRegionsLast 45 daysUptimep95
API healthapi.halden.dev/v1/healthHTTPS · 30 s30
99.98%142 ms
Checkout flowhalden.dev/checkoutBrowser · 1 min12
99.95%1.9 s
Primary databasedb-1.halden.internal:5432TCP · 30 s6
100%3 ms
Nightly exportcron · every day 03:00Heartbeat—
99.2%—
TLS certificatehalden.dev · 41 days leftSSL · 6 h3
100%—
On-call

Page one person, not the whole team.

The assistant reads every alert, matches region, endpoint and the last deploy, and opens a single incident.

    Included
  • Rotations and overrides
  • Escalation policies
  • Phone, SMS, Slack and push
  • Quiet hours per person

Rotations

Weekly or follow-the-sun. Swap a shift from your phone.

Mira Okafornow
Priya NairThu
Elena RuizMon

Escalation

If nobody acknowledges, the next step runs on its own.

  1. 0 minPush and Slack to on-call
  2. 3 minPhone call to on-call
  3. 8 minPhone call to backup
  4. 15 minWhole platform team

Alert grouping

Forty alerts about one cause become one incident.

41 alerts ↓
Incident #212
APAC API errors after deploy 4821
Incidents

Every incident writes its own timeline.

Checks, pages, deploys and status posts land in one log. Export it as the first draft of your postmortem.

Incident #212· 17 min
Resolved
  1. Checks fail in Singapore and Hong Kong503 from 2 of 30 regions, retried from Tokyo.
  2. 41 alerts grouped into one incidentMatched on region, endpoint and deploy 4821 at 02:11.
  3. Mira Okafor pagedPhone and Slack.
    Acknowledged at 02:16
  4. Status page updatedDrafted by the assistant, edited by Mira.
  5. Deploy 4821 rolled backFrom GitHub, marked on the latency chart.
  6. ResolvedAll 30 regions green for 5 minutes.
Status update
Draft · written 20 s ago
Affected: API — Asia-Pacific
MinorMajorCritical
We’re seeing errors on API requests from Singapore and Hong Kong since 02:14 UTC. Other regions are not affected. A recent deploy is the likely cause and we’re rolling it back. Next update by 02:45 UTC.
Post to status pageEdit
Status pages

A public page that keeps up with you.

Components turn amber the moment a check fails. You decide what customers read.

status.halden.dev
Halden statusSubscribe to updates
Elevated API errors in Asia-PacificIdentified · We’re rolling back a recent deploy. Next update by 02:45 UTC.
WebsiteOperational
API — Americas & EuropeOperational
API — Asia-PacificDegraded
DashboardOperational
60 days ago99.97% uptimeToday
Your domainstatus.yourcompany.com with TLS, set up in one DNS record.
SubscribersEmail, RSS, Slack and webhooks, per component.
Private pagesFor enterprise customers, behind SSO.
Config as code

Monitors in a file. Reviewed like code.

Keep checks next to the service they watch. The CLI shows a diff before anything changes.

import { monitor, regions } from 'pingvale'

export default monitor({
  name: 'API health',
  url: 'https://api.halden.dev/v1/health',
  every: '30s',
  regions: regions.all(),
  failWhen: { regionsAgree: 2 },
  expect: { status: 200, p95: '<400ms' },
  page: 'platform-oncall',
  statusPage: 'API',
})
terminalzsh
$ pingvale deployReading pingvale.ts … 64 monitors   + checkout-flow   browser  1m  ~ api-health      every 60s → 30s  + db-primary      tcp      30s Apply 3 changes? yes✓ Deployed in 2.1 s✓ First checks from 30 regions$ ▍
Integrations

Works with the tools you page with.

Deploy markers from your CI, alerts where your team already talks.

PagerDutyForward incidents
OpsgenieForward incidents
DiscordAlerts in channels
GitHubDeploy markers
GitLabDeploy markers
VercelDeploy markers
CloudflareDNS and TLS checks
TerraformProvider
DatadogMetrics export
GrafanaDashboards
PrometheusMetrics export
OpenTelemetryTraces on incidents

Fewer pages. Better ones.

“Last quarter we had 1,200 alerts. Pingvale turned them into 38 incidents, and nobody on the team muted their phone.”
Aiko MorimuraSRE lead, Ferrowise
“The status update is drafted before I’ve opened my laptop. I change one line and post it.”
Jo AchebePlatform engineer, Quillstack
“We moved 140 monitors into one file in an afternoon. Changes go through pull requests now.”
Daniel FerrazCTO, Lumenkit
Pricing

Start free. Pay when you add the team.

Flat price per workspace. Phone calls and SMS included up to fair use.

Hobby

$0
  • 10 monitors, every 3 min
  • 5 regions
  • 1 status page
  • Email and Slack alerts
Join waitlist

Team

$29 / month
  • 100 monitors, every 30 s
  • All 30 regions
  • On-call for 10 people
  • Assistant: grouping and drafts
Join waitlist

Scale

$149 / month
  • 500 monitors, every 10 s
  • Private status pages, SSO
  • 13 months of history
  • 99.99% uptime SLA
Join waitlist
FAQ

Questions we hear on calls.

How do you avoid false alarms?

A monitor fails only when at least two regions agree, and you can raise that number. Every failure is retried from a third region before anyone is paged.

What does the assistant do, exactly?

It groups alerts that share a region, an endpoint or a recent deploy into one incident, keeps the timeline summary current and drafts status updates. It never posts an update or closes an incident on its own.

Can I keep my current on-call tool?

Yes. Send incidents to it with a webhook and use Pingvale only for checks and status pages.

Where do the checks run?

30 regions on six continents. Where we can, each region runs on two cloud providers, so one provider’s bad day does not look like yours.

How do I move my monitors over?

Import a CSV or an OpenAPI file, or describe monitors in pingvale.ts and run pingvale deploy.

Is there a free plan?

Yes: 10 monitors with 3-minute checks from 5 regions and one status page. No card needed.

Sleep through the nights nothing breaks.

We’re opening Pingvale to teams in batches. Leave your work email and we’ll send an invite.

Copied