Network · data from 2026-11-12

AS399494 Brooke Telecom Cooperative

Registry name: BROOKETEL-AS-01 - Brooke Telecom Cooperative Limited, CA · PeeringDB

9IPv4 routes 55.6% 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

4No 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 AS399494, seen from no peer

Announced routes

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


67.220.34.0/24	No ROA	RIR databaseARIN	670 100%	68
96.44.44.0/24	No ROA	RIR databaseARIN	670 100%	68
173.255.72.0/21	No ROA	RIR databaseARIN	670 100%	67
216.46.158.0/24	No ROA	RIR databaseARIN	670 100%	68
155.254.196.0/22	Valid	RIR databaseARIN, RADB	670 100%	68
165.140.44.0/22	Valid	RIR databaseARIN, RADB	670 100%	68
170.205.48.0/22	Valid	RIR databaseARIN	670 100%	68
199.19.24.0/22	Valid	RIR databaseARIN	670 100%	68
199.241.48.0/22	Valid	RIR databaseARIN	670 100%	68
2604:3b40::/32	Valid	RIR databaseARIN, RADB	571 90%	67

AS-SET

PeeringDB's irr_as_set for AS399494: ARIN::AS-BROOKETEL. 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 (AS399494 isn't in the set, or no route object for AS399494 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	AS399494 in it	Not covered
ARIN::AS-BROOKETEL	ARIN	1	1	10	Yes	0

Name

Database

ASNs

Sets

Route objects

AS399494 in it

Not covered

ARIN::AS-BROOKETEL

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

ROA: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	67.220.34.0/24	No ROA covers it. Add a ROA for AS399494, maxLength 24.	670 of 673
ROA: none	96.44.44.0/24	No ROA covers it. Add a ROA for AS399494, maxLength 24.	670 of 673
ROA: none	173.255.72.0/21	No ROA covers it. Add a ROA for AS399494, maxLength 21.	670 of 673
ROA: none	216.46.158.0/24	No ROA covers it. Add a ROA for AS399494, maxLength 24.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

67.220.34.0/24

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

670 of 673

ROA: none

96.44.44.0/24

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

670 of 673

ROA: none

173.255.72.0/21

No ROA covers it. Add a ROA for AS399494, maxLength 21.

670 of 673

ROA: none

216.46.158.0/24

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

670 of 673

Route objects not announced

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