bgpreport

Network · data from 2026-11-12

AS38749 RCOM International

Registry name: RCOM-AS-AU - RCOM International. Managed Services, VOIP. Perth Australia, AU · PeeringDB

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

Announced routes

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

59.191.231.0/24 No ROA None 672 100% 67
59.191.224.0/21 No ROA Other origin only 671 100% 67
59.191.224.0/24 No ROA Other IRR onlyRADB 672 100% 67
59.191.225.0/24 No ROA Other IRR onlyRADB 672 100% 67
59.191.226.0/24 No ROA Other IRR onlyRADB 672 100% 67
59.191.227.0/24 No ROA Other IRR onlyRADB 672 100% 67
59.191.228.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS38749's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none59.191.231.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: none59.191.231.0/24No route object for it. Add a route object with origin AS38749 in the RIR database for the space.672 of 673
ROA: none59.191.224.0/21No ROA covers it. Add a ROA for AS38749, maxLength 21.671 of 673
Route object: none59.191.224.0/21Route objects for it name AS9398, AS10084. Add a route object with origin AS38749 in the RIR database for the space.671 of 673
ROA: none59.191.224.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: RIR59.191.224.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none59.191.225.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: RIR59.191.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none59.191.226.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: RIR59.191.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none59.191.227.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: RIR59.191.227.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none59.191.228.0/24No ROA covers it. Add a ROA for AS38749, maxLength 24.672 of 673
Route object: RIR59.191.228.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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