"your api is down" — now what?
Captures DNS timing, TLS handshake, TTFB, and response body at the exact moment of failure — so the answer arrives with the alert. No more SSH. No more guessing.
Built for backend engineers, solo devs, and small teams running APIs in production.
No credit card · All plans free during beta · 30 days notice before any charges
APIs behind firewalls? Pinghawk Agent runs inside your network. COMING SOON
By signing up you agree to our Terms and Privacy Policy
The problem
It's figuring out what happened. By the time you SSH in, check the logs, try to reproduce — the evidence is gone. And you're debugging a ghost.
28 minutes. No answer. Back to bed.
The difference
Most tools stop at "something is wrong." Pinghawk answers the question that actually matters.
The alert used to be the beginning of the investigation.
With Pinghawk, it's the end.
The shift
Instead of checking after failure, Pinghawk captures everything at the exact moment it happens. No reproduction required. No guesswork. No SSH.
🦅 Hawk Mode
At the moment of failure, Pinghawk automatically captures a full forensic snapshot — DNS, TLS, TTFB, response body, everything. No setup required. It's always watching.
Snapshot captured silently. No alert, no incident.
Snapshot captured silently. Still no alert — could be a fluke.
3rd consecutive failure. Incident created. All 3 snapshots linked. Alert sent to all channels.
Incident resolved. Recovery alert sent with total downtime duration. Counter resets — next outage triggers a fresh incident.
Why 3 failures before alerting?
Server restarts, DNS blips, and transient errors resolve in seconds. Alerting on the first failure would mean constant noise. Three consecutive failures means something is actually wrong — and by then, you already have 3 forensic snapshots showing how the failure developed.
Also watches over
Silent failures are the worst kind. Your backup stops running at 2am. Your sync job starts skipping records. Nobody notices — until it's too late.
Pinghawk's dead man's switch pings a unique URL at the end of each job. Miss it once — you're alerted within minutes.
An expired certificate means your API goes dark for every user instantly. No warning, no grace period — just failures.
Pinghawk warns you at 30, 14, and 7 days before expiry. And if a TLS handshake fails during a check, it's caught in the Hawk Mode snapshot too. Automatic. No configuration needed.
How it works
No agents. No SDKs. No YAML. Paste a URL and you're monitoring.
Any URL. Pick GET, POST, or HEAD. Set your check interval. Done. Custom headers coming at launch.
Pinghawk checks your endpoint every 30s–5min. Three consecutive failures confirm a real outage — dramatically reducing false alerts from transient blips.
When something breaks, your alert includes the full Hawk Mode snapshot — DNS, TLS, TTFB, response body. You know the root cause before you open your laptop.
When your endpoint recovers, Pinghawk sends a resolution alert with total downtime and incident link. One incident, two alerts — down and up. No noise in between.
Features
Every feature earns its place. If it's here, it's because you'll actually use it.
Verify from 3 global regions simultaneously. If two agree it's down, it's down. No false alarms from local network blips or transient issues.
Warned 30, 14, and 7 days before expiry. Never get caught by a certificate error in production again. Works for any HTTPS monitor — no configuration needed.
Dead man's switch for your scheduled jobs. Know immediately when a backup, sync, or cleanup task silently fails to run. Alerts via email, Slack, Discord, and webhook — not just email.
Shareable, branded pages your customers can bookmark. They stay informed. You get fewer "is it down?" support messages.
Three consecutive failures required before alerting — eliminates false positives from transient blips. One alert per incident, then silence until recovery. Recovery alerts include total downtime duration. No 3am spam.
Continuous latency monitoring with degraded and critical thresholds. Catch slowdowns before they become outages — not just 5xx errors.
HTTP method selection (GET, POST, HEAD) works now. Custom request headers and auth token injection coming at launch. Works with any API — REST or GraphQL.
Paste a URL. Pick an interval. Done. No agents, no SDKs, no YAML. If setup takes more than a minute, we failed.
Alerting
Every alert includes the endpoint, response time, region, and Hawk Mode snapshot — so you can act without logging in first.
Every plan. Always on. Sent to your account email instantly.
Rich Block Kit messages to any channel. Incident details + action buttons.
Rich embeds with colour-coded status, timing data, and incident links.
JSON payload to any URL. Signed with HMAC-SHA256 so you can verify it's from Pinghawk.
Text message alerts for critical incidents. Coming at launch.
3rd consecutive failure on api.myapp.io/payments
Incident is open. No further alerts until recovery.
Your inbox stays clean. No 3am spam.
2 consecutive successes. Incident resolved.
Recovery alert sent to all channels with total downtime: 12m 34s
Introducing
Coming soonYour APIs behind firewalls, VPNs, and private networks are invisible to cloud monitoring. Pinghawk Agent runs inside your network — so the endpoints that are restricted from outside access are no longer unmonitored.
Internal health checks, staging APIs, database endpoints, admin panels, microservices behind a VPC — these are unreachable from the internet by design. Firewalls and network policies block all external access. That means your most critical infrastructure has zero monitoring visibility.
How Pinghawk Agent works
A lightweight npm package that runs on any machine with Node.js. One command, no config files, no open inbound ports. It sits behind your firewall — right next to the services it monitors.
The agent performs HTTP checks from inside your network and captures the same forensic timing data as cloud Hawk Mode — DNS, TCP, TLS, TTFB, response body. All captured locally.
Results flow into the same pipeline — same incident detection (3-strike rule), same alerts to all your channels, same dashboard. Cloud and agent monitors appear side by side.
Available on Indie (2 agents) and Pro (10 agents) plans. See pricing → | Read the docs →
Pinghawk Agent
API https://api.pinghawk.io
Agent office-network
Monitors 4 assigned
✓ Connected · Running... (Ctrl+C to stop)
✓ Internal API up 42ms dns:3 tcp:8 tls:0 ttfb:38
✓ Staging DB up 18ms dns:2 tcp:5 tls:0 ttfb:14
✗ Auth Service timeout 10,000ms TIMEOUT
✓ Redis Health up 3ms dns:0 tcp:1 tls:0 ttfb:2
Reported 4 result(s)
Next poll in 30s
Now monitorable with Agent
Works with Docker · Kubernetes · AWS VPC · DigitalOcean · Hetzner · any machine with Node.js 18+
What developers are saying
Pricing
Priced for developers who ship things themselves. No per-seat fees. No hidden limits. No "contact sales."
Start free. No credit card. No lock-in.
On the roadmap
Check more than status codes. Define expected response shapes — alert before users hit a data bug.
Add monitors without leaving your terminal. pinghawk add https://api.example.com
Free beta
Get alerts with answers, not just problems. All plans free during beta — 30 days notice before any charges begin.
🦅 Start monitoring free →Or drop your email to follow the build:
No credit card required
By joining you agree to our Terms and Privacy Policy