bgpreport

Network · data from 2026-11-12

AS23061 PIPELCC-AS - Pipe Networks LLC

Registry name: PIPELCC-AS - Pipe Networks LLC, US · not in PeeringDB

29IPv4 routes 65.5% RPKI valid · 58.6% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
9RPKI invalid 9 origin · 0 maxLength
2No ROA 13 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS23061, seen from no peer

Announced routes

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

109.66.40.0/24 Invalid: origin None 2 0%low visibility 2
109.66.41.0/24 Invalid: origin None 2 0%low visibility 2
109.66.42.0/24 Invalid: origin None 2 0%low visibility 2
109.66.43.0/24 Invalid: origin None 2 0%low visibility 2
109.66.200.0/24 Invalid: origin Other origin only 2 0%low visibility 2
109.66.201.0/24 Invalid: origin Other origin only 2 0%low visibility 2
109.66.202.0/24 Invalid: origin None 2 0%low visibility 2
109.66.203.0/24 Invalid: origin None 2 0%low visibility 2
187.14.180.0/24 Invalid: origin Other origin only 0 0%low visibility 1
109.66.200.0/22 No ROA None 2 0%low visibility 2
2602:fa0a::/40 No ROA None 1 0%low visibility 1
79.180.190.0/24 Valid Nonecovered by 79.180.190.0/23 2 0%low visibility 1
79.180.191.0/24 Valid Nonecovered by 79.180.190.0/23 2 0%low visibility 1
31.57.55.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
62.105.196.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
62.144.44.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
62.144.46.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
88.80.137.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
109.65.84.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
109.66.57.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
189.12.138.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
200.138.29.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.216.226.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
45.143.9.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
79.183.71.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
109.65.209.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
186.241.187.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
189.12.159.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
201.4.24.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
217.216.251.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1

AS-SET

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

  • ROA: origin9
  • ROA: none2
  • Route object: none13
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin109.66.40.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.40.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.41.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.41.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.42.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.42.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.43.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.43.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.200.0/24ROAs covering it name AS218754, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.200.0/24Route objects for it name AS218754. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.201.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.201.0/24Route objects for it name AS834. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.202.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.202.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin109.66.203.0/24ROAs covering it name AS834, not AS23061. If AS23061 should announce it, add a ROA for AS23061.2 of 673
Route object: none109.66.203.0/24No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: origin187.14.180.0/24ROAs covering it name AS9009, not AS23061. If AS23061 should announce it, add a ROA for AS23061.0 of 673
Route object: none187.14.180.0/24Route objects for it name AS9009. Add a route object with origin AS23061 in the RIR database for the space.0 of 673
ROA: none109.66.200.0/22No ROA covers it. Add a ROA for AS23061, maxLength 22.2 of 673
Route object: none109.66.200.0/22No route object for it. Add a route object with origin AS23061 in the RIR database for the space.2 of 673
ROA: none2602:fa0a::/40No ROA covers it. Add a ROA for AS23061, maxLength 40.1 of 636
Route object: none2602:fa0a::/40No route object for it. Add a route object with origin AS23061 in the RIR database for the space.1 of 636
Route object: none79.180.190.0/24No route object for it. A route object for 79.180.190.0/23 with origin AS23061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23061 in the RIR database for the space.2 of 673
Route object: none79.180.191.0/24No route object for it. A route object for 79.180.190.0/23 with origin AS23061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23061 in the RIR database for the space.2 of 673

Route objects not announced

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

8.39.119.0/24RADBNo ROA
23.163.104.0/24ARINValid
79.180.190.0/23RADB, RIPEValid

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.