bgpreport

Network · data from 2026-11-12

AS204556 SysAdminOK SysAdminOK SL

Registry name: SysAdminOK SysAdminOK SL, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204556, 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.
2a0d:7b80::/64 No ROA Nonecovered by 2a0d:7b80::/29 4 1%low visibility 6
2a0d:7b80:0:2::/64 No ROA Nonecovered by 2a0d:7b80::/29 4 1%low visibility 6
2a0d:7b80:0:3::/64 No ROA Nonecovered by 2a0d:7b80::/29 4 1%low visibility 6
185.246.52.0/24 No ROA RIR databaseRIPE 672 100% 67
185.246.53.0/24 No ROA RIR databaseRIPE 672 100% 67
185.246.54.0/24 No ROA RIR databaseRIPE 672 100% 67
185.246.55.0/24 No ROA RIR databaseRIPE 672 100% 67
2a0d:7b80::/29 No ROA RIR databaseRIPE 633 100% 67

AS-SET

AS204556 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 12 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:7b80::/64No ROA covers it. Add a ROA for AS204556, maxLength 64.4 of 636
Route object: none2a0d:7b80::/64No route object for it. A route object for 2a0d:7b80::/29 with origin AS204556 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS204556 in the RIR database for the space.4 of 636
ROA: none2a0d:7b80:0:2::/64No ROA covers it. Add a ROA for AS204556, maxLength 64.4 of 636
Route object: none2a0d:7b80:0:2::/64No route object for it. A route object for 2a0d:7b80::/29 with origin AS204556 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS204556 in the RIR database for the space.4 of 636
ROA: none2a0d:7b80:0:3::/64No ROA covers it. Add a ROA for AS204556, maxLength 64.4 of 636
Route object: none2a0d:7b80:0:3::/64No route object for it. A route object for 2a0d:7b80::/29 with origin AS204556 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS204556 in the RIR database for the space.4 of 636
ROA: none185.246.52.0/24No ROA covers it. Add a ROA for AS204556, maxLength 24.672 of 673
ROA: none185.246.53.0/24No ROA covers it. Add a ROA for AS204556, maxLength 24.672 of 673
ROA: none185.246.54.0/24No ROA covers it. Add a ROA for AS204556, maxLength 24.672 of 673
ROA: none185.246.55.0/24No ROA covers it. Add a ROA for AS204556, maxLength 24.672 of 673
ROA: none2a0d:7b80::/29No ROA covers it. Add a ROA for AS204556, maxLength 29.633 of 636

Route objects not announced

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

185.246.52.0/22RIPENo 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.