net // locations · carriers · test endpoints

NETWORK & TEST IPS

Where the servers sit, who carries their traffic, and every address you need to check a route before you order: ping and trace the test IPs, or pull a speed-test file from the location itself.

Get test IPs
aixs net --summary
locations
4 (HKG TYO SIN LAX)
carriers_ix
12
test_endpoints
8 (IPv4 + IPv6)
looking_glass
lg.aixscloud.com
status_page
status.aixscloud.com
// topology

ROUTE MAP

Hover, focus or tap a location to trace its links.

net://topology 4 nodes · 6 links
Illustration

> trace --all

4 locations, 6 measured links. Pick a location to trace its routes.

  • HKG Hong Kong
  • TYO Tokyo
  • SIN Singapore
  • LAX Los Angeles

Moving packets are an illustration, not live traffic. Their pace follows the listed round-trip time.

Prototype values. They are replaced by measured averages, with the measurement date, before launch.

Measured links (round trip)

  • HKG-TYOHong Kong / Tokyo49 ms
  • HKG-SINHong Kong / Singapore34 ms
  • HKG-LAXHong Kong / Los Angeles151 ms
  • TYO-SINTokyo / Singapore69 ms
  • TYO-LAXTokyo / Los Angeles104 ms
  • SIN-LAXSingapore / Los Angeles172 ms
// probe

LATENCY PROBE

Coming with the looking-glass endpoints; until then, test from your own machine.

probe://your-browser

Not switched on yet. The probe goes live together with the looking-glass endpoints, so every number it shows comes from the location itself. Until then, ping the test IPs below from your own machine.

  • HKGHong Kong—Not measured
  • TYOTokyo—Not measured
  • SINSingapore—Not measured
  • LAXLos Angeles—Not measured

Scale: 0 to 200 ms

// test kit

TEST KIT

Ping it, trace it, download from it. Then order in the same location.

// matrix

RTT MATRIX

Round-trip time between our locations and reference points.

  • From HKG Hong Kong

    • TYOTokyo49 ms
    • SINSingapore34 ms
    • LAXLos Angeles151 ms
    • FRAref. pointFrankfurt186 ms

  • From TYO Tokyo

    • HKGHong Kong49 ms
    • SINSingapore69 ms
    • LAXLos Angeles104 ms
    • FRAref. pointFrankfurt228 ms

  • From SIN Singapore

    • HKGHong Kong34 ms
    • TYOTokyo69 ms
    • LAXLos Angeles172 ms
    • FRAref. pointFrankfurt158 ms

  • From LAX Los Angeles

    • HKGHong Kong151 ms
    • TYOTokyo104 ms
    • SINSingapore172 ms
    • FRAref. pointFrankfurt145 ms

Round-trip time in milliseconds, measured from the location in each row. A dash means not measured; values are never filled in from the other direction.

Prototype values. They are replaced by measured averages, with the measurement date, before launch.

Colour bands

  • < 50 ms
  • < 100 ms
  • < 150 ms
  • < 200 ms
  • ≥ 200 ms
// routing 101

ROUTING 101

What the route tags mean, and how to check them yourself.

01 // TRANSIT

Transit

A paid upstream carrier that delivers our traffic to the rest of the internet. More than one transit provider means traffic can take another way out when one has trouble.

02 // PEERING

Peering & IX

A direct exchange with another network, often across an internet exchange (IX). It skips intermediate carriers, which usually means fewer hops and lower latency to that network’s users.

03 // RETURN PATH

Outbound vs return path

Traffic to a server and the reply coming back can take different routes. A good ping from you only shows the round trip; trace both directions (ours via the looking glass, yours with mtr) before judging a route.

Test a route yourself

  1. Run mtr from your own machine to the test IP of the location you are considering.

  2. Run a traceroute back to your IP from our looking glass to see the return path.

  3. Download a speed-test file to check throughput over your actual route.

Demo output with documentation addresses (RFC 5737). Replace the target with a test IP from the kit above.

route-check.sh
demo
# path and loss, 100 probes, no DNS
$ mtr -rwnc 100 203.0.113.80
HOST: your-machine       Loss%   Snt   Last    Avg   Best   Wrst
  1.|-- 192.0.2.1         0.0%   100    0.6    0.7    0.5    1.9
  2.|-- 198.51.100.17     0.0%   100    3.1    3.4    2.8    7.2
  3.|-- 198.51.100.94     0.0%   100   11.8   12.1   11.5   14.0
  4.|-- 203.0.113.1       0.0%   100   34.2   34.6   33.9   38.1
  5.|-- 203.0.113.80      0.0%   100   34.9   35.1   34.5   37.7

# throughput from the looking glass host
$ curl -o /dev/null -w '%{speed_download}\n' https://lg.aixscloud.com/speedtest/hkg-100mb.bin

# iperf3 between two machines you control
$ iperf3 -c 192.0.2.10 -R -t 10

Status & tools

Incidents and maintenance are posted on the status page. The looking glass runs network tests from our locations toward you.

Live status(opens in a new tab)
Status page(opens in a new tab)Looking glass(opens in a new tab)Browse servers