bgpreport

Network · data from 2026-11-12

AS38556 Narae Networks

Registry name: NARAENETWORKS-AS-AP - Narae Networks, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38556, 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.
116.212.184.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66

AS-SET

AS38556'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.

  • Route object: not announced4

Route objects not announced

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

116.212.184.0/21NTTCOM, RADBNo ROA
116.212.184.0/22RADBNo ROA
116.212.184.0/23APNIC, RADBValid
2401:e6a0::/32APNICValid

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.