bgpreport

Network · data from 2026-11-12

AS51790 SIEL

Registry name: SIEL SIEL, d.o.o., SI · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51790, 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.

91.230.238.0/24 No ROA RIR databaseRIPE 671 100% 68
195.128.141.0/24 No ROA RIR databaseRIPE 671 100% 68
185.185.88.0/23 Valid None 671 100% 68
185.185.91.0/24 Valid RIR databaseRIPE 672 100% 67
217.61.252.0/24 Valid RIR databaseRIPE 672 100% 67
45.136.188.0/23 Valid RIR databaseRIPE 671 100% 68
45.136.190.0/23 Valid RIR databaseRIPE 671 100% 68
46.19.8.0/23 Valid RIR databaseRIPE 671 100% 68
46.19.10.0/23 Valid RIR databaseRIPE 671 100% 68
46.19.12.0/23 Valid RIR databaseRIPE 671 100% 68
46.19.14.0/23 Valid RIR databaseRIPE 671 100% 68
185.57.144.0/23 Valid RIR databaseRIPE 671 100% 68
185.57.146.0/24 Valid RIR databaseRIPE 671 100% 68
185.92.228.0/24 Valid RIR databaseRIPE 671 100% 68
185.97.52.0/23 Valid RIR databaseRIPE 671 100% 68
185.97.54.0/23 Valid RIR databaseRIPE 671 100% 68
193.3.59.0/24 Valid RIR databaseRIPE 671 100% 68
198.60.216.0/24 Valid RIR databaseRIPE 671 100% 68
209.16.152.0/23 Valid RIR databaseRIPE 671 100% 68
209.16.154.0/23 Valid RIR databaseRIPE 671 100% 68
185.57.145.0/24 Valid RIR databaseRIPE 667 99% 67
46.19.13.0/24 Valid RIR databaseRIPE 666 99% 67
2a02:28b2::/32 Valid RIR databaseRIPE 635 100% 69
2a02:28b0::/32 Valid RIR databaseRIPE 634 100% 69
2a02:28b1::/32 Valid RIR databaseRIPE 634 100% 69
2a02:28b7::/32 Valid RIR databaseRIPE 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS51790: AS-SIEL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS51790 isn't in the set, or no route object for AS51790 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS51790 in itNot covered
AS-SIEL RIPE 9255 Yes 1

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: none2
  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none91.230.238.0/24No ROA covers it. Add a ROA for AS51790, maxLength 24.671 of 673
ROA: none195.128.141.0/24No ROA covers it. Add a ROA for AS51790, maxLength 24.671 of 673
Route object: none185.185.88.0/23No route object for it. Add a route object with origin AS51790 in the RIR database for the space.671 of 673

Route objects not announced

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

46.19.8.0/21RIPENo ROA
46.19.8.0/24RIPEValid
46.19.9.0/24RIPEValid
46.19.10.0/24RIPEValid
46.19.11.0/24RIPEValid
46.19.12.0/24RIPEValid
46.19.14.0/24RIPEValid
185.57.144.0/24RIPEInvalid: maxLength
185.57.147.0/24RIPENo ROA
185.97.55.0/24RIPEValid
185.185.90.0/23RIPEValid
2001:470:435::/48ARINValid

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.