Network · data from 2026-11-12

AS151387 OMURA CABLE TELEVISION K.K.

Registry name: OCTP-NET - OMURA CABLE TELEVISION K.K., JP · PeeringDB

3IPv4 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

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS151387, seen from no peer

Announced routes

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


157.66.72.0/23	Valid	Other IRR onlyJPIRR, RADB	673 100%	67
14.15.96.0/20	Valid	Other IRR onlyJPIRR, RADB	672 100%	67
14.15.112.0/20	Valid	Other IRR onlyJPIRR, RADB	672 100%	67

AS-SET

PeeringDB's irr_as_set for AS151387: AS-151387. 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 (AS151387 isn't in the set, or no route object for AS151387 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.

Name	Database	ASNs	Sets	Route objects	AS151387 in it	Not covered
AS-151387	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS151387 in it

Not covered

AS-151387

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.

Route object: RIR3
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	157.66.72.0/23	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	14.15.96.0/20	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	14.15.112.0/20	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	672 of 673
AS-SET: not found	AS-151387	PeeringDB names AS-151387; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

157.66.72.0/23

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

14.15.96.0/20

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

672 of 673

Route object: RIR

14.15.112.0/20

Route object only in JPIRR, RADB. Add it in the RIR database for the space.

672 of 673

AS-SET: not found

AS-151387

PeeringDB names AS-151387; no IRR database read has it.

Route objects not announced

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