Vultr Speed Test

Archived Vultr datacenter benchmark script. This repository is kept as a historical speed-test utility and data-format reference, not as a live provider ranking or promotion page.

vultr-speed-test measures latency, download speed and optional traceroute results against public Vultr looking-glass endpoints. It can help you understand how a VPS network test script is structured, but old sample results should not be used as current deployment advice.

For current maintained VPS resources, start here:

Need	Maintained Resource
General VPS tools and server resources	awesome-vps-tools
VPS benchmark data structure and methodology	vps-benchmark-hub
BandwagonHost / 搬瓦工 speed test notes	bwg-speed-test

What This Script Does

• Tests ping latency to Vultr datacenter endpoints.
• Downloads public test files to estimate throughput.
• Optionally runs traceroute for route inspection.
• Saves machine-readable JSON results.
• Supports region filters such as asia, us, eu, sa, me, af and all.

Safety And Privacy

Before sharing benchmark results publicly:

• remove your real source IP address;
• remove personal server names, hostnames or account details;
• note the test time, source network and method;
• avoid treating one result as a long-term performance guarantee.

The script now writes "source_ip": "omitted" by default to reduce accidental privacy exposure.

Quick Start

Recommended: clone the repository and review the script first.

git clone https://github.com/devguoo/vultr-speed-test.git
cd vultr-speed-test
chmod +x scripts/vultr-speed-test.sh
./scripts/vultr-speed-test.sh

Historical one-line usage:

bash <(curl -sL https://raw.githubusercontent.com/devguoo/vultr-speed-test/main/scripts/vultr-speed-test.sh)

Usage Examples

# Full test with traceroute
./scripts/vultr-speed-test.sh --traceroute

# Asia-Pacific only
./scripts/vultr-speed-test.sh --region asia

# Save to a custom file
./scripts/vultr-speed-test.sh --output my-results.json

# Use a larger test file
./scripts/vultr-speed-test.sh --size 100MB

Datacenter Endpoints

The script uses public looking-glass style endpoints such as:

City	Region	Endpoint IP
Tokyo	Asia Pacific	108.61.201.100
Osaka	Asia Pacific	149.28.120.10
Singapore	Asia Pacific	45.32.100.168
Seoul	Asia Pacific	45.76.97.100
Los Angeles	North America	108.61.194.100
Silicon Valley	North America	45.32.139.100
New York / NJ	North America	45.63.1.100
London	Europe	45.63.33.100
Frankfurt	Europe	45.77.57.100
Sydney	Asia Pacific	149.28.55.100

Endpoint availability and provider URLs may change. Always verify current looking-glass details with the provider before relying on results.

Historical Sample Data

data/sample-results.json is retained as a format example only. It represents an old anonymous test run and should not be read as a current Vultr performance ranking.

Benchmark results vary by:

• source network and ISP;
• time of day;
• local congestion;
• remote endpoint load;
• route changes;
• test file size and method.

Result Format

{
  "meta": {
    "version": "1.0.0",
    "timestamp": "2026-01-01T00:00:00Z",
    "source_ip": "omitted",
    "source_location": "anonymous test network",
    "ping_count": 10,
    "download_file": "10MB.bin",
    "traceroute": false
  },
  "results": [
    {
      "code": "nrt",
      "city": "Tokyo",
      "region": "asia",
      "ip": "108.61.201.100",
      "ping_avg_ms": "58.3",
      "download_mbps": "312.4"
    }
  ]
}

Repository Status

This repository is archived in practice:

• No live Vultr ranking is maintained here.
• No direct affiliate or referral links are included here.
• New benchmark methodology and cross-provider data should go to vps-benchmark-hub.

License

MIT

Disclaimer

This is an independent community script and is not affiliated with Vultr. Results vary by network, location and time.