Conversion from 100 Terabits per second to Octets per second

=

Invert

Formula to convert Terabits per second (Tbit/s) to Octets per second (octet/s)

More information

Terabits per second to Octets per second conversion table

Terabits per second (Tbit/s)Octets per second (octet/s)
1 Terabit per second125000000000 octet/s
2 Terabits per second250000000000 octet/s
3 Terabits per second375000000000 octet/s
4 Terabits per second500000000000 octet/s
5 Terabits per second625000000000 octet/s
10 Terabits per second1250000000000 octet/s
20 Terabits per second2500000000000 octet/s
25 Terabits per second3125000000000 octet/s
50 Terabits per second6250000000000 octet/s
100 Terabits per second12500000000000 octet/s

Data-transfer rate reference points

ReferenceTerabits per second (Tbit/s)Octets per second (octet/s)
A dial-up modem0.000000056 Tbit/s7000 octet/s
Typical home broadband0.0001 Tbit/s12500000 octet/s
Gigabit Ethernet0.001 Tbit/s125000000 octet/s
Streaming a 4K film0.000025 Tbit/s3125000 octet/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

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.


Information about the Octet per second (octet/s)

The octet per second is a unit of data transfer rate equal to eight bits per second. Its symbol is octet/s. It is the unit in which software reports transfer speeds, as against the bits per second in which hardware and network services advertise them, and the factor of eight between the two conventions is the source of endless confusion.

The division of labour is consistent once it is understood. Anything describing a physical link — an Ethernet port, a fibre connection, a radio channel, a broadband package — is quoted in bits per second, because bits are what the signalling actually carries. Anything describing a file moving from one place to another is quoted in octets per second, because files are measured in octets.

A download manager that reports 12 megaoctets per second on a connection sold as 100 megabits per second is not disagreeing with the advertisement; it is stating the same rate in the other convention, and the arithmetic between them is a division by eight. Recognising this immediately removes the most common cause of complaint about internet speed.

Individual octets per second appear in the same narrow places as individual bits: deep-space telemetry, low-power sensor links, and the slowest legacy serial connections. A rate of a hundred octets per second would move a page of text in about twenty seconds, which was a normal experience in the 1970s and is unimaginable now.

The unit also underlies the way disc and interface throughput is described. A drive that sustains 500 megaoctets per second is moving four gigabits per second across its interface, and matching the two figures is a routine part of system design: an interface rated in gigabits must be compared with a drive rated in octets, and the factor of eight decides whether one starves the other.

Storage tools reinforce the convention. Every file copy utility, backup program and command-line transfer tool reports in octets per second or its multiples, and every network measurement tool reports in bits per second. A person reading both at once has to keep the conversion in mind, which is exactly what makes the distinction worth stating explicitly.

One octet per second equals 8 bits per second, 0.008 kilobits per second, or 0.001 kilooctets per second.