Announced routes
Every prefix a peer of the route collectors sees with origin AS6208, 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.158.208.0/20 | No ROA | Other IRR onlyRADB | 667 99% |
| 154.64.223.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
| 2604:fcc0:5000::/48 | Valid | Nonecovered by 2604:fcc0::/32 | 631 99% |
| 104.238.194.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 199.116.63.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 2604:fcc0::/32 | Valid | Other IRR onlyRADB | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS6208: RADB::AS6208:AS-CUSTOMERS. 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 (AS6208 isn't in the set, or no route object for AS6208 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 | AS6208 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS6208:AS-CUSTOMERS | RADBlists itself further down7 member sets in no database: AS-23379-AS-CUSTOMERS, AS-NUSTREAM, AS14979:AS-CUSTOMERS, AS271945:AS-CLIENTES, AS395502:AS-ALL … | 105 | 10 | 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 15 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR5
- AS-SET: missing member7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.158.208.0/20 | No ROA covers it. Add a ROA for AS6208, maxLength 20. |
| Route object: RIR | 38.158.208.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.64.223.0/24 | No ROA covers it. Add a ROA for AS6208, maxLength 24. |
| Route object: RIR | 154.64.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2604:fcc0:5000::/48 | No route object for it. A route object for 2604:fcc0::/32 with origin AS6208 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6208 in the RIR database for the space. |
| Route object: RIR | 104.238.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.116.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2604:fcc0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS-23379-AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS-NUSTREAM; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS14979:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS271945:AS-CLIENTES; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS395502:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS46962:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | RADB::AS6208:AS-CUSTOMERS | AS6208:AS-CUSTOMERS (RADB) lists AS46962:AS-ALL-IPV6; no IRR database read has it. |
Route objects not announced
Every route object with origin AS6208 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.