Network · data from 2026-11-12

AS401586 SQUIRREL - Squirrel Networks LLC

Registry name: SQUIRREL - Squirrel Networks LLC, US · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 40.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS401586, seen from no peer

Announced routes

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


89.167.156.0/24	Valid	Nonecovered by 89.167.156.0/22	670 100%	67
147.90.40.0/24	Valid	Nonecovered by 147.90.40.0/23	670 100%	67
147.90.41.0/24	Valid	Nonecovered by 147.90.40.0/23	670 100%	67
89.167.156.0/22	Valid	Other IRR onlyRADB	670 100%	67
147.90.40.0/23	Valid	RIR databaseRADB, RIPE	46 7%low visibility	29

89.167.156.0/24

Valid

Nonecovered by 89.167.156.0/22

670 100%

147.90.40.0/24

Valid

Nonecovered by 147.90.40.0/23

670 100%

147.90.41.0/24

Valid

Nonecovered by 147.90.40.0/23

670 100%

89.167.156.0/22

Valid

Other IRR onlyRADB

670 100%

147.90.40.0/23

Valid

RIR databaseRADB, RIPE

46 7%low visibility

AS-SET

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

Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: none	89.167.156.0/24	No route object for it. A route object for 89.167.156.0/22 with origin AS401586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401586 in the RIR database for the space.	670 of 673
Route object: none	147.90.40.0/24	No route object for it. A route object for 147.90.40.0/23 with origin AS401586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401586 in the RIR database for the space.	670 of 673
Route object: none	147.90.41.0/24	No route object for it. A route object for 147.90.40.0/23 with origin AS401586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401586 in the RIR database for the space.	670 of 673
Route object: RIR	89.167.156.0/22	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

89.167.156.0/24

No route object for it. A route object for 89.167.156.0/22 with origin AS401586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401586 in the RIR database for the space.

670 of 673

Route object: none

147.90.40.0/24

No route object for it. A route object for 147.90.40.0/23 with origin AS401586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401586 in the RIR database for the space.

670 of 673

Route object: none

147.90.41.0/24

670 of 673

Route object: RIR

89.167.156.0/22

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route objects not announced

Every route object with origin AS401586 is announced.

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.