Endpoint Lifecycle

• Endpoints are provisioned during config issuance, each one is valid for 90 days
• Static endpoints may expire or rotate based on usage pattern and jurisdiction flags
• Tier 3 users may manage tunnel lifecycles directly from the dashboard

Zone Assignment Logic

• Signal origin (your IP) influences initial region match
• Referral sponsor may override based on Tier or trust lineage
• Fallback zone applied if no compliant jurisdiction is active for your config

How Verification Works

• Each endpoint is tagged with a jurisdiction stamp and latency range
• Tunnel metadata includes endpoint hash and issuance timestamp
• Revalidation occurs during config reissue or sponsor audit
• Non-verified endpoints (e.g. leaked, repurposed) will be rejected by infrastructure filters

Managing Global Endpoints

• Tier 2+ users may request jurisdiction changes via dashboard or sponsor
• Signal drift may trigger auto-rerouting so check your config metadata
• Use Help Centre → Deployment Zones → Using Dual-Zone Configurations to deploy resilient multi-region tunnels

“Your endpoint is more than an IP, it's a reflection of your trust path through global infrastructure.”