> ## Documentation Index > Fetch the complete documentation index at: https://docs.xerobi.com/llms.txt > Use this file to discover all available pages before exploring further. # Latency Test > Measures network latency (ping) to the test server. This is a single round-trip time measurement. **Use Cases:** - Quick latency check - Network responsiveness testing - Real-time gaming suitability **Result Storage**: This test result is automatically stored with a unique ID for historical analysis. **Typical Values:** - < 20ms: Excellent (local/CDN) - 20-50ms: Good (regional) - 50-100ms: Fair (cross-region) - > 100ms: Poor (high latency) Measures latency/ping to test servers. Result is stored for historical analysis. ## OpenAPI ````yaml GET /ping openapi: 3.1.0 info: title: Xerobi Speed Test API description: >- A comprehensive network speed testing API with advanced metrics, real-time progress tracking, result history, and comparative analysis. ## Overview The Xerobi Speed Test API provides powerful network performance testing capabilities: - **Basic Metrics**: Individual tests for ping, jitter, download, and upload speeds - **Advanced Tests**: Multi-file testing for more accurate measurements - **Full Speed Tests**: Comprehensive analysis with quality scoring - **Real-time Monitoring**: Server-Sent Events (SSE) for live progress tracking - **Historical Data**: Store and retrieve test results with statistics - **Comparative Analysis**: Compare results over time - **Server Selection**: Test against specific servers ## Authentication Most endpoints require the `Xerobi-Version` header: ```bash curl -H "Xerobi-Version: 2.0.0" \ https://api.hixbe.com/speedtest/full ``` **Exceptions**: The `/` (docs) and `/health` endpoints don't require this header. ## Rate Limits - **Basic endpoints** (ping, download, upload): 60 requests/minute - **Full/Advanced tests**: 10 requests/minute - **Results/Stats endpoints**: 120 requests/minute Rate limit information is included in response headers. ## Test Result Storage Results from these endpoints are automatically stored: - `/ping` - Basic latency tests - `/download` - Download speed tests - `/upload` - Upload speed tests - `/full` - Comprehensive tests - `/advanced` - Advanced multi-file tests Each stored result receives a unique ID for later retrieval. ## Quality Score Calculation The quality score (0-100) is calculated based on: - **Ping** (30%): < 20ms = excellent, < 50ms = good, < 100ms = fair - **Jitter** (20%): < 5ms = excellent, < 15ms = good, < 30ms = fair - **Download** (25%): Relative to expected speeds - **Upload** (20%): Relative to expected speeds - **Packet Loss** (5%): 0% = perfect, < 1% = excellent, < 5% = acceptable ## Server-Sent Events (SSE) The `/stream` endpoint provides real-time progress updates: ```javascript const eventSource = new EventSource('/speedtest/stream', { headers: { 'Xerobi-Version': '2.0.0' } }); eventSource.addEventListener('ping', (e) => { const data = JSON.parse(e.data); console.log('Ping:', data.result, 'ms'); }); eventSource.addEventListener('finish', (e) => { const data = JSON.parse(e.data); console.log('Complete:', data.result); eventSource.close(); }); ``` ## Best Practices 1. **Use appropriate test types**: Use basic tests for quick checks, advanced tests for accuracy 2. **Handle rate limits**: Implement exponential backoff for retries 3. **Store results**: Use result IDs to track performance over time 4. **Compare wisely**: Use `/comparison` and `/stats` for trend analysis 5. **Real-time updates**: Use `/stream` for UI progress indicators 6. **Server selection**: Use `/servers` to find optimal test servers ## Support - Website: https://hixbe.com - Documentation: https://docs.hixbe.com/speedtest - Status: https://status.hixbe.com version: 2.0.0 contact: name: Xerobi Support url: https://hixbe.com email: support@xerobi.com license: name: MIT url: https://opensource.org/licenses/MIT servers: - url: https://api.hixbe.com/speedtest description: Production server security: [] tags: - name: Information description: API information, documentation, and health checks - name: Basic Metrics description: Individual speed test metrics (ping, jitter, download, upload) - name: Advanced Tests description: Comprehensive and multi-file speed tests for accuracy - name: Results & History description: Retrieve stored test results with filtering and statistics - name: Real-time description: Real-time test monitoring via Server-Sent Events (SSE) - name: Servers description: Test server management and selection paths: /ping: get: tags: - Basic Metrics summary: Latency Test description: >- Measures network latency (ping) to the test server. This is a single round-trip time measurement. **Use Cases:** - Quick latency check - Network responsiveness testing - Real-time gaming suitability **Result Storage**: This test result is automatically stored with a unique ID for historical analysis. **Typical Values:** - < 20ms: Excellent (local/CDN) - 20-50ms: Good (regional) - 50-100ms: Fair (cross-region) - > 100ms: Poor (high latency) operationId: getPing parameters: - $ref: '#/components/parameters/HixbeVersion' responses: '200': description: Latency measurement completed successfully headers: X-RateLimit-Limit: schema: type: integer description: Maximum requests per minute example: 60 X-RateLimit-Remaining: schema: type: integer description: Requests remaining in current window example: 59 X-RateLimit-Reset: schema: type: integer description: Unix timestamp when limit resets example: 1733569860 content: application/json: schema: $ref: '#/components/schemas/PingResponse' example: success: true timestamp: '2025-12-07T10:30:00.000Z' data: ping: 25.5 unit: ms id: 1 executionTime: 26ms '400': $ref: '#/components/responses/MissingVersionHeader' '429': $ref: 39b25672-2403-4c5d-9194-56ae3fea1725 '500': $ref: 48df11c3-12e7-4b5c-965c-acb0684491d2 components: parameters: HixbeVersion: name: Xerobi-Version in: header description: API version header. Required for all endpoints except / and /health required: true schema: type: string pattern: ^\d+\.\d+\.\d+$ example: 2.0.0 schemas: PingResponse: type: object properties: success: type: boolean example: true timestamp: type: string format: date-time data: type: object properties: ping: type: number description: Latency in milliseconds example: 25.5 minimum: 0 unit: type: string enum: - ms example: ms id: type: integer description: Result ID for historical retrieval example: 1 required: - ping - unit - id executionTime: type: string required: - success - timestamp - data Error: type: object properties: success: type: boolean example: false timestamp: type: string format: date-time error: type: object properties: code: type: string example: INVALID_REQUEST message: type: string example: Invalid request parameters details: type: object nullable: true responses: MissingVersionHeader: description: Missing Xerobi-Version header content: application/json: schema: $ref: '#/components/schemas/Error' ```` ## Related topics - [Latency Variance Test](https://docs.xerobi.com/speed-api/endpoint/latency-variance.md) - [Jitter Test](https://docs.xerobi.com/speed-api/endpoint/jitter-test.md) - [Xerobi Speed Test API](https://docs.xerobi.com/speed-api/introduction.md) - [Speed Test Server](https://docs.xerobi.com/more/speed-test.md) - [Full Speed Test](https://docs.xerobi.com/speed-api/endpoint/full-test.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.