bgpreport

Network · data from 2026-11-12

AS55736 DataKnox-DNX

Registry name: DataKnox-DNX - Dataknox Pty Limited, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55736, 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.160.130.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 69
103.160.131.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 69
202.157.179.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 69
2001:df5:9780::/48 No ROA RIR databaseAPNIC 635 100% 69
103.164.128.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.164.129.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
123.100.228.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
123.100.229.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
123.100.230.0/24 Valid RIR databaseAPNIC 672 100% 69
123.100.231.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
202.157.178.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
203.142.9.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
2405:70c0::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS55736'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 11 are in fix.csv.

  • ROA: none4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none103.160.130.0/24No ROA covers it. Add a ROA for AS55736, maxLength 24.672 of 673
ROA: none103.160.131.0/24No ROA covers it. Add a ROA for AS55736, maxLength 24.672 of 673
ROA: none202.157.179.0/24No ROA covers it. Add a ROA for AS55736, maxLength 24.672 of 673
ROA: none2001:df5:9780::/48No ROA covers it. Add a ROA for AS55736, maxLength 48.635 of 636

Route objects not announced

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

123.100.233.0/24RADBNo ROA
170.200.83.0/24RADBNo ROA
170.200.85.0/24RADBNo ROA
202.157.178.0/23RADBNo ROA
203.61.170.0/24RADBNo ROA
203.62.170.0/24RADBNo ROA
203.142.8.0/24RADBNo 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.