bgpreport

Network · data from 2026-11-12

AS135799 Rapidnet Pvt Ltd

Registry name: RNETXT-AS - Rapidnet Private Limited, IN · PeeringDB

31IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
19Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS135799, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS135799, 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.68.28.0/22 Valid RIR databaseAPNIC 672 100% 67
103.82.125.0/24 Valid RIR databaseAPNIC 672 100% 67
103.83.127.0/24 Valid RIR databaseAPNIC 672 100% 67
103.83.128.0/22 Valid RIR databaseAPNIC 672 100% 67
103.83.148.0/23 Valid RIR databaseAPNIC 672 100% 67
103.102.88.0/22 Valid RIR databaseAPNIC 672 100% 67
103.163.124.0/23 Valid RIR databaseAPNIC 672 100% 67
103.171.222.0/23 Valid RIR databaseAPNIC 672 100% 67
103.243.5.0/24 Valid RIR databaseAPNIC 672 100% 67
103.243.6.0/24 Valid RIR databaseAPNIC 672 100% 67
160.187.178.0/24 Valid RIR databaseAPNIC 672 100% 67
103.157.150.0/23 Valid RIR databaseAPNIC 671 100% 67
2401:7dc0::/32 Valid RIR databaseAPNIC 634 100% 67
2402:4cc0::/32 Valid RIR databaseAPNIC 634 100% 67
103.171.222.0/24 Valid RIR databaseAPNIC 39 6%low visibility 29
103.83.131.0/24 Valid RIR databaseAPNIC 3 0%low visibility 3
103.68.28.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.68.29.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.68.30.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.68.31.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.83.128.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.83.129.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.83.130.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.83.148.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.83.149.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.102.88.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.102.89.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.102.90.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.102.91.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.157.150.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.157.151.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.163.124.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.163.125.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS135799: AS135799:AS-RAPIDNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS135799 isn't in the set, or no route object for AS135799 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS135799 in itNot covered
AS135799:AS-RAPIDNET APNIClists itself further down 3861,486 Yes 0

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

  • Route object: not announced9

Route objects not announced

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

103.68.28.0/23APNICValid
103.68.30.0/23APNICValid
103.83.128.0/23APNICValid
103.83.130.0/23APNICValid
103.102.88.0/23APNICValid
103.102.90.0/23APNICValid
103.171.223.0/24APNICValid
160.187.178.0/23APNICValid
160.187.179.0/24APNICValid

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.