bgpreport

Network · data from 2026-11-12

AS24202 PAKTELNET-AS-ID - PT. PASIFIKTEL INDOTAMA

Registry name: PAKTELNET-AS-ID - PT. PASIFIKTEL INDOTAMA, ID · not in PeeringDB

8IPv4 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
22Route objects not announced registered with origin AS24202, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24202, 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.
202.87.240.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.241.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.242.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.243.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.244.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.245.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.246.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.87.247.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67

AS-SET

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

  • Route object: RIR8
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: RIR202.87.240.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.241.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.242.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.243.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.244.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.245.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.246.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.87.247.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

123.108.96.0/21NTTCOMNo ROA
123.108.96.0/22NTTCOMNo ROA
123.108.96.0/23NTTCOMNo ROA
123.108.96.0/24NTTCOMNo ROA
123.108.97.0/24NTTCOM, RADBNo ROA
123.108.98.0/23NTTCOMNo ROA
123.108.98.0/24NTTCOMNo ROA
123.108.99.0/24NTTCOMNo ROA
123.108.100.0/22NTTCOMNo ROA
123.108.100.0/23NTTCOMNo ROA
123.108.100.0/24NTTCOMNo ROA
123.108.101.0/24NTTCOMNo ROA
123.108.102.0/23NTTCOMNo ROA
123.108.102.0/24NTTCOMNo ROA
123.108.103.0/24NTTCOMNo ROA
202.87.240.0/21NTTCOM, RADBValid
202.87.240.0/22NTTCOM, RADBValid
202.87.240.0/23NTTCOM, RADBValid
202.87.242.0/23NTTCOM, RADBValid
202.87.244.0/22NTTCOM, RADBValid
202.87.244.0/23NTTCOM, RADBValid
202.87.246.0/23NTTCOM, RADBValid

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.