Skip to content

Network policy

Network Policy

Our own network. Peering, transit, traffic handling, no-logging commitments.

[ OUR OWN ASN · NO DPI · NO INJECTION · RTBH-CAPABLE · PEERING WELCOME ]

Autonomous system

network    our own ASN · our own IP space
IRR / RIR  registry object published
upstream   redundant transit · BGP failover
edge       fiber where available · cellular bonding · satellite backup

Traffic handling

  • · No deep packet inspection (DPI) on customer traffic.
  • · No throttling by protocol, destination, or content.
  • · No injection of ads, trackers, or content.
  • · DDoS mitigation at the IP / port level only — not content.
  • · RTBH (remote-triggered black-hole) on operator request.

Logging posture

WE DO NOT LOG:

  • · Customer traffic content / payload
  • · DNS queries originating from customer VPS
  • · Destination IPs of customer-initiated connections
  • · NetFlow / sFlow records for customer traffic

WE DO RETAIN:

  • · Aggregate bandwidth (per-port, not per-customer) · 90 days
  • · BGP route + peering state (operational)
  • · DDoS event log (source IPs of attacks)
  • · Admin auth (SSH, API) · 30 days

Encryption

  • · Management plane: SSH, TLS 1.3
  • · At rest: LUKS / dm-crypt
  • · Inter-site tunnels: WireGuard / IPsec
  • · We do not hold or escrow customer keys.

Peering and abuse

Peering inquiries: peering@sovereignhybridcompute.net
Abuse: abuse@sovereignhybridcompute.net
Law enforcement: requires valid legal process. Since we don't log customer traffic content, most requests cannot be fulfilled — by design.

─── Last updated 2026-05-12