Uptime monitoring
Catch downtime the moment it happens, from multiple regions, before your customers notice.
API monitoring17 regions, every failure confirmed API monitoring,
API monitoring,
double-checked.
API uptime monitoring with your method, headers and body, every 30 seconds from 17 regions. A failure is rechecked from other regions before anyone is paged.
Free for 20 monitors with 5-minute checks. No credit card required.
Trusted by teams that put uptime first.
Read customer stories
One request, checked like a client. Method, headers, body, expected answer.
An API check is an HTTP monitor: Hyperping sends the request you describe on a schedule and compares the answer with what a healthy endpoint returns. Set it up in the dashboard, the API or Terraform.
- 1
Send the request your clients send
GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS, with custom headers such as an Authorization token or an API key, and a JSON, form or raw body. The Content-Type follows the body.
- 2
Say what a healthy answer looks like
Any 2xx, anything up to 3xx, or one exact status code. Add text the body must contain, like "status":"ok", and a timeout: a slower answer counts as down.
- 3
Run it every 30 seconds
Checks rotate through the regions you pick, one region per check. Every 30 seconds on paid plans, every 5 minutes on Free, and the Test button runs it once before you save.
What the probe sendshttp
POST /v1/checkout/health HTTP/1.1
Host: api.example.com
Authorization: Bearer $API_TOKEN
Content-Type: application/json
{"dry_run": true, "currency": "usd"}
# Up when: status 200 to 299
# and the body contains "status":"ok"Six ways an API breaks. Each one fails the check.
- POST /v1/checkout · 503 Service Unavailabledown · confirmed from 3 regions
The endpoint that falls over
A deploy, a full connection pool, a crashed worker. Any answer outside the status codes you expect fails the check, and the other regions confirm it before anyone is paged.
How failures are confirmed - 200 OK · {"error":"upstream timeout"}body check · 422
200 OK, wrong answer
Plenty of APIs answer 200 with an error inside. Put the text a healthy response always carries in Body contains, turn on Count it as down, and a missing string fails the check.
Body checks - GET /v1/orders · 401 Unauthorized401 · expected 200 to 299
The key someone rotated
Send the same Authorization header or API key your clients send. When the key is revoked or the auth service breaks, the 401 fails the check like any outage.
Request settings - GET /v1/search · no answer after 10 stimeout · down
Slower than your clients wait
Set the timeout your clients use, from 5 to 60 seconds. An answer that takes longer counts as down, and every check’s response time is kept per region.
Response times - cert · api.example.com · 7 days leftreminder · Slack and email
The certificate on the API host
Browsers forgive a lot that API clients don’t. Every HTTPS monitor checks its certificate daily: expiry, chain, hostname and revocation, with reminders before it lapses.
SSL monitoring - api.openai.com · 5xx from 3 regionsdependency down
The API you depend on
Payments, email, the model provider: when theirs is down, so is yours. Monitor their endpoints like your own, or see which popular services are down right now.
Is it down?
17 regions, one at a time. A failure is rechecked from the others.
A failed check is never trusted on its own. Other regions you selected rerun the same request at once, and only a failure they see too opens an outage and alerts your team.
- Scheduled check1 region · every 30 s
Each check runs from one of your regions, the next one from the next, so a few regions cover the world without multiplying requests.
- Failure503 · Frankfurt
A wrong status code, a missing string, a timeout or a refused connection. Nothing is sent yet.
- RecheckLondon · N. Virginia · Singapore
Other regions you selected run the same request at once, not at the next interval. If one of them gets a good answer, no outage opens.
- Confirmedoutage opens · alerts go out
Only a failure the other regions see too opens an outage, alerts the monitor’s channels and starts its escalation policy.
Pick the regions closest to your users and to your API, three or more so a failure has somewhere to be confirmed from.
- San FranciscoSFO
- N. CaliforniaCAL
- N. VirginiaVIR
- New YorkNYC
- TorontoTOR
- São PauloSAO
- LondonLDN
- ParisPAR
- FrankfurtFRA
- AmsterdamAMS
- Cape TownCPT
- MumbaiMUM
- BangaloreBLR
- SingaporeSGP
- SeoulSEO
- TokyoTKY
- SydneySYD
Then the right person hears about it. And your customers see it.
A confirmed failure starts the monitor’s escalation policy and turns the service red on your status page. When the API answers again, the outage closes and the page goes back to operational.
The on-call engineer, not a channel
Link an escalation policy to the monitor: Slack first, then SMS and a phone call to whoever is on call, then the next person if nobody acknowledges.
On-call and escalationA status page that updates itself
Add the monitor to a status page as a service. When the outage is confirmed, its status changes on the page, and back when the API recovers.
Status pagesQuiet during your deploys
Schedule a maintenance window for a migration or a release, and the API’s monitors don’t alert while it runs. Add an alert delay for endpoints that recover on their own.
Cutting the noise
Verified alerts.Where your team works.
Every alert is double-checked from at least two other locations before it reaches the tools your team already uses.
Slack
Microsoft Teams
Google Chat
PagerDuty
Opsgenie
Jira Service Management
Discord
Telegram
Mobile app- SMS
- Phone call
- Webhooks
When one request isn’t enough. Chained API checks in Playwright.
HTTP monitors check one request against a status code and a body. For a login before the call, or assertions on JSON fields, write a browser check that only makes API requests.
- 1
Log in, then call
Fetch a token, pass it to the next request, and check what comes back: the flows a single request can’t cover, written with Playwright’s request fixture, without opening a browser.
- 2
Assert on JSON fields
Check a field’s value, a type, an array’s length, a header. Secrets stay in the check’s environment variables, and a failed run keeps its logs and trace.
- 3
Counted as browser checks
These run every 5 minutes at most and count toward your browser checks: 3 on Essentials, 10 on Pro, 25 on Business. Keep them for the few flows that matter, next to your Playwright user journeys.
orders.spec.tstypescript
import { test, expect } from '@playwright/test';
test('log in, then read the latest order', async ({ request }) => {
const login = await request.post('https://api.example.com/v1/auth/token', {
data: {
client_id: process.env.CLIENT_ID,
client_secret: process.env.CLIENT_SECRET,
},
});
expect(login.status()).toBe(200);
const { access_token } = await login.json();
const res = await request.get('https://api.example.com/v1/orders?limit=1', {
headers: { Authorization: `Bearer ${access_token}` },
});
expect(res.status()).toBe(200);
const body = await res.json();
expect(body.data).toHaveLength(1);
expect(body.data[0]).toMatchObject({ status: expect.any(String) });
});What teams say about Hyperping.
@hyperping is really amazing
Hyperping’s reputation in our company is that it’s more reactive than Datadog. We usually get notifications from Hyperping before Datadog.
We picked Hyperping to bring a high quality incidents and status reporting dashboard to our users.
We have the real-time alerts from Hyperping telling us if the app is down. These are sometimes arriving even before AWS notices or notifies us.
We couldn’t imagine running our SaaS business without Hyperping now.
Hyperping nails all aspects: from smooth setup to peace of mind and attentive customer service.
You learn your site is down from a customer’s support ticket.
Uptime, status pages and on-call.One platform. Know before your customers do.
Server monitoring
A lightweight agent tracks CPU, memory and disk, so you spot trouble before it turns into downtime.
Browser checks / E2E
Playwright tests that catch broken sign-ins and checkouts before your customers do.
Cron job monitoring
Get alerted when a backup or scheduled job silently fails to run, not days later.
api.acme.com is down. HTTP 503 from Paris, confirmed from Frankfurt and N. Virginia.9:42 AM
Incident published on status.acme.com. 1,240 subscribers notified by email.9:43 AM
api.acme.com is back up. Downtime 4 min 12 s, incident resolved automatically.9:46 AM
View incident
Notification channels
Alerts reach the right person on 
Slack, Teams, SMS or a phone call, whichever wakes them up.
SSL monitoring
Keep certificates in check. Get alerted before they expire, so your customers always connect securely.
On-call calendar
Plan rotations, share the load, and see who’s on call. Every incident reaches the right person, at the right time.
Three tools. One better bill.Monitoring, status pages, and on-call. Together.
USD · Monthly billing for every plan
The tool mix
Three subscriptions to keep it all running.
- Pingdom100 uptime + 20 advanced checks$149/mo
- StatuspagePublic Startup + private Growth$348/mo
- PagerDutyProfessional · 10 users × $25$250/mo
Combined cost
$747/month
$8,964 over 12 monthsEverything connected, from the first check.
- 1,000 monitors
- 10 status pages
- 20 team members
- On-call & escalations
- 20-second checks
- Priority support
One platform. One subscription.
$299/month
$3,588 over 12 months60% less
Explore pricing Save $5,376 a year with this mix.
Pricing sources & assumptions
Reviewed . All amounts are USD; local currency prices may differ.
- Pingdom Synthetic Monitoring: $149/month for 100 uptime checks, 20 advanced checks and 350 SMS credits. USD rate from our August 17, 2026 review; the live calculator served EUR during this check, so the USD rate was not independently reverified today.
- Statuspage: one public Startup page ($99/month, 1,000 subscribers, 10 team members) and one private Growth page ($249/month, 300 authenticated subscribers, 15 team members).
- PagerDuty Professional: $25/user/month on monthly billing, for 10 users. Its $21 rate requires annual billing.
- Hyperping Business: $299/month on monthly billing. The advertised $249/month is a rounded annual equivalent of $2,990/year and is not used in this comparison.
This is one example of a three-tool stack, not the cheapest possible setup or a feature-for-feature match. Pingdom and PagerDuty also include status-page features; a separate Statuspage subscription may not be needed by every team. Usage charges and paid connectors are not included. Annual totals are 12 monthly payments, not annual subscription quotes.
Questions about API monitoring.
What is API monitoring?
API monitoring checks from outside your infrastructure that your API endpoints answer, answer correctly and answer in time. Hyperping sends the request you define, with its method, headers and body, from 17 regions on a schedule, checks the status code and the response body, and alerts your team once a failure is confirmed. See the definition in our glossary.
How do I monitor the uptime of an API?
Create an HTTP monitor with the endpoint’s URL, pick the method, add the headers and body your clients send, then set the expected status code and text the body must contain. Choose the regions and the interval, and the alert channels or escalation policy. Hyperping runs the check from then on and keeps every response time. See create a monitor.
Can Hyperping monitor POST requests with headers and a JSON body?
Yes. HTTP monitors send GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS requests with custom headers and a JSON, form or raw body, from the dashboard or the API. The Content-Type header follows the body type.
Can Hyperping check the content of an API response?
Yes, with Body contains: an exact, case-sensitive text the response must include, such as "status":"ok". Turn on Count it as down in the dashboard and a missing string fails the check; through the API, required_keyword does this on its own. HTTP monitors don’t evaluate JSON paths: for assertions on JSON fields, write a browser check with Playwright’s request fixture.
How often can an API be checked, and from where?
Every 30 seconds on paid plans and every 5 minutes on the Free plan, from 17 regions in North America, South America, Europe, Asia, Australia and Africa. Each check runs from one of the regions you select, in turn. See datacenter regions.
How does Hyperping avoid false alerts on API checks?
A failed check is not trusted on its own. Other regions you selected rerun the request at once, and only a failure they see too opens an outage and alerts anyone. An alert delay and the expected status code cut the rest of the noise. See false positives.
Can I monitor an API that requires authentication?
Yes, when a header is enough: an Authorization bearer token, Basic auth or an API key header, sent with every check. When a token has to be fetched first, a Playwright check logs in, passes the token to the next call and keeps the credentials in environment variables. OAuth flows and client certificates (mTLS) aren’t built into HTTP monitors.
Does Hyperping support both API checks and browser checks?
Yes. HTTP monitors cover single API requests, and Playwright browser checks cover user journeys and chained API calls, next to ping, port, DNS, cron job and SSL monitoring in the same account, with on-call and status pages. Teams comparing it with Checkly can read Hyperping as a Checkly alternative.
Can Hyperping monitor an internal API?
Not from inside your network: checks run from the public internet, so the endpoint has to be reachable from it. For a job or a service that only runs inside, a cron job monitor works the other way round: it pings Hyperping, and silence raises the alert.
Is API monitoring included in the free plan?
Yes. The Free plan includes 20 monitors with 5-minute checks, keyword checks and a status page, with no credit card. Essentials adds 30-second checks, on-call with phone call alerts and 3 browser checks. See pricing.