bgpreport

Network · data from 2026-11-12

AS216129 GuardNetwork-AS SEBEK sp. z o.o

Registry name: GuardNetwork-AS SEBEK sp. z o.o, PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216129, 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.
31.56.180.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
31.57.13.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
107.161.154.0/24 Valid RIR databaseRIPE 673 100% 66
148.253.213.0/24 Valid RIR databaseRIPE 673 100% 67
148.253.214.0/24 Valid RIR databaseRIPE 673 100% 66
148.253.215.0/24 Valid RIR databaseRIPE 673 100% 67
177.177.237.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
188.220.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
199.83.103.0/24 Valid RIR databaseRIPE 673 100% 66
202.181.188.0/24 Valid RIR databaseRIPE 673 100% 66
2.27.253.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.58.85.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.58.155.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.77.241.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
143.20.155.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
148.253.208.0/24 Valid RIR databaseRIPE 672 100% 67
148.253.209.0/24 Valid RIR databaseRIPE 672 100% 67
148.253.210.0/24 Valid RIR databaseRIPE 672 100% 67
148.253.211.0/24 Valid RIR databaseRIPE 672 100% 67
185.28.84.0/24 Valid RIR databaseRIPE 672 100% 67
188.220.148.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
104.234.24.0/24 Valid RIR databaseARIN, RADB 671 100% 68
148.253.212.0/24 Valid RIR databaseRIPE 671 100% 68
177.177.230.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2a13:d201:6::/48 Valid RIR databaseRIPE 636 100% 69
2a13:d201::/48 Valid RIR databaseRIPE 634 100% 69
2a13:d201:7::/48 Valid RIR databaseRIPE 634 100% 67
2a13:d200::/32 Valid RIR databaseRIPE 633 100% 67
2a13:d200:13::/48 Valid RIR databaseRIPE 633 100% 67
2a13:d200:15::/48 Valid RIR databaseRIPE 633 100% 67
2a13:d201:1::/48 Valid RIR databaseRIPE 632 99% 67
2a13:d201:3::/48 Valid RIR databaseRIPE 632 99% 67
31.57.117.0/24 Valid RIR databaseRADB, RIPE 252 37% 61
2a13:d201:2::/48 Valid RIR databaseRIPE 2 0%low visibility 4

AS-SET

AS216129 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 8 are in fix.csv.

  • Route object: not announced8

Route objects not announced

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

81.30.105.0/24RIPEValid
95.215.56.0/24RIPEValid
121.127.37.0/24RIPEValid
185.28.85.0/24RIPEValid
185.56.162.0/24RIPEValid
194.164.245.0/24RIPEValid
202.181.148.0/24RIPEValid
203.31.40.0/24RIPEValid

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.