26IPv4 routes
92.3% RPKI valid · 96.2% with a route object
18IPv6 routes
94.4% RPKI valid · 22.2% with a route object
0RPKI invalid
0 origin · 0 maxLength
3No ROA
15 with no route object for this origin
15Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS25091, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS25091, 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.
| 0.0.0.0/0 bogon | No ROA | None | 1 0%low visibility |
| ::/0 bogon | No ROA | None | 0 0%low visibility |
| 46.102.238.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:2528:c00::/40 | Valid | Nonecovered by 2a02:2528::/29 | 15 2%low visibility |
| 2a02:2528:1900::/40 | Valid | Nonecovered by 2a02:2528::/29 | 15 2%low visibility |
| 2a02:2528:ff00::/40 | Valid | Nonecovered by 2a02:2528::/29 | 15 2%low visibility |
| 2a02:2528:f8::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:1501::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:1703::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:1e01::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff02::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff03::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff04::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff05::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff06::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 2a02:2528:ff07::/48 | Valid | Nonecovered by 2a02:2528::/29 | 0 0%low visibility |
| 5.144.34.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.144.38.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.20.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 46.174.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.110.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.8.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.100.138.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.100.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.158.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 160.53.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.60.52.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.185.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.76.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.196.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 192.162.204.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.135.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.102.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.139.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.106.93.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.247.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.144.35.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 213.139.244.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.144.34.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a01:6780:12::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a0c:4144:100::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a02:2528::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a0d:cb80::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS25091: RIPE::AS-IP-MAX RIPE::AS-IP-MAX-V6. 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 (AS25091 isn't in the set, or no route object for AS25091 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 | AS25091 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-IP-MAX | RIPElists itself further down5 member sets in no database: AS-ACCIO-IPV4, AS-DIGITALESUISSE, AS-GTLD, AS-PLAINELIMAGNE, AS199092:AS-TRANSIT | 253 | 112 | Yes | 2 |
| RIPE::AS-IP-MAX-V6 | RIPElists itself further down4 member sets in no database: AS-ACCIO-IPV6, AS-DIGITALESUISSE, AS-GTLD, AS-PLAINELIMAGNE | 244 | 107 | Yes | 2 |
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 26 are in fix.csv.
- Bogon prefix2
- ROA: none1
- Route object: none13
- AS-SET: missing member9
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Bogon prefix | 0.0.0.0/0 | In IANA's special-purpose registry: default route. |
| Bogon prefix | ::/0 | In IANA's special-purpose registry: default route. |
| ROA: none | 46.102.238.0/24 | No ROA covers it. Add a ROA for AS25091, maxLength 24. |
| Route object: none | 2a02:2528:c00::/40 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:1900::/40 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff00::/40 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:f8::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:1501::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:1703::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:1e01::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff02::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff03::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff04::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff05::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff06::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| Route object: none | 2a02:2528:ff07::/48 | No route object for it. A route object for 2a02:2528::/29 with origin AS25091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25091 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS-IP-MAX | AS-IP-MAX (RIPE) lists AS-ACCIO-IPV4; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX | AS-IP-MAX (RIPE) lists AS-DIGITALESUISSE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX | AS-IP-MAX (RIPE) lists AS-GTLD; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX | AS-IP-MAX (RIPE) lists AS-PLAINELIMAGNE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX | AS-IP-MAX (RIPE) lists AS199092:AS-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX-V6 | AS-IP-MAX-V6 (RIPE) lists AS-ACCIO-IPV6; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX-V6 | AS-IP-MAX-V6 (RIPE) lists AS-DIGITALESUISSE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX-V6 | AS-IP-MAX-V6 (RIPE) lists AS-GTLD; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-IP-MAX-V6 | AS-IP-MAX-V6 (RIPE) lists AS-PLAINELIMAGNE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS25091 whose prefix no peer sees AS25091 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0c:c600::/29 | RIPE | No ROA |
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.