Skip to main content
The network log answers a question you can’t answer from inside an untrusted sandbox: what did it actually reach on the network? Every outbound HTTP and HTTPS connection to a public address on ports 80 and 443 passes through Superserve, so the log is recorded by the platform — code inside the sandbox can’t see it or tamper with it.

Two kinds of rows

Each event has a kind:
  • connection — a raw outbound connection. Carries the host (or dstIp), a verdict, and byte counts. This is every HTTP or HTTPS connection the sandbox opened to a public address on ports 80 and 443, whether or not a secret was involved. Attempts at private, link-local, or loopback addresses are dropped before they reach the log.
  • request — an HTTPS request handled by the Superserve credential proxy. When a sandbox has secrets bound, the proxy handles its HTTPS requests, including requests that carry no secret. Carries method, path, and status. secretId is present only when the proxy attached a secret to the request. errorCode is present when the proxy refused or failed the request itself.
Fields that don’t apply to a row’s kind are omitted.

Verdicts

Every connection row has a verdict: matchRule names the rule behind a blocked connection — a useful signal for catching when a sandbox tried to reach somewhere you didn’t expect.

Filtering

Narrow by verdict, or to a time window:
A verdict filter returns only connection rows — request rows have no verdict. When a sandbox has secrets bound, the proxy refuses an HTTPS request to a host your network rules don’t allow with a request row (status 403, errorCode host_not_allowed). verdict: "blocked" does not return that row.
To see everything that was denied, page through the unfiltered log and keep both kinds:

Query parameters

Pagination

The log is cursor-paginated, newest first. Pass nextCursor as before while hasMore is true:

What the log does and doesn’t capture

The log records what the sandbox sent. It does not record work a third party does on the sandbox’s behalf — if an agent calls an LLM that itself runs a web search server-side, you’ll see the one request to the LLM, not the searches it ran on its own infrastructure. Those packets never left your sandbox. It covers HTTP and HTTPS egress on ports 80 and 443. DNS resolution, raw non-HTTP sockets, other ports, and the platform’s own drops of private, link-local, and loopback addresses happen below this log and aren’t recorded in it. The log keeps the last 7 days. Older rows are dropped on a rolling basis; page the API if you want to keep a longer history elsewhere.
Pair the network log (what was reached) with network rules (what’s allowed) and secrets (credentials attached to outbound requests) for end-to-end control and visibility over a sandbox’s network.