bgpreport

Network · data from 2026-11-12

AS44946 Dembach Goo Informatik GmbH & Co KG

Registry name: DGINET-AS Dembach Goo Informatik GmbH & Co. KG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44946, 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.
195.149.82.0/24 No ROA RIR databaseRIPE 673 100% 67
2001:678:4f4::/48 No ROA RIR databaseRIPE 634 100% 67
194.187.64.0/23 Valid Nonecovered by 194.187.64.0/22 673 100% 67
194.187.66.0/24 Valid Nonecovered by 194.187.64.0/22 673 100% 67
194.187.67.0/24 Valid Nonecovered by 194.187.64.0/22 673 100% 67
93.94.128.0/21 Valid RIR databaseRIPE 673 100% 67
93.94.129.0/24 Valid RIR databaseRIPE 673 100% 67
93.94.134.0/24 Valid RIR databaseRIPE 673 100% 67
185.59.200.0/23 Valid RIR databaseRIPE 673 100% 67
185.59.200.0/24 Valid RIR databaseRIPE 673 100% 67
185.59.202.0/23 Valid RIR databaseRIPE 673 100% 67
185.59.202.0/24 Valid RIR databaseRIPE 673 100% 67
195.49.152.0/22 Valid RIR databaseRIPE 673 100% 67
91.242.212.0/24 Valid RIR databaseRIPE 672 100% 67
185.59.201.0/24 Valid RIR databaseRIPE 672 100% 67
2a02:158::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:200::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:400::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:600::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:aa00::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:c000::/39 Valid RIR databaseRIPE 634 100% 67
2a02:158:fffe::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS44946'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 18 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none195.149.82.0/24No ROA covers it. Add a ROA for AS44946, maxLength 24.673 of 673
ROA: none2001:678:4f4::/48No ROA covers it. Add a ROA for AS44946, maxLength 48.634 of 636
Route object: none194.187.64.0/23No route object for it. A route object for 194.187.64.0/22 with origin AS44946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44946 in the RIR database for the space.673 of 673
Route object: none194.187.66.0/24No route object for it. A route object for 194.187.64.0/22 with origin AS44946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44946 in the RIR database for the space.673 of 673
Route object: none194.187.67.0/24No route object for it. A route object for 194.187.64.0/22 with origin AS44946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44946 in the RIR database for the space.673 of 673

Route objects not announced

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

93.94.135.0/24RIPEValid
185.59.203.0/24RIPEValid
194.187.64.0/22RIPEValid
194.187.64.0/24RIPEValid
2001:678:4dc::/48RIPENo ROA
2001:678:4e0::/48RIPENo ROA
2001:678:4e8::/48RIPENo ROA
2001:678:4ec::/48RIPENo ROA
2001:678:4f0::/48RIPENo ROA
2a02:158:1200::/39RIPEValid
2a02:158:aa00::/48RIPEValid
2a02:158:aa01::/48RIPEValid
2a02:158:aa02::/48RIPEValid

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.