bgpreport

Network · data from 2026-11-12

AS137172 ALL CONNECT NETWORK SERVICES PRIVATE LIMITED

Registry name: ACNS-AS-IN - ALL CONNECT NETWORK SERVICES PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137172, 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.
2403:6bc0::/32 No ROA Other IRR onlyRADB 636 100% 70
103.112.212.0/22 Valid RIR databaseAPNIC 673 100% 66
103.190.66.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
163.61.64.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.112.212.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.112.213.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.112.214.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.112.215.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.190.66.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
103.190.67.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27
163.61.64.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27
163.61.65.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 27

AS-SET

PeeringDB's irr_as_set for AS137172: AS137172:AS-ACNS. 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 (AS137172 isn't in the set, or no route object for AS137172 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 objectsAS137172 in itNot covered
AS137172:AS-ACNS RADB 9371 Yes 0
APNIC (also) 4224 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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2403:6bc0::/32No ROA covers it. Add a ROA for AS137172, maxLength 32.636 of 636
Route object: RIR2403:6bc0::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.112.212.0/23APNICValid
103.112.214.0/23APNICValid

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.