Network · data from 2026-11-12

AS10105 OMNI

Registry name: OMNI - OMNIconnect Pty Ltd, AU · PeeringDB

14IPv4 routes 78.6% RPKI valid · 78.6% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

3RPKI invalid 0 origin · 3 maxLength

0No ROA 3 with no route object for this origin

3Low visibility seen by under 10% of full-table peers

24Route objects not announced registered with origin AS10105, seen from no peer

Announced routes

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


203.143.65.0/24	Invalid: maxLength	Nonecovered by 203.143.64.0/23	39 6%low visibility	23
203.143.66.0/24	Invalid: maxLength	Nonecovered by 203.143.66.0/23	39 6%low visibility	23
203.143.68.0/24	Invalid: maxLength	Nonecovered by 203.143.64.0/20	39 6%low visibility	23
117.104.160.0/21	Valid	RIR databaseAPNIC	672 100%	67
203.143.64.0/20	Valid	RIR databaseAPNIC	672 100%	67
203.143.64.0/24	Valid	RIR databaseAPNIC	672 100%	67
203.143.66.0/23	Valid	RIR databaseAPNIC	672 100%	67
203.143.67.0/24	Valid	RIR databaseAPNIC	672 100%	67
203.143.70.0/23	Valid	RIR databaseAPNIC	672 100%	67
203.143.79.0/24	Valid	RIR databaseAPNIC	672 100%	67
203.143.80.0/23	Valid	RIR databaseAPNIC	672 100%	67
203.143.92.0/22	Valid	RIR databaseAPNIC	672 100%	67
203.143.94.0/23	Valid	RIR databaseAPNIC	672 100%	67
45.125.124.0/24	Valid	RIR databaseAPNIC	671 100%	67
2400:6800::/32	Valid	RIR databaseAPNIC, RADB	636 100%	68

203.143.65.0/24

Invalid: maxLength

Nonecovered by 203.143.64.0/23

39 6%low visibility

203.143.66.0/24

Invalid: maxLength

Nonecovered by 203.143.66.0/23

39 6%low visibility

203.143.68.0/24

Invalid: maxLength

Nonecovered by 203.143.64.0/20

39 6%low visibility

117.104.160.0/21

Valid

RIR databaseAPNIC

672 100%

203.143.64.0/20

Valid

RIR databaseAPNIC

672 100%

203.143.64.0/24

Valid

RIR databaseAPNIC

672 100%

203.143.66.0/23

Valid

RIR databaseAPNIC

672 100%

203.143.67.0/24

Valid

RIR databaseAPNIC

672 100%

203.143.70.0/23

Valid

RIR databaseAPNIC

672 100%

203.143.79.0/24

Valid

RIR databaseAPNIC

672 100%

203.143.80.0/23

Valid

RIR databaseAPNIC

672 100%

203.143.92.0/22

Valid

RIR databaseAPNIC

672 100%

203.143.94.0/23

Valid

RIR databaseAPNIC

672 100%

45.125.124.0/24

Valid

RIR databaseAPNIC

671 100%

2400:6800::/32

Valid

RIR databaseAPNIC, RADB

636 100%

AS-SET

AS10105'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 30 are in fix.csv.

ROA: maxLength3
Route object: none3
Route object: not announced24

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	203.143.65.0/24	ROA 203.143.64.0/20 AS10105 has maxLength 20; ROA 203.143.64.0/23 AS10105 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.143.65.0/24.	39 of 673
Route object: none	203.143.65.0/24	No route object for it. A route object for 203.143.64.0/23 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.	39 of 673
ROA: maxLength	203.143.66.0/24	ROA 203.143.64.0/20 AS10105 has maxLength 20; ROA 203.143.66.0/23 AS10105 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.143.66.0/24.	39 of 673
Route object: none	203.143.66.0/24	No route object for it. A route object for 203.143.66.0/23 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.	39 of 673
ROA: maxLength	203.143.68.0/24	ROA 203.143.64.0/20 AS10105 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.143.68.0/24.	39 of 673
Route object: none	203.143.68.0/24	No route object for it. A route object for 203.143.64.0/20 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.	39 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

203.143.65.0/24

ROA 203.143.64.0/20 AS10105 has maxLength 20; ROA 203.143.64.0/23 AS10105 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.143.65.0/24.

39 of 673

Route object: none

203.143.65.0/24

No route object for it. A route object for 203.143.64.0/23 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.

39 of 673

ROA: maxLength

203.143.66.0/24

ROA 203.143.64.0/20 AS10105 has maxLength 20; ROA 203.143.66.0/23 AS10105 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.143.66.0/24.

39 of 673

Route object: none

203.143.66.0/24

No route object for it. A route object for 203.143.66.0/23 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.

39 of 673

ROA: maxLength

203.143.68.0/24

ROA 203.143.64.0/20 AS10105 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.143.68.0/24.

39 of 673

Route object: none

203.143.68.0/24

No route object for it. A route object for 203.143.64.0/20 with origin AS10105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10105 in the RIR database for the space.

39 of 673

Route objects not announced

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


117.104.160.0/22	APNIC	Valid
117.104.160.0/23	APNIC	Valid
117.104.160.0/24	APNIC	Valid
117.104.161.0/24	APNIC	Valid
117.104.162.0/23	APNIC	Valid
117.104.162.0/24	APNIC	Valid
117.104.163.0/24	APNIC	Valid
117.104.164.0/22	APNIC	Valid
117.104.164.0/23	APNIC	Valid
117.104.164.0/24	APNIC	Valid
117.104.165.0/24	APNIC	Valid
117.104.166.0/23	APNIC	Valid
117.104.166.0/24	APNIC	Valid
117.104.167.0/24	APNIC	Valid
203.8.105.0/24	RADB	No ROA
203.10.80.0/22	RADB	No ROA
203.19.164.0/23	RADB	No ROA
203.143.64.0/23	APNIC	Valid
203.143.70.0/24	APNIC	Valid
203.143.72.0/24	APNIC	Valid
203.143.80.0/24	APNIC	Valid
203.143.81.0/24	APNIC	Valid
203.143.91.0/24	APNIC	Valid
203.143.94.0/24	APNIC	Valid

117.104.160.0/22

APNIC

Valid

117.104.160.0/23

APNIC

Valid

117.104.160.0/24

APNIC

Valid

117.104.161.0/24

APNIC

Valid

117.104.162.0/23

APNIC

Valid

117.104.162.0/24

APNIC

Valid

117.104.163.0/24

APNIC

Valid

117.104.164.0/22

APNIC

Valid

117.104.164.0/23

APNIC

Valid

117.104.164.0/24

APNIC

Valid

117.104.165.0/24

APNIC

Valid

117.104.166.0/23

APNIC

Valid

117.104.166.0/24

APNIC

Valid

117.104.167.0/24

APNIC

Valid

203.8.105.0/24

RADB

No ROA

203.10.80.0/22

RADB

No ROA

203.19.164.0/23

RADB

No ROA

203.143.64.0/23

APNIC

Valid

203.143.70.0/24

APNIC

Valid

203.143.72.0/24

APNIC

Valid

203.143.80.0/24

APNIC

Valid

203.143.81.0/24

APNIC

Valid

203.143.91.0/24

APNIC

Valid

203.143.94.0/24

APNIC

Valid

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.