bgpreport

Network · data from 2026-11-12

AS12643 IGD Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.

Registry name: IGD Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V., DE · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS12643, seen from no peer

Announced routes

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

146.140.0.0/16 No ROA RIR databaseRIPE 672 100% 68
2001:67c:134::/48 No ROA RIR databaseRIPE 635 100% 68
129.233.208.0/23 Valid RIR databaseRIPE 672 100% 68
153.96.244.0/22 Valid RIR databaseRIPE 672 100% 68
192.44.32.0/22 Valid RIR databaseRIPE 672 100% 68
192.67.200.0/21 Valid RIR databaseRIPE 672 100% 68
2a03:db80:3410::/48 Valid RIR databaseRIPE 635 100% 68

AS-SET

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

  • ROA: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none146.140.0.0/16No ROA covers it. Add a ROA for AS12643, maxLength 16.672 of 673
ROA: none2001:67c:134::/48No ROA covers it. Add a ROA for AS12643, maxLength 48.635 of 636

Route objects not announced

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

2a03:db80:3430::/48RIPEInvalid: origin
2a03:db80:3434::/48RIPEInvalid: origin

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.