Our Blog
Inside the parallel internet
Lorem ipsum dolor sit amet consectetur. "Parallel internet" sounds like marketing until you look at the dependency list and notice there is nothing on it. That is the whole claim, and it is a claim about procurement as much as about protocol design.
What we own
Nullam sed tellus pharetra egestas vitae. Three things have to be ours for the rest to follow: the address space, the name resolution, and the transport. Rent any one of them and the guarantees underneath collapse into a contract with somebody else.
| Layer | Ours | What renting it would cost |
|---|---|---|
| IP space | Allocated, announced from our own ASN | Provider-visible routing, no control of reassignment |
| DNS root | Own root, own resolvers, no upstream | Every lookup readable by a third party |
| Transport | Wireslammer, built in house | A dependency that can be told to stop shipping |
Sed do eiusmod tempor incididunt ut labore. The table is short on purpose. A long one would be a spreadsheet, and the point is that the list of things that have to be ours is short.
Where the hardware sits
Magna aliqua ut enim ad minim veniam. Twenty-three locations across six continents, all owned rather than leased, which is a slower way to grow and the only way to make the logging claim structural rather than contractual.
Quis nostrud exercitation ullamco laboris. The European footprint went in second and is the denser of the two, for reasons that are about peering rather than about demand.
What it buys
Nisi ut aliquip ex ea commodo consequat. Mostly it buys the ability to answer a question about the network with a fact instead of with a policy. When somebody asks what happens to a query, the answer is a description of a code path, not a description of an agreement.
Duis aute irure dolor in reprehenderit. That is a smaller-sounding benefit than it is.
