bgpreport

Network · data from 2026-11-12

AS136342 Winux Communications

Registry name: WINUXC-AS - Winux Communications Pvt. Ltd., IN · PeeringDB

24IPv4 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS136342, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136342, 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.113.228.0/22 Valid RIR databaseAPNIC 673 100% 66
103.113.228.0/24 Valid RIR databaseAPNIC 673 100% 67
103.113.229.0/24 Valid RIR databaseAPNIC 673 100% 67
103.113.230.0/24 Valid RIR databaseAPNIC 673 100% 67
103.113.231.0/24 Valid RIR databaseAPNIC 673 100% 67
103.117.64.0/24 Valid RIR databaseAPNIC 673 100% 67
103.117.65.0/24 Valid RIR databaseAPNIC 673 100% 67
103.117.66.0/24 Valid RIR databaseAPNIC 673 100% 67
103.117.67.0/24 Valid RIR databaseAPNIC 673 100% 67
103.127.184.0/22 Valid RIR databaseAPNIC 673 100% 66
103.127.184.0/24 Valid RIR databaseAPNIC 673 100% 67
103.127.185.0/24 Valid RIR databaseAPNIC 673 100% 67
103.127.186.0/24 Valid RIR databaseAPNIC 673 100% 67
103.127.187.0/24 Valid RIR databaseAPNIC 673 100% 67
103.113.228.0/23 Valid RIR databaseAPNIC 671 100% 66
103.113.230.0/23 Valid RIR databaseAPNIC 671 100% 66
103.117.64.0/22 Valid RIR databaseAPNIC 671 100% 66
103.117.64.0/23 Valid RIR databaseAPNIC 671 100% 66
103.117.66.0/23 Valid RIR databaseAPNIC 671 100% 66
103.127.184.0/23 Valid RIR databaseAPNIC 671 100% 66
103.127.186.0/23 Valid RIR databaseAPNIC 671 100% 66
103.188.48.0/23 Valid RIR databaseAPNIC 671 100% 66
2400:80a0::/32 Valid RIR databaseAPNIC 633 100% 67
2405:b740::/32 Valid RIR databaseAPNIC 633 100% 67
103.188.48.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
103.188.49.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS136342: AS136342:AS-WINUXC. 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 (AS136342 isn't in the set, or no route object for AS136342 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 objectsAS136342 in itNot covered
AS136342:AS-WINUXC APNIC 5156 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS136342 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.