bgpreport

Network · data from 2026-11-12

AS49592 Pipe Networks GmbH

Registry name: PIPE-NET Pipe Networks GmbH, AT · PeeringDB

46IPv4 routes 32.6% RPKI valid · 28.3% with a route object
6IPv6 routes 100.0% RPKI valid · 100.0% with a route object
27RPKI invalid 26 origin · 1 maxLength
4No ROA 33 with no route object for this origin
31Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS49592, seen from no peer

Announced routes

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

212.189.26.0/24 Invalid: origin Other origin only 14 2%low visibility 9
16.216.60.0/22 Invalid: origin Other origin only 3 0%low visibility 3
67.227.97.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.108.129.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.108.214.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.109.0.0/24 Invalid: origin None 2 0%low visibility 2
82.109.1.0/24 Invalid: origin None 2 0%low visibility 2
82.109.2.0/24 Invalid: origin None 2 0%low visibility 2
82.109.3.0/24 Invalid: origin None 2 0%low visibility 2
82.109.232.0/24 Invalid: origin None 2 0%low visibility 2
82.109.233.0/24 Invalid: origin None 2 0%low visibility 2
82.109.234.0/24 Invalid: origin None 2 0%low visibility 2
82.109.235.0/24 Invalid: origin None 2 0%low visibility 2
87.83.21.0/24 Invalid: origin Other origin only 2 0%low visibility 2
87.83.23.0/24 Invalid: origin None 2 0%low visibility 2
87.84.57.0/24 Invalid: origin None 2 0%low visibility 2
87.84.213.0/24 Invalid: origin None 2 0%low visibility 2
87.84.215.0/24 Invalid: origin None 2 0%low visibility 2
87.85.226.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.194.168.0/24 Invalid: origin None 2 0%low visibility 1
94.194.169.0/24 Invalid: origin None 2 0%low visibility 1
94.194.170.0/24 Invalid: origin None 2 0%low visibility 1
94.194.171.0/24 Invalid: origin None 2 0%low visibility 1
151.246.132.0/22 Invalid: origin None 2 0%low visibility 2
188.220.198.0/24 Invalid: origin Other origin only 2 0%low visibility 2
192.132.192.0/22 Invalid: origin Other origin only 2 0%low visibility 2
192.88.182.110/32 Invalid: maxLength Nonecovered by 192.88.182.0/24 1 0%low visibility 1
178.83.208.0/22 No ROA None 2 0%low visibility 2
51.241.104.0/22 No ROA None 1 0%low visibility 1
82.108.132.0/24 No ROA RIR databaseRADB, RIPE 670 100% 68
157.173.4.0/23 No ROA RIR databaseRIPE 2 0%low visibility 2
94.194.84.0/24 Valid Nonecovered by 94.194.84.0/22 672 100% 66
94.194.85.0/24 Valid Nonecovered by 94.194.84.0/22 672 100% 66
94.194.86.0/24 Valid Nonecovered by 94.194.84.0/22 672 100% 66
94.194.87.0/24 Valid Nonecovered by 94.194.84.0/22 672 100% 66
83.143.119.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.201.0/24 Valid RIR databaseRIPE 673 100% 67
48.102.239.0/24 Valid RIR databaseRIPE 672 100% 66
157.173.4.0/24 Valid RIR databaseRIPE 672 100% 66
192.88.181.0/24 Valid RIR databaseARIN 672 100% 66
192.88.182.0/24 Valid RIR databaseARIN 672 100% 66
157.173.7.0/24 Valid RIR databaseRIPE 671 100% 67
79.175.102.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
82.108.128.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
157.173.3.0/24 Valid RIR databaseRIPE 670 100% 68
2a07:cec0:4403::/48 Valid RIR databaseRIPE 636 100% 69
2602:fa0a:20::/44 Valid RIR databaseARIN 635 100% 69
2a07:cec0:4404::/48 Valid RIR databaseRIPE 634 100% 69
2602:fa0a:10::/44 Valid RIR databaseARIN 633 100% 69
2602:fa0a:50::/44 Valid RIR databaseARIN 633 100% 69
2a12:bec0:340::/44 Valid RIR databaseRIPE 594 93% 66
157.173.6.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS49592: RIPE::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 (AS49592 isn't in the set, or no route object for AS49592 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 objectsAS49592 in itNot covered
RIPE::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 29

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

  • ROA: origin26
  • ROA: maxLength1
  • ROA: none4
  • Route object: none33
  • AS-SET: missing member4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin212.189.26.0/24ROAs covering it name AS834, AS3257, not AS49592. If AS49592 should announce it, add a ROA for AS49592.14 of 673
Route object: none212.189.26.0/24Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.14 of 673
ROA: origin16.216.60.0/22ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.3 of 673
Route object: none16.216.60.0/22Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.3 of 673
ROA: origin67.227.97.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none67.227.97.0/24Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.108.129.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.108.129.0/24Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.108.214.0/24ROAs covering it name AS218911, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.108.214.0/24Route objects for it name AS218911. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.0.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.0.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.1.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.1.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.2.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.2.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.3.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.3.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.232.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.232.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.233.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.233.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.234.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.234.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin82.109.235.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none82.109.235.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.83.21.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.83.21.0/24Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.83.23.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.83.23.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.84.57.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.84.57.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.84.213.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.84.213.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.84.215.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.84.215.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin87.85.226.0/24ROAs covering it name AS147281, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none87.85.226.0/24Route objects for it name AS147281. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin94.194.168.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none94.194.168.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin94.194.169.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none94.194.169.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin94.194.170.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none94.194.170.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin94.194.171.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none94.194.171.0/24No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin151.246.132.0/22ROAs covering it name AS834, AS211484, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none151.246.132.0/22No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin188.220.198.0/24ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none188.220.198.0/24Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: origin192.132.192.0/22ROAs covering it name AS834, not AS49592. If AS49592 should announce it, add a ROA for AS49592.2 of 673
Route object: none192.132.192.0/22Route objects for it name AS834. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: maxLength192.88.182.110/32ROA 192.88.182.0/24 AS49592 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.88.182.110/32.1 of 673
Route object: none192.88.182.110/32No route object for it. A route object for 192.88.182.0/24 with origin AS49592 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49592 in the RIR database for the space.1 of 673
ROA: none178.83.208.0/22No ROA covers it. Add a ROA for AS49592, maxLength 22.2 of 673
Route object: none178.83.208.0/22No route object for it. Add a route object with origin AS49592 in the RIR database for the space.2 of 673
ROA: none51.241.104.0/22No ROA covers it. Add a ROA for AS49592, maxLength 22.1 of 673
Route object: none51.241.104.0/22No route object for it. Add a route object with origin AS49592 in the RIR database for the space.1 of 673
ROA: none82.108.132.0/24No ROA covers it. Add a ROA for AS49592, maxLength 24.670 of 673
ROA: none157.173.4.0/23No ROA covers it. Add a ROA for AS49592, maxLength 23.2 of 673
Route object: none94.194.84.0/24No route object for it. A route object for 94.194.84.0/22 with origin AS49592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49592 in the RIR database for the space.672 of 673
Route object: none94.194.85.0/24No route object for it. A route object for 94.194.84.0/22 with origin AS49592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49592 in the RIR database for the space.672 of 673
Route object: none94.194.86.0/24No route object for it. A route object for 94.194.84.0/22 with origin AS49592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49592 in the RIR database for the space.672 of 673
Route object: none94.194.87.0/24No route object for it. A route object for 94.194.84.0/22 with origin AS49592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49592 in the RIR database for the space.672 of 673
AS-SET: missing memberRIPE::AS-PIPEAS-PIPE (RIPE) lists AS198351:AS-SECUREWAN; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PIPEAS-PIPE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PIPEAS-PIPE (RIPE) lists AS208191:AS-GOHOST; no IRR database read has it.
AS-SET: missing memberRIPE::AS-PIPEAS-PIPE (RIPE) lists AS213465:AS-RAINBOW; no IRR database read has it.

Route objects not announced

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

94.194.84.0/22RADB, RIPEValid
157.173.0.0/22RIPEValid
192.88.183.0/24ARINValid
2602:fa0a:40::/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.