bgpreport

Network · data from 2026-11-12

AS147168 SGCC

Registry name: NTTINDONESIA-AS-ID - PT NTT Indonesia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS147168, 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.171.8.0/24 Valid Other origin only 670 100% 68
2404:c8:8::/48 Valid None 634 100% 68
103.178.8.0/24 Valid Other IRR onlyNTTCOM 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS147168: AS147168:AS-SET-JKTIX. 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 (AS147168 isn't in the set, or no route object for AS147168 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 objectsAS147168 in itNot covered
AS147168:AS-SET-JKTIX NTTCOM12 member sets in no database: AS-BCMEDIA, AS-BOSTI, AS-KDINDO, AS-LINTASDATA-AS-ID, AS-NETCITI … 504517,950 Yes 2

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

  • Route object: none2
  • Route object: RIR1
  • AS-SET: missing member12
ChangePrefix or setDetailFull-table peers
Route object: none202.171.8.0/24Route objects for it name AS4657. Add a route object with origin AS147168 in the RIR database for the space.670 of 673
Route object: none2404:c8:8::/48No route object for it. Add a route object with origin AS147168 in the RIR database for the space.634 of 636
Route object: RIR103.178.8.0/24Route object only in NTTCOM. Add it in the RIR database for the space.669 of 673
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS-BCMEDIA; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS-BOSTI; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS-KDINDO; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS-LINTASDATA-AS-ID; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS-NETCITI; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS150196:AS-ARTHALOKA-ID; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS150238:AS-SHARTEL; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS150249:AS-ATHARVA; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS150501:AS-HCI; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS150552:AS-BAROKAHNET; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS63883:AS-CLOUDSERVERS; no IRR database read has it.
AS-SET: missing memberAS147168:AS-SET-JKTIXAS147168:AS-SET-JKTIX (NTTCOM) lists AS9251:AS-INTERLINK; no IRR database read has it.

Route objects not announced

Every route object with origin AS147168 is announced.

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.