bgpreport

Network · data from 2026-11-12

AS199374 SDE-AS

Registry name: SDE-AS Syddansk Erhvervsskole Odense-Vejle, DK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199374, 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.19.132.0/22 No ROA Other origin only 673 100% 67
2a00:4460::/32 No ROA None 338 53% 59

AS-SET

AS199374'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 4 are in fix.csv.

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none185.19.132.0/22No ROA covers it. Add a ROA for AS199374, maxLength 22.673 of 673
Route object: none185.19.132.0/22Route objects for it name AS31027. Add a route object with origin AS199374 in the RIR database for the space.673 of 673
ROA: none2a00:4460::/32No ROA covers it. Add a ROA for AS199374, maxLength 32.338 of 636
Route object: none2a00:4460::/32No route object for it. Add a route object with origin AS199374 in the RIR database for the space.338 of 636

Route objects not announced

Every route object with origin AS199374 is announced.

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.