bgpreport

Network · data from 2026-11-12

AS12440 Hughes Network Systems

Registry name: AS12440 Hughes Network Systems GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12440, 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.238.56.0/24 Valid Nonecovered by 195.238.32.0/19 672 100% 67
195.238.57.0/24 Valid Nonecovered by 195.238.32.0/19 672 100% 67
62.128.160.0/19 Valid RIR databaseRIPE 672 100% 66
62.128.168.0/21 Valid RIR databaseRIPE 672 100% 67
62.128.168.0/22 Valid RIR databaseRIPE 672 100% 67
62.128.172.0/22 Valid RIR databaseRIPE 672 100% 67
62.128.186.0/24 Valid RIR databaseRIPE 672 100% 66
62.128.188.0/24 Valid RIR databaseRIPE 672 100% 66
62.128.191.0/24 Valid RIR databaseRIPE 672 100% 66
82.214.192.0/18 Valid RIR databaseRIPE 672 100% 66
82.214.210.0/24 Valid RIR databaseRIPE 672 100% 67
82.214.223.0/24 Valid RIR databaseRIPE 672 100% 66
82.214.240.0/21 Valid RIR databaseRIPE 672 100% 67
82.214.240.0/22 Valid RIR databaseRIPE 672 100% 67
82.214.244.0/22 Valid RIR databaseRIPE 672 100% 67
128.65.64.0/20 Valid RIR databaseRIPE 672 100% 66
185.117.52.0/22 Valid RIR databaseRIPE 672 100% 66
195.238.32.0/19 Valid RIR databaseRIPE 672 100% 66
195.238.61.0/24 Valid RIR databaseRIPE 672 100% 67
195.238.62.0/24 Valid RIR databaseRIPE 672 100% 67
2a0a:1240::/32 Valid RIR databaseRIPE 636 100% 67
2a0a:1240::/40 Valid RIR databaseRIPE 636 100% 67
2a0a:1240:100::/40 Valid RIR databaseRIPE 636 100% 67
2a0a:1240:200::/40 Valid RIR databaseRIPE 636 100% 67
2a0a:1240:1000::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS12440: RIPE::AS-HNSEU. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS12440 isn't in the set, or no route object for AS12440 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS12440 in itNot covered
RIPE::AS-HNSEU RIPE 2156 Yes 0

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.

  • Route object: none2
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none195.238.56.0/24No route object for it. A route object for 195.238.32.0/19 with origin AS12440 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12440 in the RIR database for the space.672 of 673
Route object: none195.238.57.0/24No route object for it. A route object for 195.238.32.0/19 with origin AS12440 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12440 in the RIR database for the space.672 of 673

Route objects not announced

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

82.214.192.0/19RIPEValid
82.214.220.0/24RIPEValid
82.214.224.0/19RIPEValid
82.214.224.0/20RIPEValid
82.214.226.0/24RIPEValid
82.214.232.0/24RIPEValid
82.214.234.0/24RIPEValid
82.214.239.0/24RIPEValid
128.65.64.0/19RIPEValid
195.238.44.0/24RIPEValid
195.238.45.0/24RIPEValid
195.238.60.0/24RIPEValid
195.238.63.0/24RIPEValid
2a0a:1241::/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.