TokenSwitchThe TokenSwitch network
Real-time edge nodes where provider tunnels connect and shares go live.
24h token usage
SnapshotTokens routed across every region in the last 24 hours, summed from each router's public usage feed.
3 of 5 regions reporting — the total below is a floor. Not reporting: Japan · Hong Kong
Free
freetokenswitch.cc
24h tokens: 253M
Japan
jptokenswitch.cc
Singapore
sgptokenswitch.cc
24h tokens: 0
Hong Kong
hktokenswitch.cc
United States
ustokenswitch.cc
24h tokens: 668M
What a TokenSwitch region actually is
One router per region
Each region runs a single cc-switch-router process. It terminates the public subdomain, holds the reverse SSH tunnels that provider clients dial out to, verifies the signature on every request, and injects the identity context the client trusts. There is no central control plane above it.
Providers keep the credentials
Your Claude, Codex and Gemini credentials never leave the machine running cc-switch-server. The router forwards protocol traffic through the tunnel and stores no upstream API key in plaintext, so a compromised region cannot replay your subscription.
Usage is public, identities are not
The 24h figures above come from each region's public usage endpoint and are pure aggregates: totals, the input/output/cache split, per-model rows, and active share and client counts. No email, share, account or amount is exposed.
Run your own region
Deploy cc-switch-router on your own domain and join the open network.