bgpreport

Network · data from 2026-11-12

AS55564 JETNET-AU - Malcolm Weatherley

Registry name: JETNET-AU - Malcolm Weatherley, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55564, 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.
2406:ae00:a::/48 No ROA Nonecovered by 2406:ae00::/32 635 100% 69
2406:ae00:f00d::/48 No ROA Nonecovered by 2406:ae00::/32 635 100% 69
103.212.240.0/24 No ROA None 252 37% 62
103.212.241.0/24 No ROA None 252 37% 62
2406:ae00:100::/48 No ROA Other IRR onlyRADB 636 100% 69
27.112.72.0/24 No ROA RIR databaseAPNIC 670 100% 67
27.112.73.0/24 No ROA RIR databaseAPNIC 670 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2406:ae00:a::/48No ROA covers it. Add a ROA for AS55564, maxLength 48.635 of 636
Route object: none2406:ae00:a::/48No route object for it. A route object for 2406:ae00::/32 with origin AS55564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55564 in the RIR database for the space.635 of 636
ROA: none2406:ae00:f00d::/48No ROA covers it. Add a ROA for AS55564, maxLength 48.635 of 636
Route object: none2406:ae00:f00d::/48No route object for it. A route object for 2406:ae00::/32 with origin AS55564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55564 in the RIR database for the space.635 of 636
ROA: none103.212.240.0/24No ROA covers it. Add a ROA for AS55564, maxLength 24.252 of 673
Route object: none103.212.240.0/24No route object for it. Add a route object with origin AS55564 in the RIR database for the space.252 of 673
ROA: none103.212.241.0/24No ROA covers it. Add a ROA for AS55564, maxLength 24.252 of 673
Route object: none103.212.241.0/24No route object for it. Add a route object with origin AS55564 in the RIR database for the space.252 of 673
ROA: none2406:ae00:100::/48No ROA covers it. Add a ROA for AS55564, maxLength 48.636 of 636
Route object: RIR2406:ae00:100::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none27.112.72.0/24No ROA covers it. Add a ROA for AS55564, maxLength 24.670 of 673
ROA: none27.112.73.0/24No ROA covers it. Add a ROA for AS55564, maxLength 24.670 of 673

Route objects not announced

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

27.112.74.0/24APNICNo ROA
27.112.75.0/24APNICNo ROA
2406:ae00::/32RADBNo 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.