bgpreport

Network · data from 2026-11-12

AS135748 RADIANT-AS-IN - Radiant Network Technologies Pvt Ltd

Registry name: RADIANT-AS-IN - Radiant Network Technologies Pvt Ltd, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135748, 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.
103.76.8.0/24 Valid RIR databaseAPNIC 672 100% 67
103.76.9.0/24 Valid RIR databaseAPNIC 672 100% 66
103.76.10.0/24 Valid RIR databaseAPNIC 672 100% 66
2001:df1:dcc0::/48 Valid RIR databaseAPNIC 635 100% 67
103.76.8.0/23 Valid RIR databaseAPNIC 2 0%low visibility 3

AS-SET

AS135748 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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

103.76.8.0/27APNICInvalid: maxLength
103.76.8.32/27APNICInvalid: maxLength

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.