bgpreport

Network · data from 2026-11-12

AS135839 Optical Broadband

Registry name: OPTICAL-AS - Optical Broadband Communication Pvt. Ltd, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135839, 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.83.136.0/22 Valid RIR databaseAPNIC 672 100% 67
103.83.136.0/23 Valid RIR databaseAPNIC 672 100% 67
103.83.138.0/23 Valid RIR databaseAPNIC 672 100% 67
103.158.30.0/23 Valid RIR databaseAPNIC 672 100% 67
103.83.136.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28
103.83.137.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28
103.83.138.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28
103.83.139.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28
103.158.30.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28
103.158.31.0/24 Valid RIR databaseAPNIC 37 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS135839: AS135839. 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 (AS135839 isn't in the set, or no route object for AS135839 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 objectsAS135839 in itNot covered
AS135839 A single AS number, not a set: AS135839 (this network), 13 route objects.

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

  • Route object: not announced3

Route objects not announced

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

2001:df0:dd80::/48APNICValid
2001:df5:4080::/48APNICValid
2406:9440::/32APNICValid

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.