Network · data from 2026-11-12

AS63873 Mitra Akses Globalindo

Registry name: MAGNET-AS-ID - PT Mitra Akses Globalindo, ID · PeeringDB

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

7Route objects not announced registered with origin AS63873, seen from no peer

Announced routes

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


45.115.136.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
45.115.137.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
103.53.0.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
103.53.1.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
103.53.2.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
103.53.3.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
45.115.136.0/23	Valid	Other IRR onlyNTTCOM	670 100%	67
45.115.138.0/24	Valid	Other IRR onlyNTTCOM, RADB	670 100%	69
45.115.139.0/24	Valid	Other IRR onlyNTTCOM, RADB	670 100%	69
103.53.0.0/23	Valid	Other IRR onlyNTTCOM	670 100%	67
103.53.2.0/23	Valid	Other IRR onlyNTTCOM	670 100%	67

AS-SET

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

Route object: RIR11
Route object: not announced7

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.115.136.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	45.115.137.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.53.0.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.53.1.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.53.2.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.53.3.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	45.115.136.0/23	Route object only in NTTCOM. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.115.138.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.115.139.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	103.53.0.0/23	Route object only in NTTCOM. Add it in the RIR database for the space.	670 of 673
Route object: RIR	103.53.2.0/23	Route object only in NTTCOM. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.115.136.0/24

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

673 of 673

Route object: RIR

45.115.137.0/24

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

673 of 673

Route object: RIR

103.53.0.0/24

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

673 of 673

Route object: RIR

103.53.1.0/24

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

673 of 673

Route object: RIR

103.53.2.0/24

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

673 of 673

Route object: RIR

103.53.3.0/24

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

673 of 673

Route object: RIR

45.115.136.0/23

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

670 of 673

Route object: RIR

45.115.138.0/24

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

670 of 673

Route object: RIR

45.115.139.0/24

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

670 of 673

Route object: RIR

103.53.0.0/23

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

670 of 673

Route object: RIR

103.53.2.0/23

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

670 of 673

Route objects not announced

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


45.115.136.0/22	APNIC, NTTCOM, RADB	Valid
103.53.0.0/22	APNIC, NTTCOM, RADB	Valid
203.57.24.0/23	NTTCOM	No ROA
203.57.24.0/24	NTTCOM, RADB	No ROA
203.57.25.0/24	NTTCOM, RADB	No ROA
2402:2680::/32	NTTCOM	Valid
2402:2680::/48	NTTCOM	Valid

45.115.136.0/22

APNIC, NTTCOM, RADB

Valid

103.53.0.0/22

APNIC, NTTCOM, RADB

Valid

203.57.24.0/23

NTTCOM

No ROA

203.57.24.0/24

NTTCOM, RADB

No ROA

203.57.25.0/24

NTTCOM, RADB

No ROA

2402:2680::/32

NTTCOM

Valid

2402:2680::/48

NTTCOM

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.