Announced routes
Every prefix a peer of the route collectors sees with origin AS36734, 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.
| 66.117.152.0/23 | Invalid: origin | RIR databaseARIN | 18 3%low visibility |
| 8.17.88.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 148.64.122.0/24 | Valid | Nonecovered by 148.64.120.0/21 | 673 100% |
| 2607:5100::/28 | Valid | Other IRR onlyRADB | 634 100% |
| 63.216.64.0/21 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 64.201.240.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 76.77.176.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 148.64.112.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 173.241.16.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.38.128.0/19 | Valid | RIR databaseARIN | 671 100% |
| 66.54.100.0/22 | Valid | RIR databaseARIN, RADB | 669 99% |
| 173.195.73.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 173.195.76.0/22 | Valid | RIR databaseARIN | 669 99% |
| 204.10.72.0/22 | Valid | RIR databaseARIN | 669 99% |
| 204.153.192.0/22 | Valid | RIR databaseARIN | 669 99% |
| 2604:4780::/32 | Valid | RIR databaseARIN | 634 100% |
| 2600:7f00::/28 | Valid | RIR databaseARIN | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS36734: AS-PAXIO. 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 (AS36734 isn't in the set, or no route object for AS36734 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 | AS36734 in it | Not covered |
|---|---|---|---|---|---|
| AS-PAXIO | RADB | 17 | 2 | 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 7 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 66.117.152.0/23 | ROAs covering it name AS7235, not AS36734. If AS36734 should announce it, add a ROA for AS36734. |
| ROA: none | 8.17.88.0/21 | No ROA covers it. Add a ROA for AS36734, maxLength 21. |
| Route object: RIR | 8.17.88.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 148.64.122.0/24 | No route object for it. A route object for 148.64.120.0/21 with origin AS36734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36734 in the RIR database for the space. |
| Route object: RIR | 2607:5100::/28 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36734 whose prefix no peer sees AS36734 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.64.120.0/21 | RADB | Valid |
| 2604:4780:2669::/48 | 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.