bgpreport

Network · data from 2026-11-12

AS150552 BarokahNet

Registry name: BAROKAHNET-AS-ID - PT Link Data Sumber Barokah, ID · PeeringDB

3IPv4 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
1Route objects not announced registered with origin AS150552, seen from no peer

Announced routes

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

2001:df2:84c0::/48 Valid Other IRR onlyRADB 635 100% 70
103.86.116.0/23 Valid RIR databaseAPNIC, RADB 672 100% 69
103.86.116.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 29
103.86.117.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 29

AS-SET

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

  • Route object: RIR1
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR2001:df2:84c0::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS150552:AS-BAROKAHNETPeeringDB names AS150552:AS-BAROKAHNET; no IRR database read has it.

Route objects not announced

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

103.131.28.0/23RADBNo 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.