bgpreport

Network · data from 2026-11-12

AS204741 ES-AIRSAT AIRSAT COMUNICACIONES S.L.

Registry name: ES-AIRSAT AIRSAT COMUNICACIONES S.L., ES · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS204741, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204741, 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.
5.59.212.0/22 No ROA RIR databaseRIPE 673 100% 67
85.209.72.0/22 Valid RIR databaseRIPE 673 100% 67
85.209.72.0/24 Valid RIR databaseRIPE 673 100% 67
85.209.73.0/24 Valid RIR databaseRIPE 673 100% 67
94.24.40.0/22 Valid RIR databaseRIPE 673 100% 67
185.242.24.0/22 Valid RIR databaseRIPE 673 100% 67
185.242.24.0/24 Valid RIR databaseRIPE 673 100% 67
185.242.26.0/24 Valid RIR databaseRIPE 673 100% 67
185.242.27.0/24 Valid RIR databaseRIPE 673 100% 67
217.76.254.0/24 Valid RIR databaseRIPE 673 100% 67
185.242.25.0/24 Valid RIR databaseRIPE 672 100% 67
45.194.65.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
45.195.80.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
2a0c:ba80::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none5.59.212.0/22No ROA covers it. Add a ROA for AS204741, maxLength 22.673 of 673

Route objects not announced

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

85.209.74.0/24RIPEValid
85.209.75.0/24RIPEValid
185.242.24.0/23RIPEValid
185.242.26.0/23RIPEValid
2a0c:ba80::/48RIPEValid

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.