bgpreport

Network · data from 2026-11-12

AS39249 KICUA-AS Netassist International EOOD

Registry name: KICUA-AS Netassist International EOOD, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39249, 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.
2001:67c:1874::/48 No ROA RIR databaseRIPE 8 1%low visibility 7
95.164.71.0/24 Valid RIR databaseRIPE 673 100% 66
193.104.254.0/24 Valid RIR databaseRIPE 673 100% 66
195.149.96.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS39249 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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:1874::/48No ROA covers it. Add a ROA for AS39249, maxLength 48.8 of 636

Route objects not announced

Route objects with origin AS39249 whose prefix no peer sees AS39249 announce. Many are kept on purpose (backup routes, space announced only in some places).

195.214.212.0/24RIPEValid
2a10:eb80:fe00::/40RIPEInvalid: origin
2a10:eb80:ff00::/40RIPEInvalid: origin

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.