bgpreport

Network · data from 2026-11-12

AS64457 Matteo Fruhwald trading as PipeHost e.U.

Registry name: PIPEHOST-AS Matteo Fruhwald trading as PipeHost e.U., AT · PeeringDB

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

Announced routes

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

51.241.7.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.194.144.0/24 Invalid: origin None 2 0%low visibility 1
94.194.145.0/24 Invalid: origin None 2 0%low visibility 1
94.194.146.0/24 Invalid: origin None 2 0%low visibility 1
94.194.147.0/24 Invalid: origin None 2 0%low visibility 1
188.137.158.0/24 Valid None 671 100% 67
16.220.157.0/24 Valid RIR databaseARIN, RADB 672 100% 66
151.242.144.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.224.3.0/24 Valid RIR databaseRIPE 670 100% 67
2a14:7c0:f100::/40 Valid RIR databaseRIPE 635 100% 69
2a14:7c0:f300::/40 Valid RIR databaseRIPE 634 100% 69
62.144.51.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
79.183.89.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
109.65.46.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
141.11.192.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
148.135.183.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
152.237.241.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
164.37.212.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
167.148.190.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
167.148.222.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
168.222.74.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
186.241.186.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
191.44.82.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
201.4.25.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
217.216.172.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS64457: AS-PIPE. 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 (AS64457 isn't in the set, or no route object for AS64457 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 objectsAS64457 in itNot covered
AS-PIPE RIPElists itself further down4 member sets in no database: AS198351:AS-SECUREWAN, AS199746:AS-NEXTSERV, AS208191:AS-GOHOST, AS213465:AS-RAINBOW 113112,957 Yes 6
NTTCOM (also) 912,347 No 25

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

  • ROA: origin5
  • Route object: none6
  • AS-SET: missing member4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin51.241.7.0/24ROAs covering it name AS402535, not AS64457. If AS64457 should announce it, add a ROA for AS64457.2 of 673
Route object: none51.241.7.0/24Route objects for it name AS402535. Add a route object with origin AS64457 in the RIR database for the space.2 of 673
ROA: origin94.194.144.0/24ROAs covering it name AS834, not AS64457. If AS64457 should announce it, add a ROA for AS64457.2 of 673
Route object: none94.194.144.0/24No route object for it. Add a route object with origin AS64457 in the RIR database for the space.2 of 673
ROA: origin94.194.145.0/24ROAs covering it name AS834, not AS64457. If AS64457 should announce it, add a ROA for AS64457.2 of 673
Route object: none94.194.145.0/24No route object for it. Add a route object with origin AS64457 in the RIR database for the space.2 of 673
ROA: origin94.194.146.0/24ROAs covering it name AS834, not AS64457. If AS64457 should announce it, add a ROA for AS64457.2 of 673
Route object: none94.194.146.0/24No route object for it. Add a route object with origin AS64457 in the RIR database for the space.2 of 673
ROA: origin94.194.147.0/24ROAs covering it name AS834, not AS64457. If AS64457 should announce it, add a ROA for AS64457.2 of 673
Route object: none94.194.147.0/24No route object for it. Add a route object with origin AS64457 in the RIR database for the space.2 of 673
Route object: none188.137.158.0/24No route object for it. Add a route object with origin AS64457 in the RIR database for the space.671 of 673
AS-SET: missing memberAS-PIPEAS-PIPE (RIPE) lists AS198351:AS-SECUREWAN; no IRR database read has it.
AS-SET: missing memberAS-PIPEAS-PIPE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS-PIPEAS-PIPE (RIPE) lists AS208191:AS-GOHOST; no IRR database read has it.
AS-SET: missing memberAS-PIPEAS-PIPE (RIPE) lists AS213465:AS-RAINBOW; no IRR database read has it.

Route objects not announced

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

192.88.180.0/24ARINInvalid: origin
2602:fa0a:30::/44ARINValid

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.