bgpreport

Network · data from 2026-11-12

AS136362 Yes India Communications

Registry name: INTERNET-AS - Yes India Communications Pvt. Ltd, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136362, 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.90.180.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.143.186.0/23 Valid RIR databaseAPNIC 672 100% 67
2001:df2:bc0::/48 Valid RIR databaseAPNIC 635 100% 67
103.90.180.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.90.181.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.90.182.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.90.183.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.143.187.0/24 Valid RIR databaseAPNIC 10 1%low visibility 4
103.143.186.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS136362: AS136362:AS-INTERNET. 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 (AS136362 isn't in the set, or no route object for AS136362 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 objectsAS136362 in itNot covered
AS136362:AS-INTERNET APNIC 4125 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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

103.90.180.0/23APNICValid
103.90.182.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.