About

How this site is built, where its data comes from, and what it can and cannot tell you.

Method

Once a day the public Terminal 4 and Terminal 5 broker search is read in full. For every broker it lists the trade servers, their access points, logos, and website. Each access point is an address and port; every address is looked up for its country, city, owning network (AS number), and hosting provider.

Brokers are linked as related when they share a server address, a logo, or a website domain. Each link is graded strong, medium, or weak and always shows its evidence. An address used by a great many brokers is treated as a shared hub and never counts as a link on its own. Groups are clusters of brokers joined by strong and medium links; a very large cluster is re-split on strong links only so distinct groups do not merge into one.

Sources

• Server lists — the public broker search (company names, servers, logos, websites, access points).
• IP geolocation — a free IP-to-city database for country, city, coordinates, and network.
• Published cloud ranges — provider-published address ranges, used to name cloud regions.
• Firm cards — declared regulation and company details, collected in a later pass.

Limits

• Locations are city-level estimates, not specific data centres.
• Regulation is self-declared by brokers and not yet verified against registers.
• Shared hosting suggests a connection but does not prove one.
• The server lists may be incomplete and change daily.
• Nothing here is investment advice or a statement about company ownership.

Data status

The refresh runs daily, each step independently. If a source fails, the last good data is kept and flagged. The Monitor shows recent runs and their durations.

API

A read API mirrors the page filters under /api/v1/. Endpoints include /brokers, /brokers/{slug}, /ip/{address}, /asn/{number}, /locations, /datacenters, /clusters, and /overview. Multi-values are comma-separated; a leading - sorts descending; paging is cursor-based.