Network · data from 2026-11-12

AS135448 Bukalapak.com

Registry name: IDNIC-BUKALAPAK-AS-ID - PT Bukalapak.com, ID · PeeringDB

7IPv4 routes 100.0% RPKI valid · 14.3% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 6 with no route object for this origin

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

1Route objects not announced registered with origin AS135448, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS135448, 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.64.14.0/24	Valid	None	670 100%	70
103.117.82.0/24	Valid	Nonecovered by 103.117.82.0/23	670 100%	70
103.117.83.0/24	Valid	Nonecovered by 103.117.82.0/23	670 100%	70
139.5.40.0/22	Valid	None	641 95%	66
45.122.52.0/22	Valid	None	636 95%	66
45.125.72.0/22	Valid	None	636 95%	66
103.97.251.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	70

AS-SET

AS135448's PeeringDB record names no 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: none6
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	103.64.14.0/24	No route object for it. Add a route object with origin AS135448 in the RIR database for the space.	670 of 673
Route object: none	103.117.82.0/24	No route object for it. A route object for 103.117.82.0/23 with origin AS135448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135448 in the RIR database for the space.	670 of 673
Route object: none	103.117.83.0/24	No route object for it. A route object for 103.117.82.0/23 with origin AS135448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135448 in the RIR database for the space.	670 of 673
Route object: none	139.5.40.0/22	No route object for it. Add a route object with origin AS135448 in the RIR database for the space.	641 of 673
Route object: none	45.122.52.0/22	No route object for it. Add a route object with origin AS135448 in the RIR database for the space.	636 of 673
Route object: none	45.125.72.0/22	No route object for it. Add a route object with origin AS135448 in the RIR database for the space.	636 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

103.64.14.0/24

No route object for it. Add a route object with origin AS135448 in the RIR database for the space.

670 of 673

Route object: none

103.117.82.0/24

No route object for it. A route object for 103.117.82.0/23 with origin AS135448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135448 in the RIR database for the space.

670 of 673

Route object: none

103.117.83.0/24

670 of 673

Route object: none

139.5.40.0/22

No route object for it. Add a route object with origin AS135448 in the RIR database for the space.

641 of 673

Route object: none

45.122.52.0/22

No route object for it. Add a route object with origin AS135448 in the RIR database for the space.

636 of 673

Route object: none

45.125.72.0/22

No route object for it. Add a route object with origin AS135448 in the RIR database for the space.

636 of 673

Route objects not announced

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


103.117.82.0/23	RADB	Valid

103.117.82.0/23

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.