Real product. Real data.
Not mockups. These are live screenshots from a real Pinghawk dashboard monitoring production APIs.
Dashboard overview
Monitors list
Monitor detail with active incident
"your api is down" — now what?
Forensic snapshots at the exact moment of failure — DNS, TLS, TTFB, response body. The answer arrives with the alert. No more SSH. No more guessing.
No credit card · Indie plan free during beta · Hawk Mode, Slack, Discord, webhook, SSL, cron — all included
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.
No DNS timing. No TLS data. No TTFB.
No response body. No snapshots.
You know it's down. You don't know why.
The alert used to be the beginning of the investigation.
With Pinghawk, it's the end.
🦅 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 mandatory 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 soon.
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.
Real product. Real data.
Not mockups. These are live screenshots from a real Pinghawk dashboard monitoring production APIs.
Dashboard overview
Monitors list
Monitor detail with active incident
Features
Every feature earns its place. If it's here, it's because you'll actually use it.
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 soon. Works with any API — REST or GraphQL.
Full timeline of every outage — when it started, how long it lasted, which channels were notified, and delivery status per channel. A permanent record you can review anytime.
Live uptime percentage, response time trends, 7-day charts, slowest endpoints, and active incidents — all in one view. Updates in real time, no manual refresh needed.
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 soon.
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 soonPinghawk checks your APIs from the cloud — but some services are hidden behind your company's firewall and can't be reached from the internet. Pinghawk Agent is a small program you run inside your network so those hidden services get monitored too.
Internal tools, staging servers, database health checks, admin panels — these services are behind your firewall, which means they're invisible to any monitoring tool that checks from the internet. If they go down, nobody knows until something breaks.
How Pinghawk Agent works
A single command to start. No config files, no complex setup. The agent runs on the same machine (or network) as the services you want to monitor — so it can reach them even though the internet can't.
The agent checks your internal services and captures the same forensic timing data as cloud Hawk Mode — DNS, TLS, response time, response body. If something fails, you get the same detailed snapshot.
Everything shows up in the same dashboard as your regular monitors. Same alerts (email, Slack, Discord, webhook), same 3-strike rule before alerting, same recovery notifications. No difference.
Available on Indie (2 agents) and Pro (10 agents) plans.
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. Every signup gets Indie plan features free during beta — 30 days notice before any charges.
🦅 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