Back to Dashboard
API v1 · Live
NodeProxies Developer Infrastructure
Server Status API Documentation
Real-time proxy server latency testing and automated best node selection endpoint. Use this endpoint to dynamically route traffic to the lowest-latency NodeProxies server.
HTTP Endpoint
GET
https://nodeproxies.xyz/server-statusCode Examples
Example Implementation (curl)
curl -X GET "https://nodeproxies.xyz/server-status" \ -H "Accept: application/json"
Response Schema Definition
| Field | Type | Description |
|---|---|---|
| status | string | "operational" (all online), "degraded" (some online) or "down". |
| online_count / total_servers | number | How many gateways are online, out of how many. |
| best_server | string | null | Identifier of the fastest online server (e.g. "eu-1"). Returns null if all servers are offline. |
| best_host | string | null | Fully qualified domain name of the fastest server (e.g. "eu-1.nodeproxies.xyz"). |
| best_latency_ms | number | null | Tested round-trip latency in milliseconds for the best server. |
| test_target | string | Target URL pinged during curl benchmark test (http://cp.cloudflare.com/generate_204). |
| last_tested_at | string (ISO 8601) | Exact UTC timestamp when the latency test execution completed. |
| servers | Array<Object> | List of all server test results. See server object structure below. |
Server Object Structure
id: "eu-1" | "eu-2" | "na" | "global"
name: Display name string
host: Domain endpoint e.g. "eu-1.nodeproxies.xyz"
port: 8080 (Integer)
latency_ms: Integer (ms) · Max 6000ms
status: "online" | "dead"
Latency & Status Rules
- Online Status: Assigned when the server responds successfully within 6000ms.
- Dead Status: Assigned if curl times out (≥ 6000ms) or connection is refused. Latency is defaulted to 6000ms.
- Sequential Measurement: Latency pings are run sequentially to prevent socket contention and guarantee accurate individual millisecond readings.