Network · data from 2026-11-12

AS43775 DSP-AS Digital Solutions Provider

Registry name: DSP-AS Digital Solutions Provider, SA · not in PeeringDB

29IPv4 routes 96.6% RPKI valid · 96.6% with a route object

0IPv6 routes

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

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

23Route objects not announced registered with origin AS43775, seen from no peer

Announced routes

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


91.147.144.0/20	Invalid: maxLength	Nonecovered by 91.147.128.0/19	165 25%	56
91.147.132.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.133.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.134.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.135.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.152.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.153.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.154.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.156.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.157.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.158.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.159.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.160.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.161.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.162.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.171.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.173.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.175.0/24	Valid	RIR databaseRIPE	673 100%	67
91.147.180.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.181.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.183.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.184.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.185.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.187.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.188.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.189.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.190.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.191.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.147.160.0/20	Valid	RIR databaseRIPE	672 100%	67

AS-SET

AS43775 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 25 are in fix.csv.

ROA: maxLength1
Route object: none1
Route object: not announced23

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	91.147.144.0/20	ROA 91.147.128.0/19 AS43775 has maxLength 19; the route is a /20. Raise the maxLength, or add a ROA for 91.147.144.0/20.	165 of 673
Route object: none	91.147.144.0/20	No route object for it. A route object for 91.147.128.0/19 with origin AS43775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43775 in the RIR database for the space.	165 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

91.147.144.0/20

ROA 91.147.128.0/19 AS43775 has maxLength 19; the route is a /20. Raise the maxLength, or add a ROA for 91.147.144.0/20.

165 of 673

Route object: none

91.147.144.0/20

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

165 of 673

Route objects not announced

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


91.147.128.0/18	RADB	No ROA
91.147.128.0/19	RIPE	Valid
91.147.150.0/24	RIPE	Invalid: maxLength
91.147.151.0/24	RIPE	Invalid: maxLength
91.147.160.0/19	RADB	No ROA
91.147.163.0/24	RADB, RIPE	Valid
91.147.164.0/24	RADB, RIPE	Valid
91.147.165.0/24	RIPE	Invalid: maxLength
91.147.166.0/24	RIPE	Invalid: maxLength
91.147.167.0/24	RIPE	Invalid: maxLength
91.147.168.0/24	RIPE	Invalid: maxLength
91.147.169.0/24	RIPE	Invalid: maxLength
91.147.170.0/24	RIPE	Valid
91.147.172.0/24	RIPE	Invalid: maxLength
91.147.174.0/24	RIPE	Invalid: maxLength
91.147.176.0/24	RADB, RIPE	No ROA
91.147.177.0/24	RADB, RIPE	No ROA
91.147.178.0/24	RIPE	No ROA
91.147.179.0/24	RIPE	No ROA
91.147.180.0/22	RADB	No ROA
91.147.182.0/24	RADB, RIPE	No ROA
91.147.184.0/22	RADB	No ROA
91.147.186.0/24	RADB, RIPE	Valid

91.147.128.0/18

RADB

No ROA

91.147.128.0/19

RIPE

Valid

91.147.150.0/24

RIPE

Invalid: maxLength

91.147.151.0/24

RIPE

Invalid: maxLength

91.147.160.0/19

RADB

No ROA

91.147.163.0/24

RADB, RIPE

Valid

91.147.164.0/24

RADB, RIPE

Valid

91.147.165.0/24

RIPE

Invalid: maxLength

91.147.166.0/24

RIPE

Invalid: maxLength

91.147.167.0/24

RIPE

Invalid: maxLength

91.147.168.0/24

RIPE

Invalid: maxLength

91.147.169.0/24

RIPE

Invalid: maxLength

91.147.170.0/24

RIPE

Valid

91.147.172.0/24

RIPE

Invalid: maxLength

91.147.174.0/24

RIPE

Invalid: maxLength

91.147.176.0/24

RADB, RIPE

No ROA

91.147.177.0/24

RADB, RIPE

No ROA

91.147.178.0/24

RIPE

No ROA

91.147.179.0/24

RIPE

No ROA

91.147.180.0/22

RADB

No ROA

91.147.182.0/24

RADB, RIPE

No ROA

91.147.184.0/22

RADB

No ROA

91.147.186.0/24

RADB, RIPE

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.