“Up to 1Gbps” is what the plan page says — but what is your seedbox actually doing right now? Here’s how to measure your real seedbox speed properly, why the first number you see is usually misleading, and what each result actually tells you.
The Three Speeds That Get Confused
Most “my seedbox is slow” confusion comes from mixing up three different measurements:
- Torrent speed — how fast your seedbox downloads from (and uploads to) the swarm. Depends mostly on seeders, not on your plan.
- Seedbox line speed — what the server’s connection can actually push. This is what “up to 1Gbps” refers to.
- Retrieval speed — how fast you can pull finished files from the seedbox to your home machine. Capped by your home connection, not the seedbox.
Test them separately, or the numbers will lie to you.
Test 1: Torrent Speed (the swarm test)
Add a well-seeded test torrent — a Linux distribution like Ubuntu or Debian is perfect because thousands of fast peers seed it. In ruTorrent, Deluge, qBittorrent or Transmission (all one-click installs on Iseedfast), watch the download rate settle for a minute or two.
On a healthy 1Gbps seedbox, a popular Linux ISO typically saturates at tens of MB/s — the whole file lands in a minute or two. Remember the unit trap: torrent clients report megabytes per second, plan pages advertise megabits. 1Gbps ≈ 125MB/s theoretical ceiling; anything above ~40–60MB/s on a single public torrent is your swarm limiting you, not the server.
Test 2: Line Speed (the HTTP test)
Torrents can’t tell you the line’s ceiling because swarms rarely max it. For a raw line test, download a known test file from a fast mirror to the seedbox over SSH:
wget -O /dev/null http://speedtest.tele2.net/1GB.zipwget prints a steady MB/s figure with no disk or swarm involved (writing to /dev/null skips the disk on purpose). This is the cleanest “is the server’s pipe healthy?” number you can get.
Test 3: Retrieval Speed (seedbox → you)
Download a finished file from the seedbox over SFTP/FTP with a client that supports multiple parallel connections (FileZilla or lftp with segmented transfers). Two things to know:
- The result is capped by your home downstream. A 100Mbps home line will never see more than ~12MB/s no matter how fast the seedbox is.
- A single connection over a long distance is always slower than several in parallel — that’s TCP physics, not a seedbox fault. Use 4–8 parallel segments before concluding anything.
Reading Your Results Honestly
| Symptom | What it means |
|---|---|
| Linux ISO fast, your torrent slow | The swarm is the bottleneck (few/slow seeders) — no plan upgrade fixes that |
| HTTP test fast, all torrents slow | Client configuration or tracker issue — see why is my seedbox slow? |
| Everything fast on-box, retrieval slow | Your home line or single-connection transfer — parallelize, or it’s simply your ISP speed |
| HTTP test itself slow | Genuine server-side problem — open a ticket, that’s what support is for |
Frequently Asked Questions
Why does my seedbox never show 1Gbps on a torrent?
Because a torrent is only as fast as the peers feeding it. “Up to 1Gbps” is the line, not a per-torrent promise — no provider’s swarm downloads run at line rate all the time, whatever the marketing implies. Well-seeded content gets close; obscure content never will.
Is a browser speed test on my PC a valid seedbox test?
No — that measures your home connection. The seedbox’s speed has to be measured from the seedbox itself (Tests 1 and 2 above).
Do I need 10Gbps instead?
For most users, no — we wrote up the honest math in do you need a 10Gbps seedbox?. A 1Gbps box that’s actually healthy beats a 10Gbps badge on a congested server.
What speeds do Iseedfast plans get?
All plans — from the $3 plan up — run on connections up to 1Gbps with unlimited downloads. See the fast seedbox page for what that means in practice, or grab a plan and test it yourself; there’s a 7-day money-back guarantee.