Conversion from 5 Kibioctets per second to Terabits per second

=

Invert

Formula to convert Kibioctets per second (Kio/s) to Terabits per second (Tbit/s)

More information

Kibioctets per second to Terabits per second conversion table

Kibioctets per second (Kio/s)Terabits per second (Tbit/s)
1 Kibioctet per second0.000000008192 Tbit/s
2 Kibioctets per second0.000000016384 Tbit/s
3 Kibioctets per second0.000000024576 Tbit/s
4 Kibioctets per second0.000000032768 Tbit/s
5 Kibioctets per second0.00000004096 Tbit/s
10 Kibioctets per second0.00000008192 Tbit/s
20 Kibioctets per second0.00000016384 Tbit/s
25 Kibioctets per second0.0000002048 Tbit/s
50 Kibioctets per second0.0000004096 Tbit/s
100 Kibioctets per second0.0000008192 Tbit/s

Data-transfer rate reference points

ReferenceKibioctets per second (Kio/s)Terabits per second (Tbit/s)
A dial-up modem6.83594 Kio/s0.000000056 Tbit/s
Typical home broadband12207 Kio/s0.0001 Tbit/s
Gigabit Ethernet122070 Kio/s0.001 Tbit/s
Streaming a 4K film3051.76 Kio/s0.000025 Tbit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Kibioctet per second (Kio/s)

The kibioctet per second is a unit of data transfer rate equal to 1,024 octets per second, and therefore to 8,192 bits per second. Its symbol is Kio/s. Unlike most of the binary rate units it is genuinely common, because the command-line tools that copy, download and synchronise files have reported in it for decades.

The reason is straightforward. Those tools count what they have moved in blocks, and blocks are powers of two. A program that reads in four-kibioctet pieces and divides the total by elapsed time produces a rate in kibioctets per second, and reporting it in decimal kilooctets would require an extra multiplication for no benefit. The unit is what the arithmetic naturally produces.

Anyone who has watched a file copy on a Unix-like system has seen the figure. Download utilities, archive tools, disc-writing commands and network file transfer programs all report progress in kibioctets or mebioctets per second, and most of them label it correctly with the lowercase i. It is one of the few places where the IEC prefixes are used consistently in everyday software.

For scale, a kibioctet per second moves about a thousand characters of text each second: a short letter in a second, a novel in about ten minutes. It is a rate at which a modern web page will not load in any reasonable time, so seeing it in a progress display usually means something has gone wrong with the connection rather than that the transfer is nearly finished.

The difference from a kilooctet per second is 2.4 per cent, which nobody notices. The value of using the binary unit here is not accuracy but honesty: the number came from a binary computation, and writing it with a binary prefix says so. A reader who wants the decimal figure can convert; a reader given a decimal label for a binary number cannot recover anything.

Comparing the reading with an advertised connection speed requires two steps: multiply by eight to get bits, and adjust by 2.4 per cent for the base. In practice the second step is beneath the noise of any real measurement, and the first is the one that matters.

One kibioctet per second equals 1,024 octets per second, 8,192 bits per second, or 1.024 kilooctets per second.


Information about the Terabit per second (Tbit/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.