bgpreport

Network · data from 2026-11-12

AS203499 Wi-Net-SOLIS-AS Free Technologies Excom S.L.

Registry name: Wi-Net-SOLIS-AS Free Technologies Excom S.L., ES · not in PeeringDB

1IPv4 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
22Route objects not announced registered with origin AS203499, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203499, 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.
2.59.108.0/24 Valid RIR databaseRIPE 666 99% 67

AS-SET

AS203499 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 22 are in fix.csv.

  • Route object: not announced22

Route objects not announced

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

2.59.108.0/22RIPEValid
2.59.109.0/24RIPEValid
2.59.110.0/24RIPEValid
37.26.250.0/24RIPENo ROA
45.92.132.0/23RIPEValid
154.48.130.0/23RIPE-NONAUTHNo ROA
154.48.130.0/24RADBNo ROA
154.48.131.0/24RADBNo ROA
154.48.132.0/22RIPE-NONAUTHNo ROA
154.48.144.0/23RIPE-NONAUTHNo ROA
154.48.144.0/24RADBNo ROA
154.48.145.0/24RADBNo ROA
154.48.168.0/22RADBNo ROA
154.48.172.0/22RIPE-NONAUTHNo ROA
154.48.180.0/22RIPE-NONAUTHNo ROA
154.48.184.0/24RADBNo ROA
154.48.188.0/22RADBNo ROA
154.48.188.0/24RADBNo ROA
154.48.189.0/24RADBNo ROA
154.48.190.0/24RADBNo ROA
154.48.191.0/24RADBNo ROA
154.61.96.0/22RIPE-NONAUTHNo 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.