bgpreport

Network · data from 2026-11-12

AS58552 Multidata Rancana Prima

Registry name: MULTIDATA-ID-AP - PT Multidata Rancana Prima, ID · PeeringDB

3IPv4 routes 66.7% RPKI valid · 33.3% with a route object
7IPv6 routes 57.1% RPKI valid · 14.3% with a route object
1RPKI invalid 1 origin · 0 maxLength
3No ROA 8 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS58552, seen from no peer

Announced routes

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

43.240.230.0/24 Invalid: origin Other origin only 4 1%low visibility 4
2401:a0a0:5::/48 No ROA None 631 99% 68
2401:a0a0:7::/48 No ROA None 329 52% 63
2401:a0a0:4::/48 No ROA None 1 0%low visibility 2
2404:fd00::/32 Valid None 634 100% 69
2404:fd00:1f::/48 Valid None 631 99% 69
2404:fd00:14::/48 Valid None 346 54% 63
103.11.29.0/24 Valid Other origin only 219 33% 57
2404:fd00:20::/48 Valid Other IRR onlyRADB 636 100% 69
43.240.231.0/24 Valid Other IRR onlyRADB 219 33% 57

AS-SET

PeeringDB's irr_as_set for AS58552: RADB::AS-MULTIDATA-ID-AP. 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 (AS58552 isn't in the set, or no route object for AS58552 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 objectsAS58552 in itNot covered
RADB::AS-MULTIDATA-ID-AP RADB2 member sets in no database: AS131717:AS-CIFO, AS47311:AS-ATHARVA 322210,385 Yes 8

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

  • ROA: origin1
  • ROA: none3
  • Route object: none8
  • Route object: RIR2
  • AS-SET: missing member2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin43.240.230.0/24ROAs covering it name AS58389, not AS58552. If AS58552 should announce it, add a ROA for AS58552.4 of 673
Route object: none43.240.230.0/24Route objects for it name AS58389. Add a route object with origin AS58552 in the RIR database for the space.4 of 673
ROA: none2401:a0a0:5::/48No ROA covers it. Add a ROA for AS58552, maxLength 48.631 of 636
Route object: none2401:a0a0:5::/48No route object for it. Add a route object with origin AS58552 in the RIR database for the space.631 of 636
ROA: none2401:a0a0:7::/48No ROA covers it. Add a ROA for AS58552, maxLength 48.329 of 636
Route object: none2401:a0a0:7::/48No route object for it. Add a route object with origin AS58552 in the RIR database for the space.329 of 636
ROA: none2401:a0a0:4::/48No ROA covers it. Add a ROA for AS58552, maxLength 48.1 of 636
Route object: none2401:a0a0:4::/48No route object for it. Add a route object with origin AS58552 in the RIR database for the space.1 of 636
Route object: none2404:fd00::/32No route object for it. Add a route object with origin AS58552 in the RIR database for the space.634 of 636
Route object: none2404:fd00:1f::/48No route object for it. Add a route object with origin AS58552 in the RIR database for the space.631 of 636
Route object: none2404:fd00:14::/48No route object for it. Add a route object with origin AS58552 in the RIR database for the space.346 of 636
Route object: none103.11.29.0/24Route objects for it name AS58389. Add a route object with origin AS58552 in the RIR database for the space.219 of 673
Route object: RIR2404:fd00:20::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR43.240.231.0/24Route object only in RADB. Add it in the RIR database for the space.219 of 673
AS-SET: missing memberRADB::AS-MULTIDATA-ID-APAS-MULTIDATA-ID-AP (RADB) lists AS131717:AS-CIFO; no IRR database read has it.
AS-SET: missing memberRADB::AS-MULTIDATA-ID-APAS-MULTIDATA-ID-AP (RADB) lists AS47311:AS-ATHARVA; no IRR database read has it.

Route objects not announced

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

202.72.192.0/20RADBNo ROA
202.72.194.0/24APNIC, RADBValid
202.72.198.0/24APNIC, RADBValid
202.72.199.0/24RADBValid
202.72.203.0/24RADBValid
202.72.204.0/23RADBValid
202.72.204.0/24APNIC, RADBValid
202.72.205.0/24APNIC, RADBValid
2001:470:203::/48ARINInvalid: origin

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.