Network · data from 2026-11-12
AS266297
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266297, 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.
| 170.79.204.0/22 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS266297 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 10 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 170.79.204.0/22 | ROAs covering it name AS266337, not AS266297. If AS266297 should announce it, add a ROA for AS266297. |
| Route object: none | 170.79.204.0/22 | Route objects for it name AS266337. Add a route object with origin AS266297 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266297 whose prefix no peer sees AS266297 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.185.220.0/22 | ALTDB | No ROA |
| 2804:35a0::/32 | RADB, TC | No ROA |
| 2804:35a0::/33 | RADB | No ROA |
| 2804:35a0::/34 | RADB | No ROA |
| 2804:35a0:8000::/33 | RADB | No ROA |
| 2804:35a0:d000::/36 | RADB | No ROA |
| 2804:35a0:e000::/36 | RADB | No ROA |
| 2804:35a0:f000::/36 | 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.