Announced routes
Every prefix a peer of the route collectors sees with origin AS272195, 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.
| 38.224.182.0/24 | No ROA | Nonecovered by 38.224.182.0/23 | 2 0%low visibility |
| 38.224.183.0/24 | No ROA | Nonecovered by 38.224.182.0/23 | 2 0%low visibility |
| 38.224.182.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 2804:8364::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:8364::/34 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 2804:8364:4000::/34 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 2804:8364:8000::/34 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 2804:8364:c000::/34 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS272195: AS272195:AS-SET_________________________________________________________________________________________________________________________________________________. 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 (AS272195 isn't in the set, or no route object for AS272195 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 | AS272195 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS272195:AS-SET_________________________________________________________________________________________________________________________________________________ | In no IRR database read today. | |||||
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 12 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR6
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.224.182.0/24 | No ROA covers it. Add a ROA for AS272195, maxLength 24. |
| Route object: none | 38.224.182.0/24 | No route object for it. A route object for 38.224.182.0/23 with origin AS272195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272195 in the RIR database for the space. |
| ROA: none | 38.224.183.0/24 | No ROA covers it. Add a ROA for AS272195, maxLength 24. |
| Route object: none | 38.224.183.0/24 | No route object for it. A route object for 38.224.182.0/23 with origin AS272195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272195 in the RIR database for the space. |
| ROA: none | 38.224.182.0/23 | No ROA covers it. Add a ROA for AS272195, maxLength 23. |
| Route object: RIR | 38.224.182.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:8364::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:8364::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:8364:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:8364:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:8364:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS272195:AS-SET_________________________________________________________________________________________________________________________________________________ | PeeringDB names AS272195:AS-SET_________________________________________________________________________________________________________________________________________________; no IRR database read has it. |
Route objects not announced
Every route object with origin AS272195 is announced.
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.