bgpreport

Network · data from 2026-11-12

AS40995 SIBSET-NKZ-AS Sibirskie Seti Ltd.

Registry name: SIBSET-NKZ-AS Sibirskie Seti Ltd., RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40995, 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.
80.64.160.0/21 No ROA RIR databaseRIPE 673 100% 66
89.189.160.0/21 No ROA RIR databaseRIPE 673 100% 66
89.189.168.0/21 No ROA RIR databaseRIPE 673 100% 66
5.44.172.0/23 Valid RIR databaseRIPE 673 100% 66
5.44.172.0/24 Valid RIR databaseRIPE 673 100% 66
5.44.173.0/24 Valid RIR databaseRIPE 673 100% 66
109.111.160.0/20 Valid RIR databaseRIPE 673 100% 66
109.111.160.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS40995 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 10 are in fix.csv.

  • ROA: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none80.64.160.0/21No ROA covers it. Add a ROA for AS40995, maxLength 21.673 of 673
ROA: none89.189.160.0/21No ROA covers it. Add a ROA for AS40995, maxLength 21.673 of 673
ROA: none89.189.168.0/21No ROA covers it. Add a ROA for AS40995, maxLength 21.673 of 673

Route objects not announced

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

80.64.160.0/22RIPENo ROA
80.64.164.0/22RIPENo ROA
89.189.160.0/20RIPENo ROA
89.189.169.0/24RIPENo ROA
89.189.170.0/24RIPENo ROA
109.111.160.0/21RIPEValid
109.111.168.0/21RIPEValid

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.