bgpreport

Network · data from 2026-11-12

AS150265 Rajawali Bintang Cemerlang Telkomedia

Registry name: IDNIC-RACEMEDIA-AS-ID - PT Rajawali Bintang Cemerlang Telkomedia, ID · PeeringDB

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

Announced routes

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

210.87.78.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.191.60.0/24 Valid Other IRR onlyRADB 673 100% 70
103.90.66.0/24 Valid RIR databaseAPNIC 673 100% 69
103.90.67.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69

AS-SET

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

  • ROA: none1
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none210.87.78.0/24No ROA covers it. Add a ROA for AS150265, maxLength 24.2 of 673
Route object: RIR210.87.78.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR103.191.60.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: not foundAS150265:AS-IDPeeringDB names AS150265:AS-ID; no IRR database read has it.

Route objects not announced

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

103.68.2.0/24RADBValid

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.