Network · data from 2026-11-12

AS396905 HomeWorks Connect

Registry name: HOMEWORKS-1 - HomeWorks Connect, US · PeeringDB

9IPv4 routes 88.9% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


137.119.24.0/24	No ROA	Other IRR onlyRADB	671 100%	68
64.72.160.0/20	Valid	RIR databaseARIN	671 100%	68
66.187.96.0/20	Valid	RIR databaseARIN, RADB	671 100%	68
138.43.60.0/22	Valid	RIR databaseARIN, RADB	671 100%	68
149.19.208.0/20	Valid	RIR databaseARIN	671 100%	68
192.43.156.0/22	Valid	RIR databaseARIN, RADB	671 100%	68
192.82.44.0/22	Valid	RIR databaseARIN, RADB	671 100%	68
192.105.176.0/20	Valid	RIR databaseARIN	671 100%	68
216.226.160.0/20	Valid	RIR databaseARIN	671 100%	68
2606:a740::/32	Valid	RIR databaseARIN	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS396905: AS-HOMEWORKS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS396905 isn't in the set, or no route object for AS396905 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS396905 in it	Not covered
AS-HOMEWORKS	ARIN	5	1	41	Yes	0

Name

Database

ASNs

Sets

Route objects

AS396905 in it

Not covered

AS-HOMEWORKS

ARIN

Yes

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

ROA: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	137.119.24.0/24	No ROA covers it. Add a ROA for AS396905, maxLength 24.	671 of 673
Route object: RIR	137.119.24.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

137.119.24.0/24

No ROA covers it. Add a ROA for AS396905, maxLength 24.

671 of 673

Route object: RIR

137.119.24.0/24

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

671 of 673

Route objects not announced

Every route object with origin AS396905 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.