Network · data from 2026-11-12

AS205624 Telecomunicaciones Publicas Andaluzas S.L., AIRENETWORK

Registry name: telecoandaluzas Telecomunicaciones Publicas Andaluzas S.L., ES · PeeringDB

36IPv4 routes 100.0% RPKI valid · 97.2% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

30Route objects not announced registered with origin AS205624, seen from no peer

Announced routes

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


185.234.156.0/22	Valid	Other origin only	673 100%	67
94.176.176.0/23	Valid	RIR databaseRIPE	673 100%	67
94.176.176.0/24	Valid	RIR databaseRIPE	673 100%	67
94.176.177.0/24	Valid	RIR databaseRIPE	673 100%	67
94.176.178.0/24	Valid	RIR databaseRIPE	673 100%	67
94.176.179.0/24	Valid	RIR databaseRIPE	673 100%	67
152.89.32.0/23	Valid	RIR databaseRIPE	673 100%	67
171.33.235.0/24	Valid	RIR databaseRIPE	673 100%	67
185.44.16.0/24	Valid	RIR databaseRIPE	673 100%	67
185.44.17.0/24	Valid	RIR databaseRIPE	673 100%	67
185.44.18.0/24	Valid	RIR databaseRIPE	673 100%	67
185.44.19.0/24	Valid	RIR databaseRIPE	673 100%	67
185.154.204.0/22	Valid	RIR databaseRIPE	673 100%	67
185.156.100.0/24	Valid	RIR databaseRIPE	673 100%	67
185.156.101.0/24	Valid	RIR databaseRIPE	673 100%	67
185.156.102.0/24	Valid	RIR databaseRIPE	673 100%	67
185.156.103.0/24	Valid	RIR databaseRIPE	673 100%	67
185.196.64.0/24	Valid	RIR databaseRIPE	673 100%	67
185.196.65.0/24	Valid	RIR databaseRIPE	673 100%	67
185.196.66.0/24	Valid	RIR databaseRIPE	673 100%	67
185.196.67.0/24	Valid	RIR databaseRIPE	673 100%	67
185.211.68.0/22	Valid	RIR databaseRIPE	673 100%	67
185.211.68.0/24	Valid	RIR databaseRIPE	673 100%	67
185.211.69.0/24	Valid	RIR databaseRIPE	673 100%	67
185.211.70.0/24	Valid	RIR databaseRIPE	673 100%	67
185.211.71.0/24	Valid	RIR databaseRIPE	673 100%	67
185.252.224.0/22	Valid	RIR databaseRIPE	673 100%	67
185.252.224.0/24	Valid	RIR databaseRIPE	673 100%	67
185.252.225.0/24	Valid	RIR databaseRIPE	673 100%	67
185.252.226.0/24	Valid	RIR databaseRIPE	673 100%	67
185.252.227.0/24	Valid	RIR databaseRIPE	673 100%	67
193.46.192.0/22	Valid	RIR databaseRIPE	673 100%	67
37.156.188.0/22	Valid	RIR databaseRIPE	672 100%	67
185.156.100.0/22	Valid	RIR databaseRIPE	672 100%	67
2a0d:8800::/29	Valid	RIR databaseRIPE	634 100%	67
37.156.188.0/23	Valid	RIR databaseRIPE	316 47%	62
94.176.176.0/22	Valid	RIR databaseRIPE	316 47%	62

AS-SET

AS205624'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 31 are in fix.csv.

Route object: none1
Route object: not announced30

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.234.156.0/22	Route objects for it name AS205575. Add a route object with origin AS205624 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.234.156.0/22

Route objects for it name AS205575. Add a route object with origin AS205624 in the RIR database for the space.

673 of 673

Route objects not announced

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


37.156.190.0/23	RIPE	Valid
89.39.154.0/24	RIPE	Valid
91.151.101.0/24	RIPE	Valid
94.176.178.0/23	RIPE	Valid
152.89.32.0/24	RIPE	Valid
152.89.33.0/24	RIPE	Valid
185.44.16.0/22	RIPE	Valid
185.44.16.0/23	RIPE	Valid
185.44.18.0/23	RIPE	Valid
185.154.204.0/23	RIPE	Valid
185.154.206.0/23	RIPE	Valid
185.156.100.0/23	RIPE	Valid
185.156.102.0/23	RIPE	Valid
185.196.64.0/22	RIPE	Valid
185.196.64.0/23	RIPE	Valid
185.196.66.0/23	RIPE	Valid
185.211.68.0/23	RIPE	Valid
185.211.70.0/23	RIPE	Valid
185.252.224.0/23	RIPE	Valid
185.252.226.0/23	RIPE	Valid
193.46.192.0/23	RIPE	Valid
193.46.192.0/24	RIPE	Valid
193.46.193.0/24	RIPE	Valid
193.46.194.0/23	RIPE	Valid
193.46.194.0/24	RIPE	Valid
193.46.195.0/24	RIPE	Valid
212.225.227.0/24	RIPE	Valid
212.225.244.0/24	RIPE	Valid
2a01:72e0::/32	RIPE	No ROA
2a0d:4f40::/32	RIPE	No ROA

37.156.190.0/23

RIPE

Valid

89.39.154.0/24

RIPE

Valid

91.151.101.0/24

RIPE

Valid

94.176.178.0/23

RIPE

Valid

152.89.32.0/24

RIPE

Valid

152.89.33.0/24

RIPE

Valid

185.44.16.0/22

RIPE

Valid

185.44.16.0/23

RIPE

Valid

185.44.18.0/23

RIPE

Valid

185.154.204.0/23

RIPE

Valid

185.154.206.0/23

RIPE

Valid

185.156.100.0/23

RIPE

Valid

185.156.102.0/23

RIPE

Valid

185.196.64.0/22

RIPE

Valid

185.196.64.0/23

RIPE

Valid

185.196.66.0/23

RIPE

Valid

185.211.68.0/23

RIPE

Valid

185.211.70.0/23

RIPE

Valid

185.252.224.0/23

RIPE

Valid

185.252.226.0/23

RIPE

Valid

193.46.192.0/23

RIPE

Valid

193.46.192.0/24

RIPE

Valid

193.46.193.0/24

RIPE

Valid

193.46.194.0/23

RIPE

Valid

193.46.194.0/24

RIPE

Valid

193.46.195.0/24

RIPE

Valid

212.225.227.0/24

RIPE

Valid

212.225.244.0/24

RIPE

Valid

2a01:72e0::/32

RIPE

No ROA

2a0d:4f40::/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.