bgpreport

Network · data from 2026-11-12

AS12480 ILK Internet

Registry name: ASILK ILK Internet GmbH Rechnerkommunikation im Internet, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12480, 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.

193.141.55.0/24 No ROA RIR databaseRIPE 670 100% 68
194.172.58.0/24 No ROA RIR databaseRIPE 670 100% 68
212.86.208.0/24 Valid Nonecovered by 212.86.192.0/19 670 100% 68
185.149.156.0/22 Valid RIR databaseRIPE 670 100% 68
185.193.144.0/22 Valid RIR databaseRIPE 670 100% 68
194.26.16.0/24 Valid RIR databaseRIPE 670 100% 68
194.45.22.0/24 Valid RIR databaseRIPE 670 100% 68
194.59.13.0/24 Valid RIR databaseRIPE 670 100% 68
194.120.173.0/24 Valid RIR databaseRIPE 670 100% 68
194.174.11.0/24 Valid RIR databaseRIPE 670 100% 68
212.86.192.0/19 Valid RIR databaseRIPE 670 100% 68
2a00:1970::/32 Valid RIR databaseRIPE 636 100% 67
2a11:9400::/32 Valid RIR databaseRIPE 635 100% 67
194.121.203.0/24 Valid RIR databaseRIPE 511 76% 66

AS-SET

PeeringDB's irr_as_set for AS12480: RIPE::AS-ILK. 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 (AS12480 isn't in the set, or no route object for AS12480 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 objectsAS12480 in itNot covered
RIPE::AS-ILK RIPElists itself further down1 member set in no database: AS-ASKNET 8840 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 17 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • AS-SET: missing member1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none193.141.55.0/24No ROA covers it. Add a ROA for AS12480, maxLength 24.670 of 673
ROA: none194.172.58.0/24No ROA covers it. Add a ROA for AS12480, maxLength 24.670 of 673
Route object: none212.86.208.0/24No route object for it. A route object for 212.86.192.0/19 with origin AS12480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12480 in the RIR database for the space.670 of 673
AS-SET: missing memberRIPE::AS-ILKAS-ILK (RIPE) lists AS-ASKNET; no IRR database read has it.

Route objects not announced

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

91.201.100.0/22RIPEValid
91.220.159.0/24RIPEInvalid: origin
91.221.120.0/23RIPEInvalid: origin
91.221.120.0/24RIPEInvalid: origin
91.221.121.0/24RIPEInvalid: origin
193.101.11.0/24RIPEValid
193.101.24.0/21RIPEValid
194.76.193.0/24RIPEValid
194.120.43.0/24RIPEValid
194.143.156.0/23RIPEValid
195.42.114.0/24RIPENo ROA
195.42.115.0/24RIPEValid
2001:470:583::/48ARINValid

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.