bgpreport

Network · data from 2026-11-12

AS219036 PIPE-NET Pipe Networks GmbH

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

19IPv4 routes 10.5% RPKI valid · 0.0% with a route object
0IPv6 routes
17RPKI invalid 17 origin · 0 maxLength
0No ROA 19 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS219036, seen from no peer

Announced routes

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

13.141.112.0/24 Invalid: origin None 14 2%low visibility 8
13.141.113.0/24 Invalid: origin None 14 2%low visibility 8
13.141.114.0/24 Invalid: origin None 14 2%low visibility 8
13.141.115.0/24 Invalid: origin None 14 2%low visibility 8
13.141.116.0/24 Invalid: origin None 14 2%low visibility 8
13.141.117.0/24 Invalid: origin None 14 2%low visibility 8
13.141.118.0/24 Invalid: origin None 14 2%low visibility 8
13.141.119.0/24 Invalid: origin None 14 2%low visibility 8
152.237.250.0/24 Invalid: origin None 14 2%low visibility 8
152.237.251.0/24 Invalid: origin None 14 2%low visibility 8
87.82.63.0/24 Invalid: origin Other origin only 1 0%low visibility 1
87.86.20.0/24 Invalid: origin None 1 0%low visibility 1
87.86.21.0/24 Invalid: origin None 1 0%low visibility 1
87.86.210.0/24 Invalid: origin None 1 0%low visibility 1
87.86.211.0/24 Invalid: origin None 1 0%low visibility 1
87.83.123.0/24 Invalid: origin Other origin only 0 0%low visibility 1
87.83.199.0/24 Invalid: origin Other origin only 0 0%low visibility 1
194.77.10.0/24 Valid Nonecovered by 194.77.10.0/23 2 0%low visibility 1
194.77.11.0/24 Valid Nonecovered by 194.77.10.0/23 2 0%low visibility 1

AS-SET

AS219036 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin17
  • Route object: none19
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin13.141.112.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.112.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.113.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.113.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.114.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.114.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.115.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.115.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.116.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.116.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.117.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.117.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.118.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.118.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin13.141.119.0/24ROAs covering it name AS2914, AS9304, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none13.141.119.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin152.237.250.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none152.237.250.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin152.237.251.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.14 of 673
Route object: none152.237.251.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.14 of 673
ROA: origin87.82.63.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.1 of 673
Route object: none87.82.63.0/24Route objects for it name AS834. Add a route object with origin AS219036 in the RIR database for the space.1 of 673
ROA: origin87.86.20.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.1 of 673
Route object: none87.86.20.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.1 of 673
ROA: origin87.86.21.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.1 of 673
Route object: none87.86.21.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.1 of 673
ROA: origin87.86.210.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.1 of 673
Route object: none87.86.210.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.1 of 673
ROA: origin87.86.211.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.1 of 673
Route object: none87.86.211.0/24No route object for it. Add a route object with origin AS219036 in the RIR database for the space.1 of 673
ROA: origin87.83.123.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.0 of 673
Route object: none87.83.123.0/24Route objects for it name AS834. Add a route object with origin AS219036 in the RIR database for the space.0 of 673
ROA: origin87.83.199.0/24ROAs covering it name AS834, not AS219036. If AS219036 should announce it, add a ROA for AS219036.0 of 673
Route object: none87.83.199.0/24Route objects for it name AS834. Add a route object with origin AS219036 in the RIR database for the space.0 of 673
Route object: none194.77.10.0/24No route object for it. A route object for 194.77.10.0/23 with origin AS219036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219036 in the RIR database for the space.2 of 673
Route object: none194.77.11.0/24No route object for it. A route object for 194.77.10.0/23 with origin AS219036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219036 in the RIR database for the space.2 of 673

Route objects not announced

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

194.77.10.0/23RADBValid

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.