Announced routes
Every prefix a peer of the route collectors sees with origin AS2603, 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.
| 194.68.13.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.36.171.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 193.10.255.0/24 | Valid | Other origin only | 663 99% |
| 109.105.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.105.112.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 109.105.120.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.174.116.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.10.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.10.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.11.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2001:948::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2001:948::/29 | Valid | RIR databaseRIPE | 584 92% |
AS-SET
PeeringDB's irr_as_set for AS2603: RIPE::AS-NORDUNET. 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 (AS2603 isn't in the set, or no route object for AS2603 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 | AS2603 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-NORDUNET | RIPElists itself further down2 member sets in no database: AS-SARIMNER, AS6509:AS-CANARIE | 930 | 128 | Yes | 1 |
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 9 are in fix.csv.
- ROA: none2
- Route object: none1
- AS-SET: missing member2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.68.13.0/24 | No ROA covers it. Add a ROA for AS2603, maxLength 24. |
| ROA: none | 192.36.171.0/24 | No ROA covers it. Add a ROA for AS2603, maxLength 24. |
| Route object: none | 193.10.255.0/24 | Route objects for it name AS2832. Add a route object with origin AS2603 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS-NORDUNET | AS-NORDUNET (RIPE) lists AS-SARIMNER; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-NORDUNET | AS-NORDUNET (RIPE) lists AS6509:AS-CANARIE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS2603 whose prefix no peer sees AS2603 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.105.96.0/19 | RIPE | No ROA |
| 193.10.68.0/24 | RIPE | Valid |
| 193.10.94.0/24 | RIPE | Valid |
| 193.10.95.0/24 | RIPE | 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.