bgpreport

Network · data from 2026-11-12

AS135692 Global Ra Net Services

Registry name: RAGLOBAL-AS-IN - Global Ra Net Services Pvt. Ltd., IN · PeeringDB

14IPv4 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
9Route objects not announced registered with origin AS135692, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS135692, 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.71.76.0/24 Valid RIR databaseAPNIC 672 100% 66
103.71.77.0/24 Valid RIR databaseAPNIC 672 100% 66
103.71.78.0/24 Valid RIR databaseAPNIC 672 100% 66
103.71.79.0/24 Valid RIR databaseAPNIC 672 100% 66
103.105.152.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.105.153.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.105.154.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.105.155.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.160.176.0/23 Valid RIR databaseAPNIC 672 100% 66
103.160.176.0/24 Valid RIR databaseAPNIC 672 100% 66
103.160.177.0/24 Valid RIR databaseAPNIC 672 100% 66
138.252.242.0/23 Valid RIR databaseAPNIC 672 100% 66
138.252.242.0/24 Valid RIR databaseAPNIC 672 100% 66
138.252.243.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS135692: AS135692:AS-CUSTOMERS. 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 (AS135692 isn't in the set, or no route object for AS135692 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 objectsAS135692 in itNot covered
AS135692:AS-CUSTOMERS In no IRR database read today.

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

  • AS-SET: not found1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
AS-SET: not foundAS135692:AS-CUSTOMERSPeeringDB names AS135692:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

103.71.76.0/22APNICValid
103.71.76.0/23APNICValid
103.71.78.0/23APNICValid
103.105.152.0/22APNICValid
103.105.152.0/23APNICValid
103.105.154.0/23APNICValid
2001:df3:7d00::/48APNICNo ROA
2402:640::/32APNICNo ROA
2406:edc0::/32APNICNo ROA

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.