bgpreport

Network · data from 2026-11-12

AS12731 Portus Data Centers / IPHH

Registry name: IPHH IPHH Internet Port Hamburg GmbH, DE · PeeringDB

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

Announced routes

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

185.8.224.0/24 No ROA RIR databaseRIPE 672 100% 66
192.129.45.0/24 No ROA RIR databaseRIPE 672 100% 66
2a03:4240::/32 No ROA RIR databaseRIPE 636 100% 67
62.201.171.0/24 Valid Nonecovered by 62.201.160.0/19 668 99% 67
45.130.192.0/23 Valid RIR databaseRIPE 672 100% 66
62.201.160.0/19 Valid RIR databaseRIPE 672 100% 66
91.216.90.0/24 Valid RIR databaseRIPE 672 100% 66
185.34.67.0/24 Valid RIR databaseRIPE 672 100% 66
185.53.220.0/22 Valid RIR databaseRIPE 672 100% 66
193.41.8.0/23 Valid RIR databaseRIPE 672 100% 66
194.113.42.0/23 Valid RIR databaseRIPE 672 100% 66
213.128.128.0/19 Valid RIR databaseRIPE 672 100% 66
2001:678:2c4::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:57c0:800::/38 Valid RIR databaseRIPE 636 100% 67
2a0f:f640::/47 Valid RIR databaseRIPE 636 100% 67
2001:868::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS12731: RIPE::AS-IPHH. 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 (AS12731 isn't in the set, or no route object for AS12731 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 objectsAS12731 in itNot covered
RIPE::AS-IPHH RIPElists itself further down2 member sets in no database: AS-SDN-CLINIC-LAB, AS216038:AS-EF 5918602 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 12 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • AS-SET: missing member2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none185.8.224.0/24No ROA covers it. Add a ROA for AS12731, maxLength 24.672 of 673
ROA: none192.129.45.0/24No ROA covers it. Add a ROA for AS12731, maxLength 24.672 of 673
ROA: none2a03:4240::/32No ROA covers it. Add a ROA for AS12731, maxLength 32.636 of 636
Route object: none62.201.171.0/24No route object for it. A route object for 62.201.160.0/19 with origin AS12731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12731 in the RIR database for the space.668 of 673
AS-SET: missing memberRIPE::AS-IPHHAS-IPHH (RIPE) lists AS-SDN-CLINIC-LAB; no IRR database read has it.
AS-SET: missing memberRIPE::AS-IPHHAS-IPHH (RIPE) lists AS216038:AS-EF; no IRR database read has it.

Route objects not announced

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

62.201.172.0/24RIPEValid
193.96.224.0/24RIPEInvalid: origin
194.113.42.0/24RIPEInvalid: maxLength
213.128.151.0/24RIPEValid
2a0f:f640::/32RIPENo ROA
2a0f:f640::/48RIPEInvalid: maxLength

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.