Blossom Host
← All notes

Performance · field note

High-speed ISP VPS: what 1 Gbps and 10 Gbps really mean

How to read the speed on an ISP VPS plan: port speed, single-connection limits, shared host routes, and monthly transfer, using Blossom's three US routes.

"High-speed ISP VPS" is one of the easiest phrases in hosting to write and one of the hardest to pin down. A plan can be fast in several different ways, and a single number on a pricing page rarely tells you which one matters for your workload. This note explains the four figures worth reading, using Blossom's three US ISP routes as the worked example.

Four numbers that get called speed

Port speed is the size of the network connection, such as 1 Gbps or 10 Gbps. It sets the ceiling for how quickly data can move in or out at any moment.

Single-connection throughput is what one transfer, such as one download or one proxy session, can actually reach. On many networks this is lower than the port speed, because traffic is spread across links one connection at a time.

Shared versus dedicated tells you whether the port belongs to your server alone or to the physical host that many servers share. Most VPS products, including ours, share the host connection.

Monthly transfer is how much data you can move over a billing month. It is a volume, not a speed. A fast port with a small allowance and a slower port with a large allowance suit very different jobs.

How the three Blossom routes compare

Route Port What that means in practice Monthly transfer
Washington, DC on Verizon 1 Gbps About 940 Mbps down and up on a single connection, measured from the host 1 to 2 TB
Seattle on Astound/Wave 10 Gbps symmetrical host route The most headroom in the line, shared by the servers on the host 1.25 to 3 TB
Odessa, TX on NetWest 1 Gbps A gigabit-class route in the central US 1 to 3 TB

Transfer ranges run from the smallest to the largest orderable tier on each route, from the live catalog on October 20, 2026. Checkout shows the exact figure for the plan you pick.

Why a single connection caps at 1 Gbps

The Washington route is built from two bonded links. Bonding spreads different connections across the links, but it never splits one connection across both. So however many links sit behind the server, any single transfer tops out at 1 Gbps. That is why we describe Washington as gigabit and quote the measured single-connection figure of about 940 Mbps each way, rather than adding the links together.

For proxy-style and automation workloads this is rarely the limit. Those jobs open many small connections, and each one needs only a fraction of a gigabit. Where a single large transfer matters, such as pulling big files from one source, the per-connection ceiling is the number to plan around.

What a 10 Gbps host route does and does not promise

Seattle's 10 Gbps symmetrical connection belongs to the physical host. It gives every server on that host far more shared headroom than a 1 Gbps port would, and the symmetrical part means upload capacity matches download. It is not a dedicated 10 Gbps reservation for each VPS, and no honest provider can promise that a single transfer to a distant site will run at 10 Gbps. The remote end, the path between, and the protocol all have a say.

Speed is not the whole story

Location affects how fast a server feels as much as port size does. A gigabit server close to the service it talks to can beat a faster server across the country, because every round trip is shorter. Pick the route nearest the destinations that matter: Washington for the East Coast, Seattle for the West Coast, Texas for the central US.

Transfer matters too. A server that moves a lot of data every day can use up a small allowance well before the month ends, however fast its port. Size the plan by the data you expect to move, not only by its port. For more on how allowances work, see how VPS resources and transfer allowances work.

Test the path you actually use

A speed test to a nearby, well-provisioned server measures that one path on that one day. It says little about a download from a distant site or a long-lived session to a particular service. After you deploy, test against the destinations your workload really uses, at the times it really runs. Our note on what server tests do and do not prove covers how to read those results.

Choosing a fast ISP route

If raw headroom is the priority, start with Seattle's 10 Gbps host route. If you want an East Coast Verizon address with a measured gigabit single connection, choose Washington. If you need a central US location, choose Texas, where a 3-month or longer term also slots your server for priority compute when it becomes available, with 3x speed, for the first 100 servers. Compare the three routes side by side or see current ISP VPS plans.

Ready when you are

Choose the line that fits the job.

Compare the current plan resources and prices, or ask for a dedicated build when a standard tier is not the right shape.