bgpreport

Network · data from 2026-11-12

AS211974 airecom Airecom Internet, S.L.

Registry name: airecom Airecom Internet, S.L., ES · not in PeeringDB

4IPv4 routes 75.0% RPKI valid · 75.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 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS211974, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211974, 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.
149.34.45.0/24 No ROA None 155 23% 47
185.203.220.0/22 Valid RIR databaseRIPE 672 100% 67
195.5.76.0/23 Valid RIR databaseRIPE 672 100% 67
2a12:9740::/29 Valid RIR databaseRIPE 634 100% 69
212.163.26.0/24 Valid RIR databaseRIPE 6 1%low visibility 5

AS-SET

AS211974 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none149.34.45.0/24No ROA covers it. Add a ROA for AS211974, maxLength 24.155 of 673
Route object: none149.34.45.0/24No route object for it. Add a route object with origin AS211974 in the RIR database for the space.155 of 673

Route objects not announced

Every route object with origin AS211974 is announced.

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.