Summary

  • Continent 8 combines hosting with public Internet transit and a private exchange for its customers, using its backbone alongside third-party circuits.
  • ARIN, PeeringDB and RIPE NCC routing observations identify AS14537. They establish a public network footprint, not ownership of every facility or a guarantee of service quality.

A game operator needs more than somewhere to put a server. Its service may also need a payment gateway, a supplier's game and a current odds feed. The screen is where those dependencies meet; the network is how they get there. Continent 8 Technologies sells infrastructure for that less visible part of the business.

The company describes a footprint of more than 100 connected locations across Europe, the Americas and Asia, serving regulated online gambling businesses with hosting, connectivity, cloud and cybersecurity. A map conveys the reach. It says much less about what a customer can do once its equipment is installed.

That is where the company's two kinds of connectivity become interesting. One reaches the public Internet. The other connects customers to one another without, according to Continent 8's product description, sending their exchange traffic over it.

One customer, two different journeys

For public connectivity, Continent 8 describes an Internet transit service built around an MPLS backbone, connections to Tier 1 providers at global hubs and local routing. In ordinary terms, this is a way for a customer's network to reach the wider Internet. The company includes inline DDoS mitigation in the offering; this research did not benchmark its performance.

Its Gaming Exchange addresses a different journey: traffic between Continent 8 customers. The company describes a VPN over its backbone, working in conjunction with third-party circuits. It gives payment processing, odds feeds and integration with games providers as uses. The commercial idea is straightforward: putting related businesses within easy network reach of one another can make the hosting relationship more useful.

One detail is easy to misread. The exchange uses public IPv4 addressing for private connectivity. An address drawn from public address space does not mean every packet travels across the public Internet; addressing and the route used to carry traffic are different things.

The physical connection deserves similar care. Continent 8 says the exchange can be delivered on a separate VLAN over an existing Internet port, or through a separate port. A VLAN separates traffic logically. It does not, by itself, create a second cable, a second building entrance or an independent path. For a buyer, that distinction belongs in the service design rather than in an argument over whether the product counts as a network.

The network has a name and a number

The public evidence is unusually helpful here. PeeringDB's network entry identifies Continent 8 Technologies with AS14537 and links it to Continent 8 LLC. ARIN's registration record assigns that autonomous system number to Continent 8 LLC and provides operational contact roles. RIPE NCC's routing observations show the network announcing routes.

These sources answer different questions. ARIN records the registration. PeeringDB supplies operator-maintained interconnection information, including exchange entries such as AMS-IX and LINX LON1. RIS, RIPE NCC's routing collection system, supplies observations of public routing. Taken together, they are a sound basis for identifying the network—not a survey of everything inside it.

That distinction corrects an important error in this article's earlier version. It treated PeeringDB record 3627 as an organisation record and inferred a missing routing identity from unsuccessful checks. Record 3627 is a network; its linked organisation is 3256. The network entry was updated on 12 October, before the original article appeared. The absence claim was not justified.

What the map leaves for the contract

The colocation offering promises a common commercial and technical framework across sites, with features including resilient power and cooling and round-the-clock remote hands. For a business operating in several markets, that common framework is part of the attraction. It can reduce the number of separate supplier arrangements to manage.

It still does not make every site interchangeable. Public routing cannot establish where a particular customer's data is stored, which party owns every circuit or whether a specific deployment meets a regulator's requirements. Nor does a private path warrant an absolute claim of immunity from attacks. Those questions require the relevant design, contractual commitments and evidence of operation.

Continent 8 is therefore more intelligible as a combination of hosting and connections than as a collection of pins on a map. Its public network identity is visible. The useful next question is how the service a customer buys turns that network into dependable links between the businesses on which it relies.

Corrected 27 October 2026: Replaced the incorrect PeeringDB organisation link and the unsupported claim that no routing identity could be verified. This update uses public records captured on 26 October. Original publication date and URL retained.