bgpreport

Network · data from 2026-11-12

AS28674 ITERGO-CORP-AS ITERGO Informationstechnologie GmbH

Registry name: ITERGO-CORP-AS ITERGO Informationstechnologie GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28674, 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.49.224.0/21 No ROA RIR databaseRIPE 673 100% 67
185.168.80.0/24 No ROA RIR databaseRIPE 672 100% 67
185.168.81.0/24 No ROA RIR databaseRIPE 672 100% 67
185.168.82.0/24 No ROA RIR databaseRIPE 672 100% 67
185.168.83.0/24 No ROA RIR databaseRIPE 672 100% 67
193.53.112.0/24 No ROA RIR databaseRIPE 672 100% 67
2001:67c:28dc::/48 No ROA RIR databaseRIPE 635 100% 68
2001:67c:2bb0::/48 No ROA RIR databaseRIPE 635 100% 68
2a0b:fa00::/32 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS28674 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 22 are in fix.csv.

  • ROA: none9
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none195.49.224.0/21No ROA covers it. Add a ROA for AS28674, maxLength 21.673 of 673
ROA: none185.168.80.0/24No ROA covers it. Add a ROA for AS28674, maxLength 24.672 of 673
ROA: none185.168.81.0/24No ROA covers it. Add a ROA for AS28674, maxLength 24.672 of 673
ROA: none185.168.82.0/24No ROA covers it. Add a ROA for AS28674, maxLength 24.672 of 673
ROA: none185.168.83.0/24No ROA covers it. Add a ROA for AS28674, maxLength 24.672 of 673
ROA: none193.53.112.0/24No ROA covers it. Add a ROA for AS28674, maxLength 24.672 of 673
ROA: none2001:67c:28dc::/48No ROA covers it. Add a ROA for AS28674, maxLength 48.635 of 636
ROA: none2001:67c:2bb0::/48No ROA covers it. Add a ROA for AS28674, maxLength 48.635 of 636
ROA: none2a0b:fa00::/32No ROA covers it. Add a ROA for AS28674, maxLength 32.635 of 636

Route objects not announced

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

185.189.96.0/24RIPENo ROA
193.53.109.0/24RIPENo ROA
193.53.110.0/24RIPENo ROA
193.53.111.0/24RIPENo ROA
2a0b:fa00:200::/44RIPENo ROA
2a0b:fa00:300::/44RIPENo ROA
2a0b:fa01::/32RIPENo ROA
2a0b:fa02::/32RIPENo ROA
2a0b:fa03::/32RIPENo ROA
2a0b:fa04::/32RIPENo ROA
2a0b:fa05::/32RIPENo ROA
2a0b:fa06::/32RIPENo ROA
2a0b:fa07::/32RIPENo ROA

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.