bgpreport

Network · data from 2026-11-12

AS154723 Optical Communication

Registry name: OPTICA-AS-AP - Optical Communication, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154723, 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.

162.4.64.0/23 No ROA RIR databaseAPNIC 2 0%low visibility 2
160.236.10.0/24 Valid RIR databaseAPNIC 671 100% 67
160.236.11.0/24 Valid RIR databaseAPNIC 671 100% 67
162.4.64.0/24 Valid RIR databaseAPNIC 669 99% 67
162.4.65.0/24 Valid RIR databaseAPNIC 669 99% 67
160.236.10.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS154723: AS-154723. 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 (AS154723 isn't in the set, or no route object for AS154723 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 objectsAS154723 in itNot covered
AS-154723 In no IRR database read today.

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
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none162.4.64.0/23No ROA covers it. Add a ROA for AS154723, maxLength 23.2 of 673
AS-SET: not foundAS-154723PeeringDB names AS-154723; no IRR database read has it.

Route objects not announced

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

2001:df7:4a40::/48APNICValid
2402:5b20::/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.