Network · data from 2026-11-12
AS12480 ILK Internet
Registry name: ASILK ILK Internet GmbH Rechnerkommunikation im Internet, DE · PeeringDB
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% |
| 194.172.58.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 212.86.208.0/24 | Valid | Nonecovered by 212.86.192.0/19 | 670 100% |
| 185.149.156.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.193.144.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 194.26.16.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.45.22.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.59.13.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.120.173.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.174.11.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.192.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 2a00:1970::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a11:9400::/32 | Valid | RIR databaseRIPE | 635 100% |
| 194.121.203.0/24 | Valid | RIR databaseRIPE | 511 76% |
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.
| Name | Database | ASNs | Sets | AS12480 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ILK | RIPElists itself further down1 member set in no database: AS-ASKNET | 8 | 8 | 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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.141.55.0/24 | No ROA covers it. Add a ROA for AS12480, maxLength 24. |
| ROA: none | 194.172.58.0/24 | No ROA covers it. Add a ROA for AS12480, maxLength 24. |
| Route object: none | 212.86.208.0/24 | No 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. |
| AS-SET: missing member | RIPE::AS-ILK | AS-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/22 | RIPE | Valid |
| 91.220.159.0/24 | RIPE | Invalid: origin |
| 91.221.120.0/23 | RIPE | Invalid: origin |
| 91.221.120.0/24 | RIPE | Invalid: origin |
| 91.221.121.0/24 | RIPE | Invalid: origin |
| 193.101.11.0/24 | RIPE | Valid |
| 193.101.24.0/21 | RIPE | Valid |
| 194.76.193.0/24 | RIPE | Valid |
| 194.120.43.0/24 | RIPE | Valid |
| 194.143.156.0/23 | RIPE | Valid |
| 195.42.114.0/24 | RIPE | No ROA |
| 195.42.115.0/24 | RIPE | Valid |
| 2001:470:583::/48 | ARIN | Valid |
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.