Network · data from 2026-11-12
AS47966 Koinot-Tv
Registry name: KOINOT-AS Koinot-Tv MChJ, UZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47966, 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.
| 95.46.47.0/24 | Invalid: origin | None | 3 0%low visibility |
| 94.154.10.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.47.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS47966'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 4 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 95.46.47.0/24 | ROAs covering it name AS44546, not AS47966. If AS47966 should announce it, add a ROA for AS47966. |
| Route object: none | 95.46.47.0/24 | No route object for it. Add a route object with origin AS47966 in the RIR database for the space. |
| ROA: none | 94.154.10.0/24 | No ROA covers it. Add a ROA for AS47966, maxLength 24. |
Route objects not announced
Route objects with origin AS47966 whose prefix no peer sees AS47966 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:f440::/32 | RIPE | 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.