Network · data from 2026-11-12

AS205334 Fiberplus2AS FIBERPLUS COMUNICATIONS, SL

Registry name: Fiberplus2AS FIBERPLUS COMUNICATIONS, SL, ES · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

6Route objects not announced registered with origin AS205334, seen from no peer

Announced routes

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


146.19.117.0/24	Valid	RIR databaseRIPE	673 100%	67
176.119.133.0/24	Valid	RIR databaseRIPE	673 100%	67
176.119.135.0/24	Valid	RIR databaseRIPE	673 100%	67
185.193.172.0/24	Valid	RIR databaseRIPE	673 100%	67
185.193.173.0/24	Valid	RIR databaseRIPE	673 100%	67
185.193.174.0/24	Valid	RIR databaseRIPE	673 100%	67
185.193.175.0/24	Valid	RIR databaseRIPE	673 100%	67
185.211.41.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.168.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.169.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.170.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.171.0/24	Valid	RIR databaseRIPE	673 100%	67
176.119.132.0/24	Valid	RIR databaseRIPE	670 100%	67

AS-SET

AS205334 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 6 are in fix.csv.

Route object: not announced6

Route objects not announced

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


176.119.132.0/22	RIPE	Valid
176.119.132.0/23	RIPE	Valid
176.119.134.0/23	RIPE	Valid
176.119.134.0/24	RIPE	Valid
185.193.172.0/22	RIPE	No ROA
2a0a:3b40::/29	RIPE	No ROA

176.119.132.0/22

RIPE

Valid

176.119.132.0/23

RIPE

Valid

176.119.134.0/23

RIPE

Valid

176.119.134.0/24

RIPE

Valid

185.193.172.0/22

RIPE

No ROA

2a0a:3b40::/29

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.