bgpreport

Network · data from 2026-11-12

AS45325 PT PC24 Telekomunikasi Indonesia

Registry name: PC24NET-AS-ID - PT PC24 Telekomunikasi Indonesia, ID · PeeringDB

32IPv4 routes 62.5% RPKI valid · 65.6% with a route object
3IPv6 routes 33.3% RPKI valid · 0.0% with a route object
10RPKI invalid 10 origin · 0 maxLength
4No ROA 14 with no route object for this origin
14Low visibility seen by under 10% of full-table peers
28Route objects not announced registered with origin AS45325, seen from no peer

Announced routes

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

157.66.52.0/24 Invalid: origin None 2 0%low visibility 1
157.66.53.0/24 Invalid: origin None 2 0%low visibility 1
157.66.112.0/24 Invalid: origin None 2 0%low visibility 1
157.66.113.0/24 Invalid: origin None 2 0%low visibility 1
157.66.114.0/24 Invalid: origin None 2 0%low visibility 1
157.66.115.0/24 Invalid: origin None 2 0%low visibility 1
157.66.116.0/24 Invalid: origin None 2 0%low visibility 1
157.66.117.0/24 Invalid: origin None 2 0%low visibility 1
157.66.136.0/24 Invalid: origin None 2 0%low visibility 1
157.66.137.0/24 Invalid: origin None 2 0%low visibility 1
2001:df3:3580::/48 No ROA None 1 0%low visibility 2
2001:df5:1280::/48 No ROA None 1 0%low visibility 2
103.149.180.0/24 No ROA Other IRR onlyRADB 672 100% 67
157.15.119.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.146.182.0/24 Valid None 672 100% 67
2001:df7:880::/48 Valid None 1 0%low visibility 2
122.248.35.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
122.248.40.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.3.68.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
103.3.69.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
122.248.46.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
122.248.32.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.33.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.34.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.36.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.38.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.39.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.41.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.43.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.45.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
202.43.112.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
202.43.113.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
203.30.254.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
203.30.255.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
122.248.42.0/24 Valid Other IRR onlyNTTCOM, RADB 32 5%low visibility 26

AS-SET

PeeringDB's irr_as_set for AS45325: AS45325:AS-PC24. 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 (AS45325 isn't in the set, or no route object for AS45325 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 objectsAS45325 in itNot covered
AS45325:AS-PC24 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 78 are in fix.csv.

  • ROA: origin10
  • ROA: none4
  • Route object: none14
  • Route object: RIR21
  • AS-SET: not found1
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: origin157.66.52.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.52.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.53.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.53.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.112.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.112.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.113.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.113.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.114.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.114.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.115.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.115.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.116.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.116.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.117.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.117.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.136.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.136.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: origin157.66.137.0/24ROAs covering it name AS4800, not AS45325. If AS45325 should announce it, add a ROA for AS45325.2 of 673
Route object: none157.66.137.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.2 of 673
ROA: none2001:df3:3580::/48No ROA covers it. Add a ROA for AS45325, maxLength 48.1 of 636
Route object: none2001:df3:3580::/48No route object for it. Add a route object with origin AS45325 in the RIR database for the space.1 of 636
ROA: none2001:df5:1280::/48No ROA covers it. Add a ROA for AS45325, maxLength 48.1 of 636
Route object: none2001:df5:1280::/48No route object for it. Add a route object with origin AS45325 in the RIR database for the space.1 of 636
ROA: none103.149.180.0/24No ROA covers it. Add a ROA for AS45325, maxLength 24.672 of 673
Route object: RIR103.149.180.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none157.15.119.0/24No ROA covers it. Add a ROA for AS45325, maxLength 24.672 of 673
Route object: RIR157.15.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none103.146.182.0/24No route object for it. Add a route object with origin AS45325 in the RIR database for the space.672 of 673
Route object: none2001:df7:880::/48No route object for it. Add a route object with origin AS45325 in the RIR database for the space.1 of 636
Route object: RIR122.248.35.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.248.40.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.3.68.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.3.69.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR122.248.46.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR122.248.32.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.33.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.34.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.36.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.38.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.39.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.41.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.43.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.45.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.43.112.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.43.113.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.30.254.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.30.255.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR122.248.42.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.32 of 673
AS-SET: not foundAS45325:AS-PC24PeeringDB names AS45325:AS-PC24; no IRR database read has it.

Route objects not announced

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

22.243.32.0/23NTTCOMNo ROA
22.243.32.0/24NTTCOMNo ROA
22.243.33.0/24NTTCOMNo ROA
103.3.68.0/23APNIC, RADBValid
103.151.140.0/24RADBValid
103.169.206.0/24RADBValid
103.169.207.0/24RADBValid
122.248.32.0/20APNIC, NTTCOMNo ROA
122.248.32.0/21NTTCOM, RADBNo ROA
122.248.32.0/22NTTCOM, RADBNo ROA
122.248.32.0/23NTTCOM, RADBNo ROA
122.248.34.0/23NTTCOM, RADBNo ROA
122.248.36.0/22NTTCOM, RADBNo ROA
122.248.36.0/23NTTCOM, RADBNo ROA
122.248.38.0/23NTTCOM, RADBNo ROA
122.248.40.0/21NTTCOM, RADBNo ROA
122.248.40.0/22NTTCOM, RADBNo ROA
122.248.40.0/23NTTCOM, RADBNo ROA
122.248.42.0/23NTTCOM, RADBNo ROA
122.248.44.0/22NTTCOM, RADBNo ROA
122.248.44.0/23NTTCOM, RADBNo ROA
122.248.44.0/24NTTCOM, RADBValid
122.248.46.0/23NTTCOM, RADBNo ROA
122.248.47.0/24NTTCOM, RADBValid
202.43.112.0/23NTTCOM, RADBNo ROA
202.58.242.0/23NTTCOM, RADBNo ROA
202.58.243.0/24NTTCOM, RADBValid
203.30.254.0/23NTTCOMNo 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.