bgpreport

Network · data from 2026-11-12

AS138525 MINIPORTPTYLTD-AS-AP - Miniport Pty Ltd

Registry name: MINIPORTPTYLTD-AS-AP - Miniport Pty Ltd, AU · not in PeeringDB

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

Announced routes

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

103.127.244.0/24 No ROA Other origin onlycovered by 103.127.244.0/22 669 99% 67
103.127.246.0/24 No ROA Other origin onlycovered by 103.127.244.0/22 669 99% 67
103.81.217.0/24 No ROA None 241 36% 60
2404:2ac0::/32 No ROA Other IRR onlyRADB 322 51% 63
103.127.247.0/24 No ROA RIR databaseAPNIC, RADB 669 99% 67

AS-SET

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.127.244.0/24No ROA covers it. Add a ROA for AS138525, maxLength 24.669 of 673
Route object: none103.127.244.0/24Route objects for it name AS17766. A route object for 103.127.244.0/22 with origin AS138525 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138525 in the RIR database for the space.669 of 673
ROA: none103.127.246.0/24No ROA covers it. Add a ROA for AS138525, maxLength 24.669 of 673
Route object: none103.127.246.0/24Route objects for it name AS17766, AS63956. A route object for 103.127.244.0/22 with origin AS138525 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138525 in the RIR database for the space.669 of 673
ROA: none103.81.217.0/24No ROA covers it. Add a ROA for AS138525, maxLength 24.241 of 673
Route object: none103.81.217.0/24No route object for it. Add a route object with origin AS138525 in the RIR database for the space.241 of 673
ROA: none2404:2ac0::/32No ROA covers it. Add a ROA for AS138525, maxLength 32.322 of 636
Route object: RIR2404:2ac0::/32Route object only in RADB. Add it in the RIR database for the space.322 of 636
ROA: none103.127.247.0/24No ROA covers it. Add a ROA for AS138525, maxLength 24.669 of 673

Route objects not announced

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

103.127.244.0/22RADBNo 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.