bgpreport

Network · data from 2026-11-12

AS39078 GDM Konsult

Registry name: GDM GDM Konsult AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39078, 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.
91.192.112.0/24 No ROA RIR databaseRIPE 673 100% 66
91.192.114.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:67c:904::/48 No ROA RIR databaseRIPE 636 100% 67
2a12:3600::/30 Valid None 632 99% 67
81.25.80.0/21 Valid RIR databaseRIPE 673 100% 66
212.23.220.0/24 Valid RIR databaseRIPE 673 100% 66
217.68.32.0/20 Valid RIR databaseRIPE 673 100% 66
2a06:3640::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS39078'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: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none91.192.112.0/24No ROA covers it. Add a ROA for AS39078, maxLength 24.673 of 673
ROA: none91.192.114.0/24No ROA covers it. Add a ROA for AS39078, maxLength 24.673 of 673
ROA: none2001:67c:904::/48No ROA covers it. Add a ROA for AS39078, maxLength 48.636 of 636
Route object: none2a12:3600::/30No route object for it. Add a route object with origin AS39078 in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS39078 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.