Network · data from 2026-11-12
AS267664
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267664, 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.
| 45.71.132.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 45.71.134.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
AS-SET
AS267664 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.71.132.0/23 | ROAs covering it name AS262468, not AS267664. If AS267664 should announce it, add a ROA for AS267664. |
| Route object: none | 45.71.132.0/23 | Route objects for it name AS262468. Add a route object with origin AS267664 in the RIR database for the space. |
| ROA: origin | 45.71.134.0/23 | ROAs covering it name AS262468, not AS267664. If AS267664 should announce it, add a ROA for AS267664. |
| Route object: none | 45.71.134.0/23 | Route objects for it name AS262468. Add a route object with origin AS267664 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267664 whose prefix no peer sees AS267664 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:44f8::/32 | RADB, TC | No ROA |
| 2804:44f8::/33 | RADB | No ROA |
| 2804:44f8:8000::/33 | 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.