01
Private reachability
Check RFC 1918 endpoints, internal DNS, private ports, and authenticated applications.
Private network monitoring
Monitor private APIs and services from inside your network.
Run HTTP, port, heartbeat, Playwright, Postman, and custom scripted checks from self-hosted monitoring sources in your VPC, data center, or customer environment.
Self-hosted monitoring sources are available on eligible paid plans. On Free, public Ping, Port, and HTTP monitors have unlimited executions at a five-minute minimum interval from an assigned location.
Start Free for public Ping, Port, and HTTP coverage, then upgrade when a monitor must run inside your network.
Internal payments APIPassed from private pool
Healthy
Resolve private host 12 ms
Open TLS connection 48 ms
Run API workflow 284 ms
Verify response Passed
What this monitor proves
See private systems from the same network as their users.
Public probes cannot verify services that are intentionally unreachable from the internet. A self-hosted source keeps execution close to the system while centralizing results and response workflows.
02
Flexible depth
Use lightweight network checks or full browser, API, and custom scripted workflows.
03
Central operations
Keep history, alerts, incidents, maintenance windows, and status communication in Testable.
Setup
Place a monitoring source where the service is reachable.
Deploy the source in the appropriate network, assign monitors to it, and keep credentials and network access scoped to that environment.
Deploy the sourceRun it in the VPC, data center, or customer network that can reach the target.
Assign monitorsRoute one check or a group of monitors to the appropriate source pool.
Set health policyChoose interval, thresholds, retries, and confirmation rules.
Centralize responseReview evidence and manage notifications and incidents from Testable.
Example private target
target: https://payments.internal/health
source_pool: prod-us-east-private
interval: 60s
assert:
status: 200
json.status: readyWhen a check fails
Get evidence your team can act on.
Testable connects the failed check to investigation, alerting, incident response, and customer communication.
Source-level resultsSee which private location passed or failed and compare behavior across environments.
Protocol and script evidenceInspect timing, assertions, logs, traces, screenshots, and execution history as appropriate.
Controlled communicationAlert internal responders or publish selected components to a customer or partner status page.
Common questions
What teams ask before they start.
What can a self-hosted source monitor?It can run supported network, HTTP, heartbeat, browser, API, and custom scripted checks.
Does the service need to be internet-accessible?No. The monitoring source only needs network access to the target and the connectivity required to report results.
Can I use multiple private locations?Yes. Use source pools to monitor from the environments and regions that matter.
Bring production monitoring to systems the public internet cannot reach.
Deploy a source inside your network and run the same deep checks, diagnostics, and response workflows as public monitors.
