Home/How it works
DISTRIBUTED ARCHITECTURE & INCIDENT LIFECYCLE

How Stillpoint keeps guard over your infrastructure.

A transparent look under the hood: from multi-region edge dispatch and consensus verification algorithms to automated root-cause capture and noise-free escalation.

DETERMINISTIC PIPELINE

The 5 stages of an uptime check

Every synthetic probe follows an immutable, multi-step pipeline engineered for sub-second precision and total immunity to false alarms.

01

Edge Dispatch & Jitter Scheduling

Our distributed scheduler instructs global edge probes to execute requests against your configured endpoint. Probe executions incorporate microsecond jitter to avoid artificial traffic spikes on your origin servers.

Operational Specs
  • Check frequency: 10s to 300s
  • Protocols: HTTP/1.1, HTTP/2, TLS 1.3, WS
  • Global coverage: 5 continents
02

Multi-Hop Metric Collection

During the network handshake, our probe records low-level TCP connection states, SSL certificate expiration dates, DNS resolver latency, and initial server compute response times.

Operational Specs
  • DNS, TCP, TLS, TTFB breakdown
  • Payload size & gzip compression ratio
  • SSL expiry counter (days remaining)
03

Consensus Verification Protocol

If an edge node detects a non-200 code or timeout, it does NOT trigger an alert immediately. It initiates a rapid consensus voting round across two neighboring geographic zones on different internet backbones.

Operational Specs
  • Dual-node quorum requirement
  • Zero alerts on single-ISP packet drops
  • Consensus reached in < 3 seconds
04

Root-Cause Capture & Triage

When an incident is confirmed, Stillpoint automatically snapshots an MTR traceroute, saves raw HTTP response headers, extracts error traces, and generates a ready-to-run curl command for your developers.

Operational Specs
  • Automated traceroute packet loss map
  • HTTP response body preview
  • Instant curl reproduction snippet
05

Smart Escalation & Noise Reduction

Alerts are dispatched strictly according to your team’s on-call rotation. Cascade notifications from Slack to SMS or PagerDuty if the incident isn’t acknowledged within your designated SLA threshold.

Operational Specs
  • Slack, Discord, PagerDuty, Webhooks
  • Cooldown periods prevent spam storms
  • Auto-recovery resolution notices
CONSENSUS DEMONSTRATION [SAMPLE DATA]

Simulate the consensus state machine

Click through the lifecycle phases below to observe how our consensus algorithm evaluates anomalies before alerting your on-call team.

daemon-consensus-stream.log
State: Healthy
[14:30:00 UTC] PROBE -> https://api.example.com/health: HTTP 200 OK (138ms). TLS 1.3 cert valid for 64d. Quorum check: ALL_HEALTHY.
Target: https://api.example.com/health • Probed every 10s • Sample audit trace
GLOBAL PRESENCE

18 distributed points of presence

Our probes run on bare-metal and edge compute in Tier-1 carrier facilities across North America, Europe, Asia Pacific, and Latin America.

N. Virginia
us-east-1 • AS16509 AWS
Online
12 ms ping
Oregon
us-west-2 • AS16509 AWS
Online
24 ms ping
Frankfurt
eu-central-1 • AS16509 AWS
Online
18 ms ping
London
eu-west-2 • AS16509 AWS
Online
15 ms ping
Tokyo
ap-northeast-1 • AS16509 AWS
Online
22 ms ping
Singapore
ap-southeast-1 • AS16509 AWS
Online
29 ms ping
Sydney
ap-southeast-2 • AS16509 AWS
Online
34 ms ping
São Paulo
sa-east-1 • AS16509 AWS
Online
42 ms ping
Note: Latencies shown are sample network diagnostics.
RELIABLE MONITORING

Reliability monitoring without the complexity.

Add your endpoints and get instant observability from 18 global edge locations.