bgpreport

Network · data from 2026-11-12

AS57395 HARTL-EDV-AS synaforce GmbH

Registry name: HARTL-EDV-AS synaforce GmbH, DE · not in PeeringDB

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

Announced routes

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

149.13.71.0/24 No ROA Other IRR onlyRADB 673 100% 67
5.183.48.0/22 Valid RIR databaseRIPE 673 100% 67
89.207.153.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.160.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.161.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.162.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.163.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.164.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.165.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.166.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.167.0/24 Valid RIR databaseRIPE 673 100% 67
176.124.36.0/24 Valid RIR databaseRIPE 673 100% 67
176.124.37.0/24 Valid RIR databaseRIPE 673 100% 67
185.155.192.0/22 Valid RIR databaseRIPE 673 100% 67
185.181.168.0/24 Valid RIR databaseRIPE 673 100% 67
185.181.169.0/24 Valid RIR databaseRIPE 673 100% 67
185.181.170.0/24 Valid RIR databaseRIPE 673 100% 67
185.181.171.0/24 Valid RIR databaseRIPE 673 100% 67
185.254.0.0/24 Valid RIR databaseRIPE 673 100% 67
185.254.3.0/24 Valid RIR databaseRIPE 673 100% 67
185.255.80.0/22 Valid RIR databaseRIPE 673 100% 67
193.150.64.0/24 Valid RIR databaseRIPE 673 100% 67
194.93.8.0/22 Valid RIR databaseRIPE 673 100% 67
2a07:9580::/40 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:1::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:2::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:3::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:6::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:10::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:50::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:51::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:107::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:112::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:113::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:114::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:117::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:118::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:33c0:134::/48 Valid RIR databaseRIPE 634 100% 67
2a0e:d200::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS57395 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 16 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none149.13.71.0/24No ROA covers it. Add a ROA for AS57395, maxLength 24.673 of 673
Route object: RIR149.13.71.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

149.7.19.0/24RADBNo ROA
154.47.0.0/24RADBNo ROA
154.47.1.0/24RADBNo ROA
176.98.160.0/21RIPENo ROA
185.181.168.0/22RIPENo ROA
185.254.1.0/24RIPEValid
194.26.16.0/24RIPEValid
2001:67c:2520::/48RIPENo ROA
2a0b:33c0::/29RIPENo ROA
2a0b:33c0:4::/48RIPENo ROA
2a0b:33c0:5::/48RIPENo ROA
2a0b:33c0:a::/48RIPENo ROA
2a0b:33c0:116::/48RIPENo ROA
2a11:9400::/32RIPEValid

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.