Observed traffic

The network view shows what actually talked to your components — and what they talked to. Review it, then allow or block with one click.

What you see

Every stage records its real traffic: inbound connections to your routes and outbound connections your components make. Each flow is enriched so it's readable at a glance — country, network and hostname instead of a bare IP.

Allow and block

Any observed destination can be blocked directly from its row, and a blocked one allowed again. Blocks take effect on the outpost itself, so they hold even for traffic that never crosses the hub.

Outbound allowlists

For stages that should only ever talk to known destinations, give the stage an explicit outbound allowlist. Everything outside the list is refused at the node — a compromised dependency can't quietly phone home. Allowlisted destinations are also excluded from security-sensor noise, so alerts stay meaningful.