bgpreport

Network · data from 2026-11-12

AS212762 Ck IT Solutions

Registry name: CK-IT-AS Casper Krook trading as Ck IT Solutions, NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212762, 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.
2a05:dfc1:5506::/48 Valid Nonecovered by 2a05:dfc1:5500::/40 635 100% 69
146.103.47.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
2a05:dfc1:5503::/48 Valid RIR databaseRIPE 635 100% 69
2a0f:6280:1501::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS212762: RIPE::AS212762:AS-CK-IT-AS. 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 (AS212762 isn't in the set, or no route object for AS212762 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 objectsAS212762 in itNot covered
RIPE::AS212762:AS-CK-IT-AS RIPE4 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-SERV, AS152135:AS-CSSI, AS199746:AS-NEXTSERV 148381,693 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • Route object: none1
  • AS-SET: missing member4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none2a05:dfc1:5506::/48No route object for it. A route object for 2a05:dfc1:5500::/40 with origin AS212762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212762 in the RIR database for the space.635 of 636
AS-SET: missing memberRIPE::AS212762:AS-CK-IT-ASAS212762:AS-CK-IT-AS (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it.
AS-SET: missing memberRIPE::AS212762:AS-CK-IT-ASAS212762:AS-CK-IT-AS (RIPE) lists AS-SERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS212762:AS-CK-IT-ASAS212762:AS-CK-IT-AS (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing memberRIPE::AS212762:AS-CK-IT-ASAS212762:AS-CK-IT-AS (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

Route objects with origin AS212762 whose prefix no peer sees AS212762 announce. Many are kept on purpose (backup routes, space announced only in some places).

109.176.202.0/24RADB, RIPEValid
2a05:dfc1:5500::/40RIPEValid
2a05:dfc1:5501::/48RIPEValid
2a05:dfc1:5502::/48RIPEValid
2a0f:6280:1500::/40RIPEValid

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.