bgpreport

Network · data from 2026-11-12

AS35684 SHC SHC Netzwerktechnik GmbH

Registry name: SHC SHC Netzwerktechnik GmbH, DE · not in PeeringDB

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

Announced routes

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

2001:678:302::/48 No ROA RIR databaseRIPE 633 100% 67
109.71.26.0/23 Valid None 673 100% 66
93.188.56.0/22 Valid RIR databaseRIPE 673 100% 66
185.79.44.0/22 Valid RIR databaseRIPE 673 100% 66
185.178.40.0/22 Valid RIR databaseRIPE 673 100% 66
194.59.192.0/22 Valid RIR databaseRIPE 673 100% 66
195.137.191.0/24 Valid RIR databaseRIPE 673 100% 66
2001:678:b68::/48 Valid RIR databaseRIPE 633 100% 67
2001:67c:74::/48 Valid RIR databaseRIPE 633 100% 67
2001:67c:18b0::/48 Valid RIR databaseRIPE 633 100% 67
2a05:7180::/29 Valid RIR databaseRIPE 632 99% 67
2a06:8500::/29 Valid RIR databaseRIPE 632 99% 67
2a06:9300::/29 Valid RIR databaseRIPE 632 99% 67
2a0c:d980::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS35684 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 10 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2001:678:302::/48No ROA covers it. Add a ROA for AS35684, maxLength 48.633 of 636
Route object: none109.71.26.0/23No route object for it. Add a route object with origin AS35684 in the RIR database for the space.673 of 673

Route objects not announced

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

185.117.160.0/22RIPENo ROA
185.117.162.0/23RIPENo ROA
185.178.40.0/24RIPEInvalid: maxLength
185.178.41.0/24RIPEInvalid: maxLength
185.178.42.0/24RIPEInvalid: maxLength
185.178.43.0/24RIPEInvalid: maxLength
193.239.162.0/23RIPEValid
2a0a:5280::/29RIPENo 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.