Which official Looking-Glass hostnames does PingBench list for Vultr APAC?
PingBench indexes sgp-ping.vultr.com (Singapore), hnd-jp-ping.vultr.com (Tokyo), and sel-kor-ping.vultr.com (Seoul) for direct pre-deployment MTR probing.
All specifications on PingBench are derived deterministically from upstream documentation and public vendor pricing retrieved 2026-11-12; validate workload-specific disk IOPS and network latency directly on your target instance before production cutover.
PingBench Specification Profile: Vultr High Frequency NVMe & Public Looking-Glass Endpoints
On PingBench, we highlight Vultr High Frequency NVMe ($6.00/mo to $24.00/mo hourly-capped rates retrieved 2026-11-12) because Vultr publishes live Looking-Glass endpoints in Singapore (sgp-ping.vultr.com) and Tokyo (hnd-jp-ping.vultr.com).
This PingBench profile references official vendor specifications retrieved 2026-11-12 (https://www.vultr.com/pricing/) and remains noindexed pending raw ISP telemetry.
PingBench Published Hardware & Billing Summary (Vultr)
| Specification Axis | Published Vendor Specification (2026-11-12) |
|---|---|
| Compute / RAM | 1–12 vCPU (3.8GHz+) / 1–48 GB RAM |
| Storage Subsystem | 32–768 GB Local NVMe |
| Network / Transfer | 1–8 TB Hourly Billing |
| Published Entry Rate | From $6.00/mo |
PingBench Recommended Post-Provisioning CLI Probe
mtr -rwzc 100 sgp-ping.vultr.com && mtr -rwzc 100 hnd-jp-ping.vultr.comPingBench Review of Published 3.8GHz+ Clock & Hourly Billing Specs
Vultr official documentation specifies 3.8GHz+ high-clock processors paired with local NVMe storage and hourly billing caps, allowing sysadmins to spin up test instances across Singapore, Tokyo, or Seoul and destroy them after verification.
PingBench Pre-Purchase Looking-Glass MTR Verification Steps
Before spending a cent, run mtr -rwzc 100 sgp-ping.vultr.com and mtr -rwzc 100 hnd-jp-ping.vultr.com from your production ISP line to compare southward AAG/SJC routing against northbound APG/SJC2 paths.