Announced routes
Every prefix a peer of the route collectors sees with origin AS36817, 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.
| 64.187.210.0/23 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 66.112.176.0/20 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 72.172.96.0/19 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 74.214.128.0/20 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 74.214.144.0/20 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 162.208.36.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 162.220.36.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 162.248.152.0/21 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 173.209.112.0/20 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 192.40.136.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 170.253.96.0/19 | No ROA | RIR databaseARIN | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS36817: AS-MCSNET. 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 (AS36817 isn't in the set, or no route object for AS36817 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 | AS36817 in it | Not covered |
|---|---|---|---|---|---|
| AS-MCSNET | ARIN | 1 | 1 | 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 11 are in fix.csv.
- ROA: none11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.187.210.0/23 | No ROA covers it. Add a ROA for AS36817, maxLength 23. |
| ROA: none | 66.112.176.0/20 | No ROA covers it. Add a ROA for AS36817, maxLength 20. |
| ROA: none | 72.172.96.0/19 | No ROA covers it. Add a ROA for AS36817, maxLength 19. |
| ROA: none | 74.214.128.0/20 | No ROA covers it. Add a ROA for AS36817, maxLength 20. |
| ROA: none | 74.214.144.0/20 | No ROA covers it. Add a ROA for AS36817, maxLength 20. |
| ROA: none | 162.208.36.0/22 | No ROA covers it. Add a ROA for AS36817, maxLength 22. |
| ROA: none | 162.220.36.0/22 | No ROA covers it. Add a ROA for AS36817, maxLength 22. |
| ROA: none | 162.248.152.0/21 | No ROA covers it. Add a ROA for AS36817, maxLength 21. |
| ROA: none | 173.209.112.0/20 | No ROA covers it. Add a ROA for AS36817, maxLength 20. |
| ROA: none | 192.40.136.0/22 | No ROA covers it. Add a ROA for AS36817, maxLength 22. |
| ROA: none | 170.253.96.0/19 | No ROA covers it. Add a ROA for AS36817, maxLength 19. |
Route objects not announced
Every route object with origin AS36817 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.