bgpreport

Network · data from 2026-11-12

AS45004 kct KCT OOO

Registry name: kct KCT OOO, RU · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS45004, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45004, 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.
91.210.120.0/22 Invalid: origin RIR databaseRIPE 82 12% 36

AS-SET

AS45004 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 1 are in fix.csv.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin91.210.120.0/22ROAs covering it name AS57844, AS397477, not AS45004. If AS45004 should announce it, add a ROA for AS45004.82 of 673

Route objects not announced

Every route object with origin AS45004 is announced.

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.