Why real phones
A monitor next to your server can't see what your users feel
We ran Radar on our own RPC first. The node was healthy the whole time, yet real phones waited far longer than a server check would ever show. Most of the time went on crossing the internet to our server in the UK.
Looks perfect. Every check passes.
The real average wait, and 2.3% of checks lost to timeouts and network errors on users' connections.
What you get
Uptime and speed, measured where your users are
Checks from real devices
Opted-in Android phones check your endpoint up to four times a day each, on their everyday networks.
Success rate and failure types
Every check is a success, a timeout or a network error, so you can tell one bad connection from an outage.
Response time users feel
Timed on the phone from request to answer, and split by Wi-Fi and mobile data.
Block height in every check
Each answer carries the block number, so a node that falls behind stands out.
A clear report and raw data
A report like our pilot report, plus a CSV file of every check.
Private by design
Testers share no location, device model or wallet data. Your endpoint only gets a read-only call.
How it works
Three steps, nothing to install on your side
Send us your endpoint
A public JSON-RPC URL over HTTPS. Radar sends one read-only call, eth_blockNumber. No keys, no transactions.
Phones check it
Testers who choose to join partner checks run them in the background, on Wi-Fi or mobile data, never while roaming.
You get the numbers
At the end of the week you get the report and the raw data, and we go through it with you on a short call.
Who it's for
Teams whose users are on phones
Early access
A free one-week pilot for the first 5 teams
See your own endpoint through real phones for seven days, before you decide anything.
Or write to radar@magnitudenetwork.tech
- 7 days of checks from real phones on Wi-Fi and mobile data, free.
- A full report and raw data at the end of the week, and a short call to go through them.
- What we ask: honest feedback, and permission to share a short summary of the results, with or without your name.
- After the pilot: paid plans. Pilot teams keep founding pricing.
Today and next
What Radar does today, and what comes next
Today Live
- Android phones on Wi-Fi and mobile data
- EVM JSON-RPC endpoints over HTTPS
- Results split by network type
- 46 active phones in our pilot, and growing
Coming next Planned
- Results by country
- More check types: REST APIs and websites
- Alerts when failures spike
- More phones in more places
Questions
Common questions
Will Radar add load to our endpoint?
Hardly any. Each phone sends at most four small read-only requests a day. With 50 phones that is about 200 requests a day.
What do testers share with us?
Only what the check measures: whether it worked, how long it took, the block number and the network type (Wi-Fi or mobile data). No location, device model, account or wallet data. Testers opt in and can switch Radar off at any time.
Which endpoints can you check?
Any public EVM JSON-RPC endpoint over HTTPS during early access. Tell us in your email if you need something else, such as a REST API.
How many phones will check our endpoint?
Partner checks run on the testers who choose to join them. Our own pilot had 46 active phones, and we will tell you the number for your pilot before it starts.
How is this different from a normal uptime monitor?
Uptime monitors run in data centers with fast, stable connections. Radar runs on the phones and networks real users have, so it shows the delays and failures they actually get.
Want to see your network from real phones?
5 pilot spots, one week each, free.