bgpreport

Network · data from 2026-11-12

AS138884 Centronet Data Indonesia

Registry name: CENTRONETWORK-AS-ID - PT Centronet Data Indonesia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138884, 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.
103.94.250.0/24 Valid Other IRR onlyRADB 673 100% 70
103.138.71.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 70
103.138.70.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
2404:ce40::/32 Valid Other IRR onlyRADB 635 100% 67
103.94.251.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
103.94.250.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
103.138.70.0/23 Valid RIR databaseAPNIC 672 100% 69

AS-SET

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

  • Route object: RIR6
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR103.94.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.138.71.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.138.70.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2404:ce40::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR103.94.251.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR103.94.250.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
AS-SET: not foundAS138884:AS-CENTRONETPeeringDB names AS138884:AS-CENTRONET; no IRR database read has it.

Route objects not announced

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

2404:ce40::/36RADBValid
2404:ce40:1000::/36RADBValid

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.