| Terabits per second (Tbit/s) | Kibibits per second (Kibit/s) |
|---|---|
| 1 Terabit per second | 976562500 Kibit/s |
| 2 Terabits per second | 1953125000 Kibit/s |
| 3 Terabits per second | 2929687500 Kibit/s |
| 4 Terabits per second | 3906250000 Kibit/s |
| 5 Terabits per second | 4882812500 Kibit/s |
| 10 Terabits per second | 9765625000 Kibit/s |
| 20 Terabits per second | 19531250000 Kibit/s |
| 25 Terabits per second | 24414062500 Kibit/s |
| 50 Terabits per second | 48828125000 Kibit/s |
| 100 Terabits per second | 97656250000 Kibit/s |
| Reference | Terabits per second (Tbit/s) | Kibibits per second (Kibit/s) |
|---|---|---|
| A dial-up modem | 0.000000056 Tbit/s | 54.6875 Kibit/s |
| Typical home broadband | 0.0001 Tbit/s | 97656.2 Kibit/s |
| Gigabit Ethernet | 0.001 Tbit/s | 976562 Kibit/s |
| Streaming a 4K film | 0.000025 Tbit/s | 24414.1 Kibit/s |
The terabit per second is a unit of data transfer rate equal to a thousand gigabits per second. Its symbol is Tbit/s. It is the unit of the internet's backbone: the submarine cables, the exchange points and the long-haul optical links that carry traffic between continents.
A single modern transoceanic cable carries several hundred terabits per second. It achieves this not with one enormous channel but with wavelength division multiplexing, which sends dozens of separate colours of light down each fibre at once, and with several fibre pairs in the same cable. Each wavelength carries a few hundred gigabits, and the totals add up.
The historical comparison is worth stating plainly. The first transatlantic telephone cable, laid in 1956, carried thirty-six simultaneous voice calls. A cable laid in the 2020s carries hundreds of terabits per second, enough for hundreds of millions of simultaneous calls. That is a factor of roughly ten million in seventy years, and it was achieved almost entirely by changing what is sent down the glass rather than by laying more cable.
Internet exchange points, where networks meet and hand traffic to one another, publish their throughput in terabits per second. The largest in Europe and Asia peak in the tens of terabits, and those public graphs are among the most reliable measurements of how heavily the internet is being used at a given moment, because they count real traffic rather than capacity.
In octets, a terabit per second is 125 gigaoctets per second — the contents of a large laptop's disc moved every second, continuously. No single storage system can feed such a link; the traffic on these routes is the aggregate of millions of separate connections, each of them tiny by comparison.
Laboratory records go far higher, into petabits per second, using multi-core fibre and hundreds of wavelengths at once, though over short distances under controlled conditions. The gap between what is demonstrated in a laboratory and what is deployed under an ocean has historically been about a decade.
One terabit per second equals 1,000 gigabits per second, 125 gigaoctets per second, or about 0.9095 tebibits per second.
The kibibit per second is a unit of data transfer rate equal to 1,024 bits per second. Its symbol is Kibit/s. It is the binary counterpart of the kilobit per second, and it is the least used member of an already unusual family, because transfer rates are one of the few places in computing where the decimal convention has always been unambiguous.
Networking has counted in true thousands from the beginning. A modem rated at 56 kilobits per second meant fifty-six thousand, not fifty-seven thousand three hundred and forty-four. The reason is that a transmission rate is set by a clock, and clocks are specified in decimal frequencies: a link running at ten million symbols per second carries a decimal number of bits, not a power of two.
The binary prefixes exist for quantities, not for rates, because quantities of storage are organised in powers of two while time is not. There is no natural reason for a rate to be a power of two, and consequently no reason for a rate unit to need a binary prefix. Where one appears, it is almost always because a program divided a binary file size by a duration.
That is exactly where the kibibit per second does turn up. A tool that measures a transfer by counting kibioctets and dividing by seconds produces a rate in kibioctets per second, and multiplying by eight gives kibibits per second. The unit is a consequence of the arithmetic rather than a description of the channel.
For scale, a kibibit per second is 128 octets per second, and the difference from a kilobit per second is 2.4 per cent — smaller than the measurement error of almost any real throughput test. At this level the distinction is technically correct and practically invisible, which is a fair description of the whole binary prefix system at its lower end.
The unit is properly defined and a converter must handle it, because the IEC series applies to every unit without exception. Whether anyone writes it is a separate question from whether it means something definite, and it does.
One kibibit per second equals 1,024 bits per second, 128 octets per second, or 1.024 kilobits per second.