bgpreport

Network · data from 2026-11-12

AS26785 Netwurx

Registry name: NETWURX-AS - Netwurx LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26785, 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.
173.0.248.0/21 No ROA Nonecovered by 173.0.240.0/20 101 15% 37
66.175.204.0/23 No ROA Nonecovered by 66.175.192.0/20 99 15% 37
66.175.192.0/20 No ROA Other IRR onlyRADB 671 100% 68
173.0.240.0/20 No ROA Other IRR onlyRADB 671 100% 68
199.200.108.0/22 No ROA Other IRR onlyRADB 671 100% 68
209.242.224.0/20 No ROA Other IRR onlyRADB 671 100% 68
2607:f4d8::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS26785's PeeringDB record names no 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 17 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none173.0.248.0/21No ROA covers it. Add a ROA for AS26785, maxLength 21.101 of 673
Route object: none173.0.248.0/21No route object for it. A route object for 173.0.240.0/20 with origin AS26785 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26785 in the RIR database for the space.101 of 673
ROA: none66.175.204.0/23No ROA covers it. Add a ROA for AS26785, maxLength 23.99 of 673
Route object: none66.175.204.0/23No route object for it. A route object for 66.175.192.0/20 with origin AS26785 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26785 in the RIR database for the space.99 of 673
ROA: none66.175.192.0/20No ROA covers it. Add a ROA for AS26785, maxLength 20.671 of 673
Route object: RIR66.175.192.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none173.0.240.0/20No ROA covers it. Add a ROA for AS26785, maxLength 20.671 of 673
Route object: RIR173.0.240.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.200.108.0/22No ROA covers it. Add a ROA for AS26785, maxLength 22.671 of 673
Route object: RIR199.200.108.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none209.242.224.0/20No ROA covers it. Add a ROA for AS26785, maxLength 20.671 of 673
Route object: RIR209.242.224.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f4d8::/32No ROA covers it. Add a ROA for AS26785, maxLength 32.634 of 636
Route object: RIR2607:f4d8::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

69.28.24.0/21RADBNo ROA
104.36.144.0/22RADBNo ROA
192.132.13.0/24RADBNo ROA

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.