bgpreport

Network · data from 2026-11-12

AS43568 VEV Romerike

Registry name: VEV-alo1 VEV Romerike AS, NO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43568, 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.
185.78.68.0/22 No ROA RIR databaseRIPE 672 100% 67
77.247.144.0/20 Valid RIR databaseRIPE 672 100% 67
178.250.216.0/21 Valid RIR databaseRIPE 672 100% 67
128.0.16.0/21 Valid RIR databaseRIPE 671 100% 67
2a02:2470::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS43568's PeeringDB record names no 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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.78.68.0/22No ROA covers it. Add a ROA for AS43568, maxLength 22.672 of 673

Route objects not announced

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

77.247.144.0/21RIPEValid
77.247.152.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.