bgpreport

Network · data from 2026-11-12

AS201136 AGLZ Agiliza Solutions SL

Registry name: AGLZ Agiliza Solutions SL, ES · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 92.3% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 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 AS201136, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201136, 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.
92.112.220.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a06:9801:53::/48 No ROA RIR databaseRIPE 634 100% 67
185.210.152.0/24 Valid Other IRR onlyRADB 673 100% 67
194.143.207.0/24 Valid Other IRR onlyRADB 673 100% 67
194.143.210.0/24 Valid Other IRR onlyRADB 673 100% 67
194.143.222.0/24 Valid Other IRR onlyRADB 673 100% 67
194.143.223.0/24 Valid Other IRR onlyRADB 673 100% 67
46.202.102.0/24 Valid Other IRR onlyRADB 672 100% 67
46.202.103.0/24 Valid Other IRR onlyRADB 672 100% 67
80.174.113.0/24 Valid Other IRR onlyRADB 672 100% 67
80.174.121.0/24 Valid Other IRR onlyRADB 672 100% 67
80.174.122.0/24 Valid Other IRR onlyRADB 672 100% 67
185.225.168.0/24 Valid Other IRR onlyRADB 672 100% 67
185.225.169.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS201136 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
ROA: origin92.112.220.0/24ROAs covering it name AS834, not AS201136. If AS201136 should announce it, add a ROA for AS201136.2 of 673
Route object: none92.112.220.0/24Route objects for it name AS834. Add a route object with origin AS201136 in the RIR database for the space.2 of 673
ROA: none2a06:9801:53::/48No ROA covers it. Add a ROA for AS201136, maxLength 48.634 of 636
Route object: RIR185.210.152.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR194.143.207.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR194.143.210.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR194.143.222.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR194.143.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR46.202.102.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR46.202.103.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR80.174.113.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR80.174.121.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR80.174.122.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.225.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.225.169.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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