bgpreport

Network · data from 2026-11-12

AS15675 Etat-de-Vaud Direction generale du numerique et des systemes d'information (DGNSI) Etat de Vaud

Registry name: Etat-de-Vaud Direction generale du numerique et des systemes d'information (DGNSI) Etat de Vaud, CH · not in PeeringDB

31IPv4 routes 90.3% 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
20Route objects not announced registered with origin AS15675, seen from no peer

Announced routes

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

193.135.104.0/23 No ROA RIR databaseRIPE 670 100% 67
193.135.138.0/24 No ROA RIR databaseRIPE 670 100% 67
194.56.250.0/23 No ROA RIR databaseRIPE 670 100% 67
145.232.0.0/16 Valid RIR databaseRIPE 671 100% 67
145.232.192.0/23 Valid RIR databaseRIPE 671 100% 66
145.232.194.0/23 Valid RIR databaseRIPE 671 100% 66
145.232.254.0/23 Valid RIR databaseRIPE 671 100% 66
145.232.0.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.32.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.32.0/24 Valid RIR databaseRIPE 670 100% 67
145.232.64.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.96.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.107.0/24 Valid RIR databaseRIPE 670 100% 67
145.232.128.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.128.0/24 Valid RIR databaseRIPE 670 100% 67
145.232.160.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.192.0/19 Valid RIR databaseRIPE 670 100% 67
145.232.199.0/24 Valid RIR databaseRIPE 670 100% 67
145.232.224.0/19 Valid RIR databaseRIPE 670 100% 67
193.5.240.0/21 Valid RIR databaseRIPE 670 100% 67
193.5.240.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.241.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.242.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.243.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.244.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.245.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.246.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.247.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.248.0/23 Valid RIR databaseRIPE 670 100% 67
193.5.248.0/24 Valid RIR databaseRIPE 670 100% 67
193.5.249.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS15675 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 23 are in fix.csv.

  • ROA: none3
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none193.135.104.0/23No ROA covers it. Add a ROA for AS15675, maxLength 23.670 of 673
ROA: none193.135.138.0/24No ROA covers it. Add a ROA for AS15675, maxLength 24.670 of 673
ROA: none194.56.250.0/23No ROA covers it. Add a ROA for AS15675, maxLength 23.670 of 673

Route objects not announced

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

145.232.33.0/24RIPEInvalid: maxLength
145.232.108.0/24RIPEInvalid: maxLength
145.232.110.0/24RIPEInvalid: maxLength
145.232.112.0/20RIPEInvalid: maxLength
145.232.129.0/24RIPEInvalid: maxLength
145.232.134.0/23RIPEInvalid: maxLength
145.232.196.0/24RIPEInvalid: maxLength
145.232.200.0/24RIPEInvalid: maxLength
145.232.229.0/24RIPEInvalid: maxLength
145.232.230.0/24RIPEInvalid: maxLength
145.232.233.0/24RIPEInvalid: maxLength
145.232.234.0/24RIPEInvalid: maxLength
145.232.235.0/24RIPEInvalid: maxLength
145.232.236.0/24RIPEInvalid: maxLength
145.232.246.0/24RIPEInvalid: maxLength
145.232.250.0/24RIPEInvalid: maxLength
145.232.252.0/24RIPEInvalid: maxLength
145.232.253.0/24RIPEInvalid: maxLength
145.232.254.0/24RIPEInvalid: maxLength
145.232.255.0/24RIPEInvalid: maxLength

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.