Announced routes
Every prefix a peer of the route collectors sees with origin AS13823, 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.
| 204.238.187.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 204.238.218.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 208.66.148.0/23 | Valid | RIR databaseARIN | 670 100% |
| 208.66.151.0/24 | Valid | RIR databaseARIN | 670 100% |
| 74.113.240.0/22 | Valid | RIR databaseARIN | 669 99% |
| 74.113.244.0/24 | Valid | RIR databaseARIN | 669 99% |
| 74.113.246.0/24 | Valid | RIR databaseARIN | 669 99% |
| 74.113.247.0/24 | Valid | RIR databaseARIN | 669 99% |
| 208.66.144.0/22 | Valid | RIR databaseARIN | 669 99% |
| 208.66.148.0/24 | Valid | RIR databaseARIN | 669 99% |
| 208.66.149.0/24 | Valid | RIR databaseARIN | 669 99% |
| 208.66.150.0/24 | Valid | RIR databaseARIN | 669 99% |
| 2605:d600::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS13823: AS-MESH. 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 (AS13823 isn't in the set, or no route object for AS13823 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 | AS13823 in it | Not covered |
|---|---|---|---|---|---|
| AS-MESH | RADB1 member set in no database: AS-MESH-CUSTOMER:AS9326 | 229 | 40 | No | 13 |
| ARIN (also) | 2 | 2 | Yes | 0 | |
| JPIRR (also)1 member set in no database: AS-MESH-CUSTOMER:AS9326 | 228 | 40 | No | 13 | |
| RIPE (also) | 1 | 1 | No | 13 |
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: RIR2
- AS-SET: own ASN1
- AS-SET: missing member1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.238.187.0/24 | No ROA covers it. Add a ROA for AS13823, maxLength 24. |
| Route object: RIR | 204.238.187.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.238.218.0/24 | No ROA covers it. Add a ROA for AS13823, maxLength 24. |
| Route object: RIR | 204.238.218.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-MESH | AS13823 isn't in AS-MESH (RADB) once expanded. Add AS13823 to it. |
| AS-SET: missing member | AS-MESH | AS-MESH (RADB) lists AS-MESH-CUSTOMER:AS9326; no IRR database read has it. |
Route objects not announced
Route objects with origin AS13823 whose prefix no peer sees AS13823 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.113.240.0/21 | ARIN, RADB | Valid |
| 74.113.244.0/23 | ARIN | Valid |
| 208.66.144.0/21 | ARIN, RADB | 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.