Help Start here
Network and location
Where your server runs, the network it is on, what every server gets, and how to test the route from your own computer.
Every server we sell runs in one place, on hardware we own and our own network.
The facts#
| Fact | Detail |
|---|---|
| Location | Charlotte, North Carolina, United States |
| Hardware | Ours: bought, racked and looked after by Darkless |
| Network | AS197924, our own. See it on bgp.tools. |
| Our addresses | 31.77.212.0/24 |
| Test address | 31.77.212.1 |
| Port speed | 1 Gbps per server |
| Traffic | Unmetered |
| DDoS mitigation | Layers 3 and 4, included |
| IPv4 | One included with each dedicated server. Ask for more from the server's page. |
| IPv6 | no. Coming soon. |
| Status page | darkless.cloud/status |
Your own server's addresses are on its page: see IP addresses and reverse DNS for a VPS, or Addresses and reverse DNS for a dedicated server. If everything stops at once, look at the status page first.
Test the route yourself#
What counts is the route between you and Charlotte, not the distance on a map. Test from the computer that will talk to the server, not from a website. Before you buy, use our test address, 31.77.212.1; once you have a server, use its own address from the Connect card.
| Tool | What it tells you |
|---|---|
| ping | Your latency, in milliseconds |
| mtr | Every hop on the way, with the loss and latency at each |
Windows
Open Command Prompt or PowerShell. Send twenty pings:
ping -n 20 31.77.212.1To see the route, Windows has pathping, which works like mtr. It takes a few minutes to finish:
pathping 31.77.212.1tracert shows the hops faster, without the loss figures:
tracert 31.77.212.1macOS
Open Terminal. Send twenty pings:
ping -c 20 31.77.212.1mtr isn't built in. With Homebrew, install it:
brew install mtrThen run it. It needs sudo on a Mac:
sudo mtr 31.77.212.1Press q to stop. Without mtr, traceroute 31.77.212.1 shows the hops.
Linux
Open a terminal. Send twenty pings:
ping -c 20 31.77.212.1Install mtr if you don't have it. On Debian or Ubuntu:
sudo apt install mtr-tinyThen run it, and press q to stop:
mtr 31.77.212.1For a report you can paste into a ticket, run it as a fixed number of rounds instead:
mtr --report --report-cycles 100 31.77.212.1Reading the results#
| You see | It means |
|---|---|
| Under about 50 ms | Feels instant, even in a game |
| Over 150 ms | Players will notice |
| Loss at the last hop | A real problem. This is the one that matters. |
| Loss on a middle hop, none after it | Harmless: that router just doesn't answer tests |
| A jump in time that stays for every hop after | Where the route gets slow, often at your own provider |
If the route looks wrong, open a ticket with the mtr report pasted as text, and say where you are testing from. See Get help from a person.
Still stuck? Open a ticket and say which guide you followed.