bgpreport

Network · data from 2026-11-12

AS397735 NETWIRE-INC - Netwire inc

Registry name: NETWIRE-INC - Netwire inc, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397735, 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.
74.120.104.0/24 Valid Nonecovered by 74.120.104.0/22 672 100% 67
74.120.105.0/24 Valid Nonecovered by 74.120.104.0/22 672 100% 67
74.120.106.0/24 Valid Nonecovered by 74.120.104.0/22 672 100% 67
74.120.107.0/24 Valid Nonecovered by 74.120.104.0/22 672 100% 67
2a0e:dd40::/32 Valid Other IRR onlyRADB 636 100% 68
142.202.138.0/23 Valid RIR databaseARIN 673 100% 67
158.51.44.0/22 Valid RIR databaseARIN 673 100% 67
173.195.104.0/23 Valid RIR databaseARIN 673 100% 67
193.53.2.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.53.5.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.53.7.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.53.12.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
198.175.20.0/22 Valid RIR databaseARIN 673 100% 67
198.200.185.0/24 Valid RIR databaseARIN 673 100% 67
45.142.248.0/24 Valid RIR databaseRIPE 672 100% 67
45.142.249.0/24 Valid RIR databaseRIPE 672 100% 67
45.142.250.0/24 Valid RIR databaseRIPE 672 100% 67
45.142.251.0/24 Valid RIR databaseRIPE 672 100% 67
2605:54c0::/32 Valid RIR databaseARIN, RADB 635 100% 69
2606:3740::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

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

  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none74.120.104.0/24No route object for it. A route object for 74.120.104.0/22 with origin AS397735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397735 in the RIR database for the space.672 of 673
Route object: none74.120.105.0/24No route object for it. A route object for 74.120.104.0/22 with origin AS397735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397735 in the RIR database for the space.672 of 673
Route object: none74.120.106.0/24No route object for it. A route object for 74.120.104.0/22 with origin AS397735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397735 in the RIR database for the space.672 of 673
Route object: none74.120.107.0/24No route object for it. A route object for 74.120.104.0/22 with origin AS397735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397735 in the RIR database for the space.672 of 673
Route object: RIR2a0e:dd40::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.142.248.0/22RADBNo ROA
74.120.104.0/22ARINValid

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.