Skip to content
LIVCK Cloud
Our measurement network

9 locations. 9 independent networks.

We measure from our own locations on separate carriers — exactly one network per location. If you want to check whose network sees your traffic, every operator is named here.

9
measurement locations
9
independent networks
6
countries
8/9
in the EEA or under an adequacy decision

Where we measure — and who runs the network

One location, one operator — none appears twice. The network ID is shown on every entry.

  • ViennaAustrianetcupAS197540
  • GenevaSwitzerlandInfomaniakAS29222
  • CologneGermanyEmeraldHostAS200482 Network partner
  • Enge-SandeGermanyWindcloudAS210226
  • FrankfurtGermanydataforestAS58212
  • NurembergGermanyHetznerAS24940
  • HelsinkiFinlandUpCloudAS202053
  • WarsawPolandOVHcloudAS16276
  • New YorkUnited StatesContaboAS40021

Locations we are opening up

We are looking for a carrier here. These locations do not exist yet and count towards no figure on this page.

Why not simply more locations?

Because locations are not the unit that matters. Networks are.

An outage only counts as an outage once several mutually independent networks confirm it. Two locations on the same network cannot do that: they ride one backbone and fail together. So we take exactly one carrier per location — and grow along new networks, not along new cities.

The example the rule rests on

A large European host runs data centres in a dozen cities — all under a single network identifier. Twelve probes there would be twelve votes from one network, which is a false majority. We use exactly one of its locations.

The result: 9 locations, 9 distinct networks, no duplicates. Each location carries its network identifier — verifiable with a public whois query.

Carriers behind our locations

Every operator is also a sub-processor under Art. 28 GDPR and listed in our sub-processor register — the logos link there.

Partner programme

Do you run a network we are missing?

We open up new locations together with regional network operators.

If you run a data centre or your own network in one of the open regions, write to us. Network partners come first on this page and carry the partner badge. Terms depend on the location and the network, so we agree them individually.

Offer a network

What an operator has to bring

  • Its own network identifierYour own ASN, one we do not already have. A second location in the same network gives us no extra vote.
  • Processing under Art. 28A signable data processing agreement and documented technical and organisational measures. Outside the EU, standard contractual clauses and a transfer impact assessment on top.
  • Maintained network objectsA valid abuse contact in the RIR database and RPKI-signed prefixes. We check both ourselves.
  • A reachable abuse deskReports about our probes are forwarded to us rather than acted on unilaterally — so a probe is never shut down without a word.
  • Openness about incidentsWe look at how you handled past security incidents: whether they were published and what changed afterwards.

We assess every candidate against the same criteria. Article 28(1) GDPR obliges us to select only processors providing sufficient guarantees.

Egress IPs The addresses our checks come from — as a plain list or JSON, for firewall allow-lists.Fetch the list The LIVCK bot How to spot our requests in your logs and how to control the frequency.View the bot page Report abuse Problems with our measurement traffic belong with us — not with the data centre operator.Report abuse