bgpreport

Network · data from 2026-11-12

AS132641 Netciti Persada

Registry name: NETCITI-AS-ID - PT Netciti Persada, ID · PeeringDB

38IPv4 routes 94.7% RPKI valid · 84.2% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 6 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS132641, seen from no peer

Announced routes

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

38.102.78.0/24 No ROA None 2 0%low visibility 2
38.102.79.0/24 No ROA None 2 0%low visibility 2
103.41.120.0/24 Valid None 673 100% 69
103.41.121.0/24 Valid None 673 100% 69
103.41.122.0/24 Valid None 673 100% 69
103.41.123.0/24 Valid None 673 100% 69
103.19.110.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.19.111.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.83.172.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
103.83.175.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
103.145.219.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
103.145.240.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
103.145.245.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
43.251.96.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
43.251.97.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
43.251.98.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
43.251.99.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
103.19.108.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
103.19.109.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
103.83.173.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.83.174.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.84.4.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.84.5.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.84.6.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.84.7.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.145.218.0/24 Valid Other IRR onlyRADB 672 100% 69
103.145.224.0/24 Valid Other IRR onlyNTTCOM 672 100% 69
103.145.244.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
2406:a500:c3e7::/48 Valid Other IRR onlyRADB 636 100% 69
103.145.225.0/24 Valid Other IRR onlyNTTCOM 35 5%low visibility 28
103.145.241.0/24 Valid Other IRR onlyNTTCOM 35 5%low visibility 28
103.132.141.0/24 Valid RIR databaseAPNIC 673 100% 69
103.132.142.0/24 Valid RIR databaseAPNIC 673 100% 69
103.132.143.0/24 Valid RIR databaseAPNIC 673 100% 69
103.253.112.0/24 Valid RIR databaseAPNIC 673 100% 69
103.253.113.0/24 Valid RIR databaseAPNIC 673 100% 69
103.253.114.0/24 Valid RIR databaseAPNIC 673 100% 69
103.132.140.0/24 Valid RIR databaseAPNIC 672 100% 69
103.253.115.0/24 Valid RIR databaseAPNIC 672 100% 69

AS-SET

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

NameDatabaseASNsSets Route objectsAS132641 in itNot covered
AS-NETCITI 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 51 are in fix.csv.

  • ROA: none2
  • Route object: none6
  • Route object: RIR25
  • AS-SET: not found1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none38.102.78.0/24No ROA covers it. Add a ROA for AS132641, maxLength 24.2 of 673
Route object: none38.102.78.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.2 of 673
ROA: none38.102.79.0/24No ROA covers it. Add a ROA for AS132641, maxLength 24.2 of 673
Route object: none38.102.79.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.2 of 673
Route object: none103.41.120.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.673 of 673
Route object: none103.41.121.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.673 of 673
Route object: none103.41.122.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.673 of 673
Route object: none103.41.123.0/24No route object for it. Add a route object with origin AS132641 in the RIR database for the space.673 of 673
Route object: RIR103.19.110.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.19.111.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.83.172.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR103.83.175.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR103.145.219.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR103.145.240.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR103.145.245.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.251.96.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.251.97.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.251.98.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.251.99.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.19.108.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.19.109.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.83.173.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.83.174.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.84.4.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.84.5.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.84.6.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.84.7.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.145.218.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.145.224.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.145.244.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2406:a500:c3e7::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR103.145.225.0/24Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR103.145.241.0/24Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
AS-SET: not foundAS-NETCITIPeeringDB names AS-NETCITI; no IRR database read has it.

Route objects not announced

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

43.251.96.0/22RADBValid
103.19.108.0/22RADBValid
103.83.172.0/22APNIC, RADBValid
103.84.4.0/22APNIC, RADBValid
103.132.140.0/22APNICValid
103.132.140.0/23APNICValid
103.132.142.0/23APNICValid
103.145.218.0/23RADBValid
103.145.224.0/23RADBValid
103.145.240.0/22RADBNo ROA
103.145.244.0/23RADBValid
103.252.50.0/23RADBNo ROA
103.253.112.0/22APNICValid
103.253.112.0/23APNICValid
103.253.114.0/23APNICValid
2406:a500::/48RADBNo ROA
2406:a500:777::/48RADBNo ROA

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.