bgpreport

Network · data from 2026-11-12

AS38508 CBN-CARRIER-AS-ID - PT. Cyberindo Aditama

Registry name: CBN-CARRIER-AS-ID - PT. Cyberindo Aditama, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38508, 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.
101.50.18.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2402:9800:4003::/48 Valid Other IRR onlyRADB 634 100% 69

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin101.50.18.0/24ROAs covering it name AS4787, not AS38508. If AS38508 should announce it, add a ROA for AS38508.2 of 673
Route object: none101.50.18.0/24Route objects for it name AS4787. Add a route object with origin AS38508 in the RIR database for the space.2 of 673
Route object: RIR2402:9800:4003::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS38508 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.