ST multi-IP servers: more addresses do not lower latency

The ST prefix means multi-address delivery in Hong Kong, Tokyo, Los Angeles, Singapore, Taipei, Seoul and Seattle. Latency still follows the path. Do not park the database across a city from the sites.

Multi-IP servers in the current catalog use the ST prefix. ST means the dedicated server is delivered with many addresses, so a group of sites can bind their own. It does not mean lower latency or a larger port. More addresses, same path. Hong Kong multi-IP server HK-ST-E5-2620, Tokyo Japan multi-IP server JP-TYO-ST-E5-2620, Los Angeles US multi-IP server US-LA-ST-E5-2620, Singapore Singapore multi-IP server SG-ST-E5-2620. The same prefix is Taipei multi-IP server, Seoul multi-IP server and Seattle multi-IP server.

Separate jacks on a patch panel

Slow and unreachable are different faults

A long TTFB is the path or an evening queue. A page that fails to open, or opens on only some networks, starts as an address question: blocked, or freshly assigned and not cooled down. Both show up as errors. One wants another line or another city. The other wants another address or time. A larger CPU fixes neither. In one city, put sites on ST and the order or account database on a non-ST box. Hong Kong uses Hong Kong server HK-E5-2620. Tokyo uses Japan server. A database across the public internet turns an address problem into write latency for every site.

DEF is not “ST with more IPs.” Hong Kong DDoS server sells cleaning capacity. Buy ST for addresses. Add DEF on the entrance that needs cleaning. Do not buy DDoS to obtain addresses, and do not wrap every multi-IP address in aggressive cleaning. A strict policy drops normal visitors first, which looks like a sudden latency jump.

Keep one site group in one city

Sites that link to each other and share a login stay on one ST server or in one room. Spread across four countries and every click pays an ocean round trip. Crawlers also see inconsistent response times. A North American group uses Los Angeles or Seattle ST. A mainland group uses Hong Kong or Taipei ST. Sync content between them. Do not share a write ledger. How to read the prefix is Hong Kong model names. Other cities use the same rule. Address planning is the multi-IP plan. Do not put cleaning capacity and address count in one purchase number. See the two DDoS bandwidth figures.

Acceptance has three columns: address count matches the sites you bind, evening TTFB from the visitor network, and the non-ST database still in the same room. Pass all three. A pingable IP is not acceptance.