Announced routes
Every prefix a peer of the route collectors sees with origin AS23273, 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.
| 192.161.167.0/24 | Valid | None | 673 100% |
| 69.12.66.0/24 | Valid | RIR databaseARIN | 673 100% |
| 107.150.4.0/24 | Valid | RIR databaseARIN | 673 100% |
| 155.94.167.0/24 | Valid | RIR databaseARIN | 673 100% |
| 192.161.49.0/24 | Valid | RIR databaseARIN | 673 100% |
| 198.84.80.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.44.192.0/20 | Valid | RIR databaseARIN | 673 100% |
| 155.94.128.0/24 | Valid | RIR databaseARIN | 672 100% |
| 194.146.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 172.96.180.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
| 2605:6f0f::/32 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS23273's PeeringDB record names no AS-SET.
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.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 192.161.167.0/24 | No route object for it. Add a route object with origin AS23273 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23273 whose prefix no peer sees AS23273 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.116.99.0/24 | RADB | No ROA |
| 66.116.106.0/24 | RADB | No ROA |
| 66.116.114.0/24 | RADB | No ROA |
| 66.209.86.0/24 | RADB | No ROA |
| 69.194.138.0/24 | RADB | No ROA |
| 192.210.246.0/24 | ARIN | Invalid: origin |
| 207.114.137.0/24 | RADB | No ROA |
| 207.114.164.0/24 | RADB | No ROA |
| 207.114.165.0/24 | RADB | No ROA |
| 216.64.185.0/24 | RADB | No ROA |
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.