ip402.xyz
https://ip402.xyz/v1/geoPaid IP intelligence endpoint returning normalized geolocation and ASN data for a single IPv4 or IPv6 address.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 502ms · p95 1482msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/6/2026, 12:00:00 AM | 100% | 17 | 1142ms |
| 9/7/2026, 12:00:00 AM | 100% | 15 | 1159ms |
| 9/8/2026, 12:00:00 AM | 100% | 20 | 1160ms |
| 9/9/2026, 12:00:00 AM | 100% | 21 | 493ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 1294ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 858ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 496ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 1156ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 1168ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 828ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 1306ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 1152ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 530ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 504ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 822ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 756ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 832ms |
| 9/23/2026, 12:00:00 AM | 100% | 12 | 1150ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 502ms |
| 9/25/2026, 12:00:00 AM | 100% | 14 | 430ms |
| 9/26/2026, 12:00:00 AM | 100% | 13 | 356ms |
| 9/27/2026, 12:00:00 AM | 100% | 14 | 1142ms |
| 9/28/2026, 12:00:00 AM | 100% | 12 | 350ms |
| 9/29/2026, 12:00:00 AM | 100% | 12 | 508ms |
| 9/30/2026, 12:00:00 AM | 100% | 12 | 205ms |
| 10/1/2026, 12:00:00 AM | 100% | 12 | 811ms |
| 10/2/2026, 12:00:00 AM | 100% | 12 | 1132ms |
| 10/3/2026, 12:00:00 AM | 100% | 12 | 814ms |
| 10/4/2026, 12:00:00 AM | 100% | 10 | 675ms |
| 10/5/2026, 12:00:00 AM | 100% | 7 | 203ms |
- Availability
- 100
- Latency
- 98
- Security
- 100
- Transparency
- 42
- Activity
- 19
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base, eip155:5042, eip155:5042002, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- GoDaddy.com, LLC
- Domain registered
- 2026-06-13
- Hosting network
- ORACLE-4
- Hosting country
- IN
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 10/4/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/13/2026 | 1 | 0.01 | 1 |
| 9/14/2026 | 1 | 0.01 | 1 |
| 9/17/2026 | 2 | 0.02 | 2 |
| 9/19/2026 | 3 | 0.03 | 1 |
| 9/20/2026 | 1 | 0.01 | 1 |
| 9/21/2026 | 1 | 0.01 | 1 |
| 9/22/2026 | 1 | 0.01 | 1 |
| 9/23/2026 | 2 | 0.02 | 2 |
| 9/24/2026 | 1 | 0.01 | 1 |
| 9/25/2026 | 1 | 0.01 | 1 |
| 9/27/2026 | 3 | 0.03 | 2 |
| 9/28/2026 | 1 | 0.01 | 1 |
| 9/29/2026 | 4 | 0.04 | 3 |
| 9/30/2026 | 1 | 0.01 | 1 |
| 10/1/2026 | 1 | 0.01 | 1 |
| 10/2/2026 | 2 | 0.02 | 2 |
| 10/3/2026 | 1 | 0.01 | 1 |
| 10/4/2026 | 2 | 0.02 | 2 |
Only payments settled on chains and facilitators we index.