bgpreport

Network · data from 2026-11-12

AS205112 PHILUNET GmbH

Registry name: PHILUNET PHILUNET GmbH, DE · PeeringDB

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

Announced routes

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

45.151.164.0/23 No ROA RIR databaseRIPE 673 100% 66
45.151.167.0/24 No ROA RIR databaseRIPE 672 100% 66
2a0f:6481::/32 Valid Nonecovered by 2a0f:6480::/29 407 64% 65
45.157.240.0/22 Valid RIR databaseRIPE 673 100% 66
185.65.240.0/24 Valid RIR databaseRIPE 673 100% 66
185.65.242.0/24 Valid RIR databaseRIPE 673 100% 66
185.117.214.0/24 Valid RIR databaseRIPE 673 100% 66
185.138.54.0/24 Valid RIR databaseRIPE 673 100% 66
185.232.100.0/22 Valid RIR databaseRIPE 673 100% 66
185.232.100.0/24 Valid RIR databaseRIPE 673 100% 66
185.232.102.0/24 Valid RIR databaseRIPE 673 100% 66
185.232.103.0/24 Valid RIR databaseRIPE 673 100% 66
45.157.241.0/24 Valid RIR databaseRIPE 672 100% 66
45.157.242.0/24 Valid RIR databaseRIPE 672 100% 66
2a06:8784::/32 Valid RIR databaseRIPE 635 100% 67
2a07:a40:c::/48 Valid RIR databaseRIPE 635 100% 67
2a0c:1700:3::/48 Valid RIR databaseRIPE 635 100% 67
2a0f:6480::/32 Valid RIR databaseRIPE 635 100% 67
2a0c:1700::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:6480::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS205112: RIPE::AS-PHILUNET. 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 (AS205112 isn't in the set, or no route object for AS205112 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 objectsAS205112 in itNot covered
RIPE::AS-PHILUNET RIPElists itself further down12 member sets in no database: AS-A, AS-CAST, AS-IPV6GO, AS-JSMSR-DOWNSTREAMS, AS-ROUTE48 … 282876,492 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 19 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • AS-SET: missing member12
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.151.164.0/23No ROA covers it. Add a ROA for AS205112, maxLength 23.673 of 673
ROA: none45.151.167.0/24No ROA covers it. Add a ROA for AS205112, maxLength 24.672 of 673
Route object: none2a0f:6481::/32No route object for it. A route object for 2a0f:6480::/29 with origin AS205112 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205112 in the RIR database for the space.407 of 636
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-A; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-CAST; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-IPV6GO; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-JSMSR-DOWNSTREAMS; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-ROUTE48; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-SHIZUKUGLOBAL-EUROPE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-SVINE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS-ZH-NET; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS200372:AS-DORFHOSTER-SET; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PHILUNETAS-PHILUNET (RIPE) lists AS63800:AS-SERVG; no IRR database read has it.

Route objects not announced

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

45.157.240.0/24RIPEInvalid: maxLength
45.157.243.0/24RIPEInvalid: maxLength
185.232.101.0/24RIPEValid
2a0c:1700:1::/48RIPEValid

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.