OwnNetInfrastructure Ltd.
Subscriber Portal
Network

European edge mesh

Three gateway regions currently form the OwnNet ingest fabric. Each gateway terminates TLS 1.3 locally, validates the tenant envelope and writes only to infrastructure inside the same jurisdiction.

1 region operational 2 regions provisioning Anycast front door

Gateway topology

Provisioning nodes accept no production traffic until the compliance and key-custody acceptance checks complete.

Gateway registry

Status observed from the control plane. Latency is measured from the gateway to the regional ingest store.
Region Hostname IPv4 Protocol Status Endpoint
SE-Stockholm-01 gw-se.ownnet.club 70.34.216.222 TLS 1.3 / H2 Active gw-se.ownnet.club
NL-Amsterdam-01 gw-nl.ownnet.club 70.34.216.222 TLS 1.3 / H2 Provisioning —
DE-Frankfurt-01 gw-de.ownnet.club 70.34.216.222 TLS 1.3 / H2 Provisioning —

Ingest path

Agents open a persistent WebSocket over TLS 1.3. Frames are batched, compressed and acknowledged per window; nothing is deleted client-side until the gateway confirms the write.

Failover policy

Each agent keeps an ordered buffer and a ranked candidate list. On two missed probes the agent re-anchors to the next region and replays from the last acknowledged offset.

Capacity policy

Gateways shed load by protocol class rather than tenant, so a burst from one workload cannot starve metric and log streams from the rest of the estate.

Need a region we do not cover yet?

Tell us your residency requirements and we will map the nearest compliant gateway.

Talk to infrastructure team