Traffic Inspector
See every request that reaches your tunnel — method, path, status, latency, size, client IP, and user agent.
The Traffic Inspector shows every request that reaches the edge for your tunnels, in real time. It's the fastest way to confirm traffic is arriving, debug a webhook, or find a heavy endpoint.
Open it under Dashboard → Inspector.
What each request shows
| Field | Description |
|---|---|
| Method | GET, POST, PUT, … |
| Path | The request path, including query string |
| Status | The response status code returned by your service |
| Latency | Time to first byte / total duration in milliseconds |
| Size | Response body size in bytes |
| Client IP | The visitor's source IP |
| User agent | The client that made the request |
| Protocol | HTTP/1.1, HTTP/2, … |
| Host | The tunnel hostname the request hit |
Reading the data
- Confirm traffic is arriving. If a request you expect never appears, it's not reaching the edge — check DNS, the client, and that the tunnel is online.
- Debug webhooks. Watch a provider's deliveries land, inspect the path and
status, and confirm your handler returned
2xx. - Find heavy endpoints. Sort by size to find what's eating bandwidth — large media or unbounded streaming responses are the usual culprits.
- Watch streams in flight. A long-running streaming request shows up in-flight with a climbing latency. That's the stream working, not a stall.
A connection refused on localhost surfaces as a 502 at the edge — if you see
502s in the Inspector, your local service isn't up on that port.
Over the API
The same data is available programmatically. Read recent requests for your account:
curl https://api.osmrouter.com/v1/requests \
-H "Authorization: Bearer $OSM_TOKEN"Each entry includes the method, path, status, duration, byte size, client IP, user agent, and protocol. See the REST API for the full shape.
Retention
Request records are retained for a rolling window (14 days) and then pruned automatically. For longer retention, pull from the API on a schedule and store the results yourself.
Next steps
- Plans & limits — bandwidth and request quotas.
- Streaming — how long-lived requests appear in the Inspector.