bgpreport

Network · data from 2026-11-12

AS31055 Consultix

Registry name: CONSULTIX-AS Consultix GmbH, DE · PeeringDB

33IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS31055, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31055, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
62.168.192.0/19 Valid RIR databaseRIPE 673 100% 66
62.168.192.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.193.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.194.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.195.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
62.168.196.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
62.168.197.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 66
62.168.198.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.199.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
62.168.200.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.201.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.202.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.203.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.204.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.205.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.206.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.207.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.208.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.209.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.210.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.211.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.212.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.214.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.215.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.216.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.217.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.218.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.219.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.220.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.221.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.222.0/24 Valid RIR databaseRIPE 673 100% 66
62.168.213.0/24 Valid RIR databaseRIPE 671 100% 66
62.168.223.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS31055: as-consultix. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS31055 isn't in the set, or no route object for AS31055 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS31055 in itNot covered
as-consultix RIPE 81110 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS31055 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.