bgpreport

Network · data from 2026-11-12

AS206195 beconet-as BECONET FIBRA S.L.

Registry name: beconet-as BECONET FIBRA S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206195, 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.
154.62.249.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.193.200.0/24 Valid Nonecovered by 185.193.200.0/22 672 100% 67
185.193.201.0/24 Valid Nonecovered by 185.193.200.0/22 672 100% 67
185.193.202.0/24 Valid Nonecovered by 185.193.200.0/22 672 100% 67
185.193.203.0/24 Valid Nonecovered by 185.193.200.0/22 672 100% 67
45.15.116.0/22 Valid RIR databaseRIPE 672 100% 67
185.193.200.0/22 Valid RIR databaseRIPE 672 100% 67
45.15.116.0/24 Valid RIR databaseRIPE 671 100% 67
45.15.117.0/24 Valid RIR databaseRIPE 671 100% 67
45.15.118.0/24 Valid RIR databaseRIPE 671 100% 67
45.15.119.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS206195 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: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none154.62.249.0/24No ROA covers it. Add a ROA for AS206195, maxLength 24.672 of 673
Route object: RIR154.62.249.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none185.193.200.0/24No route object for it. A route object for 185.193.200.0/22 with origin AS206195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206195 in the RIR database for the space.672 of 673
Route object: none185.193.201.0/24No route object for it. A route object for 185.193.200.0/22 with origin AS206195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206195 in the RIR database for the space.672 of 673
Route object: none185.193.202.0/24No route object for it. A route object for 185.193.200.0/22 with origin AS206195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206195 in the RIR database for the space.672 of 673
Route object: none185.193.203.0/24No route object for it. A route object for 185.193.200.0/22 with origin AS206195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206195 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS206195 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.