🔑 Sats4Tokens upstream network
One key, many upstreams. None of them knows who you are, and none of them sees all the traffic.
Loading the routing table…
real request
route preview (sampled from the real routing table)
response
upstream channel
switched off
Where a request goes
Latest real requests
Calls made with Sats4Tokens keys, and the upstream that served each one. Only time, model and node — no key, no content.
Why many upstreams?
Providers are shown as letters (A, B, …), their channels as A1, A2, …: we publish how requests are routed, not who our upstreams are. The routing table is the one the relay really uses — highest priority first, by weight inside a tier, the next tier on failure.