Network · data from 2026-11-12

AS202125 ACACIONET ACACIO SERVICIOS TELEMATICOS S.L.

Registry name: ACACIONET ACACIO SERVICIOS TELEMATICOS S.L., ES · not in PeeringDB

11IPv4 routes 81.8% RPKI valid · 100.0% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

14Route objects not announced registered with origin AS202125, seen from no peer

Announced routes

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


193.43.75.0/24	Invalid: origin	RIR databaseRIPE	89 13%	40
45.13.8.0/24	No ROA	RIR databaseRIPE	671 100%	67
185.50.204.0/23	Valid	RIR databaseRIPE	673 100%	67
185.247.164.0/22	Valid	RIR databaseRIPE	673 100%	67
185.247.164.0/24	Valid	RIR databaseRIPE	673 100%	67
185.247.165.0/24	Valid	RIR databaseRIPE	673 100%	67
185.247.166.0/24	Valid	RIR databaseRIPE	673 100%	67
188.119.105.0/24	Valid	RIR databaseRIPE	672 100%	67
188.119.106.0/24	Valid	RIR databaseRIPE	672 100%	67
188.119.107.0/24	Valid	RIR databaseRIPE	672 100%	67
185.247.167.0/24	Valid	RIR databaseRIPE	670 100%	67

AS-SET

AS202125 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 16 are in fix.csv.

ROA: origin1
ROA: none1
Route object: not announced14

Change	Prefix or set	Detail	Full-table peers
ROA: origin	193.43.75.0/24	ROAs covering it name AS29119, not AS202125. If AS202125 should announce it, add a ROA for AS202125.	89 of 673
ROA: none	45.13.8.0/24	No ROA covers it. Add a ROA for AS202125, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

193.43.75.0/24

ROAs covering it name AS29119, not AS202125. If AS202125 should announce it, add a ROA for AS202125.

89 of 673

ROA: none

45.13.8.0/24

No ROA covers it. Add a ROA for AS202125, maxLength 24.

671 of 673

Route objects not announced

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


45.13.8.0/23	RIPE	No ROA
45.13.9.0/24	RIPE	Valid
45.13.10.0/23	RIPE	No ROA
45.13.10.0/24	RIPE	Valid
185.50.206.0/23	RIPE	No ROA
185.50.207.0/24	RIPE	Valid
185.247.164.0/23	RIPE	Valid
185.247.166.0/23	RIPE	Valid
188.119.104.0/22	RIPE	Valid
188.119.104.0/23	RIPE	Valid
188.119.104.0/24	RIPE	Valid
188.119.106.0/23	RIPE	Valid
193.43.74.0/24	RIPE	Valid
2a01:ad20::/32	RIPE	No ROA

45.13.8.0/23

RIPE

No ROA

45.13.9.0/24

RIPE

Valid

45.13.10.0/23

RIPE

No ROA

45.13.10.0/24

RIPE

Valid

185.50.206.0/23

RIPE

No ROA

185.50.207.0/24

RIPE

Valid

185.247.164.0/23

RIPE

Valid

185.247.166.0/23

RIPE

Valid

188.119.104.0/22

RIPE

Valid

188.119.104.0/23

RIPE

Valid

188.119.104.0/24

RIPE

Valid

188.119.106.0/23

RIPE

Valid

193.43.74.0/24

RIPE

Valid

2a01:ad20::/32

RIPE

No 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.