Half the latency to Binance
A short path from your terminal to the servers of Binance, OKX, Bitget and Gate — through the Far East instead of Europe. The gain depends on your city — see the table below.
Our own measurements, medians: direct → via PingNitro. By city — estimate below.
Test in 20 seconds
We connect to the exchanges' live trade streams right in your browser and calculate how many milliseconds it takes a trade to reach you. Your clock is checked against Binance's server time. Nothing to install.
| Exchange, BTC stream | Right now | Via PingNitro* |
|---|
* Before you run the test: our measurement of 30 Sep 2026 (median of the BTC trade feed); after the test: a forecast for your connection.
How it works
Crypto exchange servers are in Tokyo. From Russia the usual path runs through Europe — 250–300 ms round trip. We send your terminal's traffic through the Far East instead.
Exchanges only
Only addresses from a closed list of exchanges go through the route. The rest of your internet goes direct.
We can't see your data
Your terminal's connection to the exchange is encrypted (TLS). We can't access your API keys or orders.
Two entry points
The app picks the best entry and switches to the backup one in 10 seconds if something fails.
Measurements by exchange
BTC trade-feed latency, median. Our own measurement, 30 Sep 2026.
| Exchange | Direct | Via PingNitro | Difference |
|---|---|---|---|
| Binance Futures | 144 ms | 78 ms | −66 |
| Binance Spot | 165 ms | 72 ms | −93 |
| OKX | 147 ms | 79 ms | −68 |
| Bitget | 153 ms | 91 ms | −62 |
| Gate | 204 ms | 75 ms | −129 |
| Bybit, BingX | 106 ms | — | direct |
Bybit and BingX run their servers in Singapore — from Russia the direct path to them is shorter, so the app sends them directly, outside the route.
Gain by city
The gain depends on where you connect from. Below is our estimate by city; for your own connection, run the test above.
Estimate for other cities
| Gain of more than 100 ms | Saint Petersburg, Minsk, Almaty, Yerevan |
| Gain of 60–90 ms | Moscow, Yekaterinburg, Istanbul, Tbilisi, Baku |
| Almost no gain | Novosibirsk, the Far East (Vladivostok) |
This is an estimate, not a feed measurement: Globalping, 30 Sep 2026 — TCP connection time to Binance in Tokyo directly vs. time to our node plus the link to Tokyo; median of 1–3 probes per city, a single observation. For your own connection, the test above is more accurate.
Route status
Updated every 2 minutes.
| loading… |
Connect in 2 minutes
Apps for Windows 10/11 and macOS (Apple Silicon, M1–M4); you sign in with Telegram right in the app — no key to enter.
Get the app
Access — in the bot @pingnitrobot or in your account. The Windows installer is there too; for Mac — one command in Terminal or a DMG file.
Install
It starts with the system and runs in the background, alongside your other network programs. In the app window — "Sign in with Telegram".
Set the proxy
In your terminal: HTTP, host 127.0.0.1, port 1081, no login.
Right now — a free test
- All exchanges on the route
- Apps for Windows and macOS
- A short weekly survey in the bot — to renew your access
We'll announce pricing after the test, taking testers' answers about price into account. Testers hear first and get better terms.
FAQ
What goes through PingNitro?
Only exchange addresses go through PingNitro; all other traffic goes direct. We shorten the path to the exchange; please use the exchange under its own rules — its country-specific terms apply as usual.
Can you see my API keys or orders?
No. Your terminal connects to the exchange over TLS; we only pass on the already-encrypted stream.
Which terminals work?
Any terminal that lets you set a proxy: CScalp, Tiger.Trade, Vataga, MetaScalp and others. Setup guides.
Why is a "20 ms ping" to an exchange misleading?
That is the time to the nearest CDN node, while trades happen in Tokyo or Singapore. What matters is when an exchange event reaches you — and that is what the test shows.
What gain will I get from my city?
It depends on the city: from more than 100 ms (Saint Petersburg, Minsk, Almaty, Yerevan) to almost none (Novosibirsk, the Far East). Our measurements and estimates by city are in the table; for your own connection, run the test on this page.
What if the route goes down?
The route has two entry points and three exits in Tokyo. The app switches to the backup entry in 10 seconds (tested on 6 Oct 2026); exits are switched by the node's watchdog. We post incidents in the channel @pingnitro. An app downloaded before 6 Oct 2026 has no backup entry — download it again in the bot.