bgpreport

Network · data from 2026-11-12

AS198218 HTS-MOOSBURG Horizon Teleports GmbH

Registry name: HTS-MOOSBURG Horizon Teleports GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198218, 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.
82.205.134.0/24 Valid Nonecovered by 82.205.134.0/23 673 100% 67
82.205.208.0/20 Valid None 673 100% 67
2a03:d080::/32 Valid None 635 100% 67
82.205.128.0/22 Valid RIR databaseRIPE 673 100% 67
82.205.160.0/21 Valid RIR databaseRIPE 673 100% 67
82.205.168.0/21 Valid RIR databaseRIPE 673 100% 67
82.205.176.0/21 Valid RIR databaseRIPE 673 100% 67
82.205.202.0/23 Valid RIR databaseRIPE 673 100% 67
82.205.204.0/22 Valid RIR databaseRIPE 673 100% 67
164.40.160.0/21 Valid RIR databaseRIPE 673 100% 67
82.205.184.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS198218 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.

  • Route object: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none82.205.134.0/24No route object for it. A route object for 82.205.134.0/23 with origin AS198218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198218 in the RIR database for the space.673 of 673
Route object: none82.205.208.0/20No route object for it. Add a route object with origin AS198218 in the RIR database for the space.673 of 673
Route object: none2a03:d080::/32No route object for it. Add a route object with origin AS198218 in the RIR database for the space.635 of 636

Route objects not announced

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

82.205.134.0/23RIPENo ROA
82.205.136.0/21RIPENo ROA
82.205.144.0/20RIPENo ROA
82.205.192.0/21RIPENo ROA
82.205.208.0/21RIPEValid
82.205.224.0/20RIPEValid
82.205.240.0/21RIPEValid

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.