bgpreport

Network · data from 2026-11-12

AS134119 CNWAPL-AS-AP - Cirrus Networks (WA) Pty Ltd

Registry name: CNWAPL-AS-AP - Cirrus Networks (WA) Pty Ltd, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134119, 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.54.68.0/22 No ROA None 671 100% 67
103.138.23.0/24 No ROA None 422 63% 66
2402:3380::/32 No ROA None 341 54% 63
103.54.69.0/24 Valid Other IRR onlyNTTCOM 22 3%low visibility 8
103.54.70.0/24 Valid Other IRR onlyNTTCOM 22 3%low visibility 8
103.54.71.0/24 Valid Other IRR onlyNTTCOM 22 3%low visibility 8

AS-SET

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

  • ROA: none3
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.54.68.0/22No ROA covers it. Add a ROA for AS134119, maxLength 22.671 of 673
Route object: none103.54.68.0/22No route object for it. Add a route object with origin AS134119 in the RIR database for the space.671 of 673
ROA: none103.138.23.0/24No ROA covers it. Add a ROA for AS134119, maxLength 24.422 of 673
Route object: none103.138.23.0/24No route object for it. Add a route object with origin AS134119 in the RIR database for the space.422 of 673
ROA: none2402:3380::/32No ROA covers it. Add a ROA for AS134119, maxLength 32.341 of 636
Route object: none2402:3380::/32No route object for it. Add a route object with origin AS134119 in the RIR database for the space.341 of 636
Route object: RIR103.54.69.0/24Route object only in NTTCOM. Add it in the RIR database for the space.22 of 673
Route object: RIR103.54.70.0/24Route object only in NTTCOM. Add it in the RIR database for the space.22 of 673
Route object: RIR103.54.71.0/24Route object only in NTTCOM. Add it in the RIR database for the space.22 of 673

Route objects not announced

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

103.54.68.0/23NTTCOMNo ROA
103.54.68.0/24APNIC, NTTCOMValid
103.54.70.0/23NTTCOMNo ROA
2402:3380:1::/64APNICNo 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.