bgpreport

Network · data from 2026-11-12

AS135761 Userlinks Netcom

Registry name: ULNPLSUM-AS - Userlinks Netcom Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135761, 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.38.52.0/23 Valid RIR databaseAPNIC 672 100% 67
103.70.164.0/23 Valid RIR databaseAPNIC 672 100% 67
103.70.166.0/23 Valid RIR databaseAPNIC 672 100% 67
103.143.166.0/23 Valid RIR databaseAPNIC 672 100% 67
103.152.159.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.160.196.0/23 Valid RIR databaseAPNIC 672 100% 67
103.168.2.0/23 Valid RIR databaseAPNIC 672 100% 67
103.208.90.0/23 Valid RIR databaseAPNIC 672 100% 67
103.218.186.0/23 Valid RIR databaseAPNIC 672 100% 67
2407:1f40::/32 Valid RIR databaseAPNIC 635 100% 67
103.38.52.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.38.53.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.70.164.0/24 Valid RIR databaseAPNIC, RADB 11 2%low visibility 5
103.70.165.0/24 Valid RIR databaseAPNIC, RADB 11 2%low visibility 5
103.70.166.0/24 Valid RIR databaseAPNIC, RADB 11 2%low visibility 5
103.70.167.0/24 Valid RIR databaseAPNIC, RADB 11 2%low visibility 5
103.143.166.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.143.167.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.160.196.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.160.197.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.168.2.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.168.3.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.208.90.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.208.91.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.218.186.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.218.187.0/24 Valid RIR databaseAPNIC 11 2%low visibility 5
103.70.164.0/22 Valid RIR databaseAPNIC, RADB 10 1%low visibility 5
2407:1f40::/34 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40::/35 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40::/36 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40:1000::/36 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40:2000::/35 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40:2000::/36 Valid RIR databaseAPNIC 10 2%low visibility 5
2407:1f40:3000::/36 Valid RIR databaseAPNIC 10 2%low visibility 5
103.175.29.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS135761: AS135761:AS-ULNPLSUM. 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 (AS135761 isn't in the set, or no route object for AS135761 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 objectsAS135761 in itNot covered
AS135761:AS-ULNPLSUM APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7247721,485 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 5 are in fix.csv.

  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS135761:AS-ULNPLSUMAS135761:AS-ULNPLSUM (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS135761:AS-ULNPLSUMAS135761:AS-ULNPLSUM (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS135761:AS-ULNPLSUMAS135761:AS-ULNPLSUM (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS135761:AS-ULNPLSUMAS135761:AS-ULNPLSUM (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS135761:AS-ULNPLSUMAS135761:AS-ULNPLSUM (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

Every route object with origin AS135761 is announced.

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.