bgpreport

Network · data from 2026-11-12

AS34895 HOSTNET-DE-AS hostNET Medien GmbH

Registry name: HOSTNET-DE-AS hostNET Medien GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34895, 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.
83.138.80.115/32 Invalid: maxLength Nonecovered by 83.138.64.0/18 2 0%low visibility 6
83.138.89.41/32 Invalid: maxLength Nonecovered by 83.138.64.0/18 2 0%low visibility 6
185.171.139.255/32 Invalid: maxLength Nonecovered by 185.171.136.0/22 2 0%low visibility 6
83.138.64.0/18 Valid RIR databaseRIPE 673 100% 66
185.171.136.0/22 Valid RIR databaseRIPE 673 100% 66
2a01:4da0::/48 Valid RIR databaseRIPE 316 50% 63

AS-SET

AS34895 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 6 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: maxLength83.138.80.115/32ROA 83.138.64.0/18 AS34895 has maxLength 18; the route is a /32. Raise the maxLength, or add a ROA for 83.138.80.115/32.2 of 673
Route object: none83.138.80.115/32No route object for it. A route object for 83.138.64.0/18 with origin AS34895 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34895 in the RIR database for the space.2 of 673
ROA: maxLength83.138.89.41/32ROA 83.138.64.0/18 AS34895 has maxLength 18; the route is a /32. Raise the maxLength, or add a ROA for 83.138.89.41/32.2 of 673
Route object: none83.138.89.41/32No route object for it. A route object for 83.138.64.0/18 with origin AS34895 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34895 in the RIR database for the space.2 of 673
ROA: maxLength185.171.139.255/32ROA 185.171.136.0/22 AS34895 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.171.139.255/32.2 of 673
Route object: none185.171.139.255/32No route object for it. A route object for 185.171.136.0/22 with origin AS34895 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34895 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS34895 is announced.

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.