For Engineers

Monitoring that
speaks your stack.

Authenticated endpoints, custom headers, webhooks, traceroute, IRR/RPKI lookups. Built for engineers who own production, priced for teams without a procurement department.

Enlist Free Run a free ping test
40+
Ping probes
2
Monitor regions
1 min
Detection
0
Sales calls
The Pain

Most monitoring tools were built to check homepages. Your production isn’t a homepage.

Authenticated endpoints, geographic blind spots, and network changes that break for some regions and not others. Three pains uptime tools weren’t built to handle.

Your API needs a Bearer token. Their monitor sends a GET.

Real production endpoints sit behind authentication. They expect Bearer tokens, custom headers, the right HTTP method, and they return status codes outside the 2xx/3xx default. Pingdom and UptimeRobot were built for marketing sites — they choke on anything past GET /. PingForce monitors handle Basic auth, Bearer auth, custom headers, all standard HTTP methods (HEAD/GET/POST/PUT/PATCH/DELETE/OPTIONS), and user-defined "up" status code ranges. You can monitor /api/v1/health behind a token. You can flag 401 as an incident on a protected route. You can POST a real payload and parse the response.

"It’s slow from Singapore" — and your tools test from Virginia.

When a customer reports latency from a region you don’t monitor from, single-location uptime tools leave you guessing. PingForce’s Ping feature tests on-demand from 40+ probes across 7 cloud providers — North America, Europe, Asia-Pacific, South America, Africa. Reproduce the customer’s experience from their continent, not yours.

BGP change at 2am. Did it route correctly from every region?

Anycast misconfigurations, CDN routing issues, and BGP changes don’t show up on uptime monitors — they show up in customer support tickets days later. Run a multi-region traceroute before and after the change. Confirm the new route from every continent. Get out before your pager does.

Ping Feature

Recon tools for engineers who care about the path, not just the destination.

When something’s wrong with the network, latency numbers don’t tell you why. You need to see the route, the routing registry, and the signal validation. Bring your own probes when the public network isn’t enough. Export when you need evidence.

40+ probes. 7 cloud providers.

AWS, Vultr, DigitalOcean, Linode, GCP, Hetzner, Azure. Multi-provider isn’t just geographic — it’s network path diversity. Up to 50 simultaneous probes per test (tier-dependent). North America, Europe, Asia-Pacific, South America, Africa coverage.

Traceroute with hop-by-hop path

ICMP and TCP traceroute from any probe location. See the full hop chain, identify the slow hop, screenshot the result and drop it into the incident postmortem. Configurable hop count, timeout, and probe count per hop.

WHOIS / IRR / RPKI lookups, built-in

Every ping result includes the network intelligence you’d otherwise pull from three separate tools. WHOIS for ownership and ASN. IRR for declared route objects. RPKI for route origin validation status. One result page, no CLI tabs.

Bring your own probes

Deploy probes anywhere — internal VPCs, on-prem datacenters, branch offices, edge locations. Private probes are yours alone. Contribute probes back to the community network and earn additional ping slots in return. Lightweight agent, minimal config.

Export to JSON, CSV, or shareable link

Result data goes where you need it: into a Jupyter notebook for analysis, into a Jira ticket as a shareable link, into a runbook as CSV evidence. No "contact sales for API access" wall.

Explore the probe network
Monitor Feature

Uptime monitoring that handles real endpoints.

Continuous endpoint monitoring from multiple US locations. 3-check confirmation eliminates false alarms. Configurable for the endpoints you actually run.

Authentication, methods, headers — all configurable

Monitor what’s actually running:
  • Auth: None, Basic, Bearer
  • HTTP methods: HEAD, GET, POST, PUT, PATCH, DELETE, OPTIONS
  • Custom headers: API keys, content negotiation, routing headers
  • Request bodies: JSON or form-encoded
  • Up status codes: user-defined ranges (flag 401 as down on auth-protected routes, allow 404 on search endpoints)
  • Follow redirects: toggle on/off
  • Keyword checks: presence or absence of strings in response body
  • SSL & domain expiry: 30-day warnings before certificate or domain death

Webhooks, Slack, Teams, PagerDuty

Incident open and close events fire as webhooks — wire them into PagerDuty, Opsgenie, your CI/CD pipeline, your internal incident bot. Native Slack and Microsoft Teams integrations. Email and SMS still work for the humans on the team. Pick channels per-monitor or globally.

Monitor Feature currently runs from 2 US locations. EU monitor probes are on the roadmap.

Workflow

A workflow that looks like your incident channel.

Alert fires. Verify globally. Drill into the path. Export the evidence. Four moves between page and postmortem.

1

Monitor opens an incident

PagerDuty pages on-call. Slack channel gets the webhook. You’re 30 seconds awake and squinting at your laptop.

2

Ping from 40+ probes

Confirm the outage is real and identify the geographic blast radius. East Coast US only? Global? Single ASN? Now you know where to look.

3

Traceroute + RPKI lookup

Hop-by-hop path from affected regions. Cross-check the route against IRR/RPKI. Spot the misconfigured peer or the dropped announcement.

4

Export the evidence

Shareable link in the incident channel. CSV attached to the postmortem ticket. Move on with your night.

  • No instrumentation
  • No agents on prod
  • Webhooks fire on open and close
  • Free tier covers small teams
Recommended for Teams

Most engineering teams land on Major.

Production-grade slot counts. Room for private probes. Priced like a tool, not a procurement event.

RECOMMENDED FOR TEAMS
Major
$33/mo
or $316.80/yr · save 20%
  • 100 monitors at 1-minute intervals
  • 200 SMS alerts/month
  • 3 status pages
  • 2 child accounts
  • 25 Flex / 7 Private / 20 Donated ping slots
  • Email, SMS, Slack, Teams, webhook alerts
  • Public + password-protected status pages
  • Authenticated HTTP monitoring (all methods, headers, custom status codes)
Get Major — $33/mo

Bigger team? See Colonel — 200 monitors, 50 Flex / 20 Private slots, 5 child accounts.

See full pricing →
Field Reports

From engineers running real production.

Sample — Replace before launch

Got a quote from a big enterprise monitoring vendor — $40k a year, six-month rollout, and a sales motion that took weeks. Signed up for Captain in 90 seconds. Same insights, less bureaucracy.

[CMS: author_name]
[CMS: author_role] · [CMS: author_company]
Intel Briefing

Questions engineers ask us.

Can I monitor an endpoint that requires authentication?

Yes. PingForce monitors support Basic auth (username/password) and Bearer tokens, plus custom request headers for API keys or other auth schemes. You can also set custom HTTP methods (HEAD, GET, POST, PUT, PATCH, DELETE, OPTIONS), send a request body (JSON or form-encoded), and define which status codes count as 'up' — useful for routes where 200 isn't the only valid response, or where 401 should specifically flag as an outage on a protected endpoint.

Are webhooks available? Can I wire PingForce into PagerDuty / Opsgenie / our CI/CD pipeline?

Yes. Webhooks fire on both incident open and incident close events. Wire them into PagerDuty, Opsgenie, your internal incident bot, or your CI/CD pipeline. Native Slack and Microsoft Teams integrations are also available alongside email and SMS. You can configure alerting per-monitor or globally.

Is there an API? Can I export results programmatically?

Ping results can be exported as JSON or CSV, and shared via shareable result links. A full programmatic API for managing monitors and probes is on the roadmap — if it's a blocker for you, email support@pingforce.net and let us know your use case.

Can I run my own probes? What does 'BYOP' actually mean?

Yes. Deploy a lightweight probe agent anywhere — internal VPCs, on-prem datacenters, branch offices, edge locations. Private probes are visible only to your account. Community probes are contributed back to the shared network and earn you additional ping slots in return. Each paid tier includes a slot allotment for private and donated probes.

Do you support traceroute? From which locations?

Yes. ICMP and TCP traceroute are available from any of the 40+ Ping probe locations across 7 cloud providers. Configurable hop count, per-hop probe count, and timeout. Results include the full hop chain with latency at each hop. Useful for identifying where the path is breaking — your network, transit, or the destination's network.

How do you handle transient network blips? I don't want to wake up for a 2-second hiccup.

Monitors require 3 consecutive failed checks before opening an incident, and 3 consecutive successful checks before closing it. On 1-minute intervals that's 3 minutes minimum detection time — fast enough for real outages, immune to single-check noise. There's also a known minor inflation in down_count from the 3-check clearing requirement; we're tracking that as an internal accuracy improvement.

Do you monitor SSL certificates and domain expiry?

Yes. HTTP/HTTPS monitors automatically check SSL certificate validity and warn you 30 days before expiry. Domain registration expiry is also monitored on HTTP/HTTPS monitors. Both are alerted through your normal alert channels (email, SMS, Slack, Teams, webhook) so they show up in the same incident flow as availability failures.

How do simultaneous probes and slot allotments work?

Each ping test consumes one or more Flex slots — one slot per probe location used in that test. Captain tier has 15 Flex slots, Major has 25, Colonel has 50. Private slots are reserved capacity for your own BYOP probes. Donated slots are earned by contributing community probes. Up to 50 simultaneous probes per test is the platform cap (which is why Colonel has 0 donated — already maxed).

Have a different question? Email support@pingforce.net — engineers usually reply within a few hours.
Stand-By for Deployment

Stop guessing. Start watching the network.

Free forever tier. 40+ probes. Authenticated monitoring. No procurement theater.

ENLIST FREE Run a free ping test
No credit card Free 5-min checks 1-min on paid plans Cancel anytime