Trace every path.Before it breaks.

Open-source network observability from probes you control.

Read the docs View on GitHub

Open source controller

Go API, React web app, generated OpenAPI contract.

Probes you control

Agents report heartbeat, capabilities, labels, and measurements.

Complete check suite

HTTP uptime, DNS, ping, TCP connect, and traceroute assigned by labels.

Status you can publish

Operational state, charts, and incidents for public pages.

The internet, measured from where you stand

Netstamp is the observability layer where probes, checks, routes, and incidents are owned, measured, and verified by your own infrastructure. The result?real viewpointsmeasurable uptimeandroute evidenceyour team can act on.

Netstamp is

Built for operators who need evidence.

Owned viewpoints

Measurements start from probes you deploy, label, and trust.

Verifiable by result

Every status is backed by ping, TCP, traceroute, and latest-result evidence.

Uptime with context

Operational state includes success rate, failure percent, stale probes, and incidents.

Route-aware by default

Traceroute runs become hop timelines, topology, and path-change signals.

Automation ready

OpenAPI, Docker Compose, and notification targets fit into existing operations.

The measurement stack

Measurement, engineered.

Netstamp turns distributed probes into evidence your operators can inspect, automate, and publish.

PROBE FLEET

Viewpoints you control

Heartbeat, labels, location, IPv4/IPv6 capability, public IPs, and runtime status.

TPENRTSJCFRASIN

CHECK SCHEDULER

Assignments by label

Define HTTP, DNS, ping, TCP, and traceroute checks once; match probes through selectors.

env=prodregion=apacprobe.tpeprobe.nrt

REACHABILITY ENGINE

Uptime from measurements

Latest statuses, HTTP response time, DNS resolution, success rates, packet loss, and TCP failure percent.

ROUTE INTELLIGENCE

Traceroute topology

Hop timelines, destination reachability, path changes, loss propagation, and topology edges.

TPEIXPNRTSJCAPI

INCIDENT LOOP

Alerts and notifications

Threshold windows, severity, cooldown, incidents, webhook, Slack, Discord, Telegram, and email.

p95 > 220mscriticalwebhook

PUBLIC INTERFACE

Status pages and API

Operational pages, uptime charts, active incidents, Docker Compose, and generated OpenAPI.

GET /v1/checks200 application/jsonstatus: operational

Evidence layer

A green dot is not enough.

Netstamp shows why a service looks healthy, where it was measured from, and which path the packet actually took.

api.example.com

STATUS operationallatest result verified by 18 probes

Product surfaces

Every surface leads back to evidence.

Fleet state, check definitions, result insight, alert routing, public status, and API automation share the same measurement loop.

Insight

Latency, loss, and path changes in one view.

Dashboard

Probe fleet map, online count, active checks.

Probes

Heartbeat, labels, location, capabilities, secret rotation.

Checks

HTTP uptime, DNS, ping, TCP connect, traceroute.

Alerts

Threshold rules, incidents, cooldowns, notifications.

Status pages

Operational state, assignment groups, charts, active incidents.

API

Generated OpenAPI, request console, typed client.

GET /openapi.json

Self-hosting

Docker Compose, migrations, PostgreSQL and TimescaleDB.

docker compose up

Why operators choose Netstamp

Measure from real networks, not a vendor region.
Compare latency and packet loss across probes.
Investigate route changes before users report symptoms.
Route incidents to the tools the team already watches.
Publish status with evidence, not guesswork.

How builders integrate Netstamp

Deploy the controller with Docker Compose.
Install lightweight probe agents.
Use labels and selectors to assign checks.
Query generated OpenAPI endpoints.
Store history in PostgreSQL and TimescaleDB.

Where it fits

Run it where the network matters.

SaaS and API teams

Track reachability from customer-like regions, compare latency across providers, and publish incidents with context.

Labs and private networks

Run probes inside networks only you can see, detect stale viewpoints, and keep historical measurements.

Edge and hosting operators

Watch route changes between regions, verify DNS answers, and compare packet loss across ISPs.

Open-source infra

Self-host the controller, share public status pages, and automate through OpenAPI.

Start with a measurement loop

Choose the first system to instrument.

Start deployingRun the self-hosted controller and install your first probe.Start measuringCreate ping, TCP, and traceroute checks assigned by labels.Start investigatingInspect latency, packet loss, route changes, and topology.Start publishingTurn measurements and incidents into public status pages.

Stay in the loop

Docs, API, status examples, and operational patterns.

FEATUREDDeploy Netstamp with Docker Compose FEATUREDCreate your first probe OPENAPIGenerated contract for controller integrations GITHUBOpen-source controller, web app, and probe agent

FAQ

Questions before you deploy.

What is Netstamp?

Netstamp is open-source, self-hosted network observability from probes you control.

How is this different from normal uptime monitoring?

Normal uptime monitoring checks from someone else's cloud. Netstamp measures from the networks you choose.

What checks does Netstamp support?

HTTP uptime, DNS, ping, TCP connect, and traceroute checks from controlled probes.

Can I publish a public status page?

Yes. Netstamp can turn assignment groups, measurements, and incidents into public operational state.

Can I automate it with an API?

Yes. The controller exposes a generated OpenAPI contract for integrations and request-console workflows.

What do I need to self-host it?

A controller deployment, PostgreSQL/TimescaleDB-backed history, and probe agents installed where you need viewpoints.

Run measurements from networks you own

Deploy the controller, register probes, and start collecting evidence about the paths your traffic actually takes.

Deploy Netstamp Read the docs