Network · data from 2026-11-12

AS136100 BKVTELEMEDIA-AS-ID - PT. BKVNET TELEMEDIA

Registry name: BKVTELEMEDIA-AS-ID - PT. BKVNET TELEMEDIA, ID · not in PeeringDB

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

3Route objects not announced registered with origin AS136100, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136100, 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.89.160.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
103.89.161.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
103.89.162.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
103.89.163.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67

AS-SET

AS136100 isn't in PeeringDB, where networks name their AS-SET.

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

Route object: RIR4
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	103.89.160.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	103.89.161.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	103.89.162.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	103.89.163.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

103.89.160.0/24

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

667 of 673

Route object: RIR

103.89.161.0/24

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

667 of 673

Route object: RIR

103.89.162.0/24

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

667 of 673

Route object: RIR

103.89.163.0/24

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

667 of 673

Route objects not announced

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


103.89.160.0/22	APNIC, NTTCOM, RADB	Valid
103.89.160.0/23	NTTCOM, RADB	Valid
103.89.162.0/23	NTTCOM, RADB	Valid

103.89.160.0/22

APNIC, NTTCOM, RADB

Valid

103.89.160.0/23

NTTCOM, RADB

Valid

103.89.162.0/23

NTTCOM, RADB

Valid

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.