Network · data from 2026-11-12

AS15005 Circle B Wireless

Registry name: CIRCLE-B - Circle B Wireless, US · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

4No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS15005, seen from no peer

Announced routes

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


38.80.64.0/23	No ROA	Other IRR onlyRADB	673 100%	67
38.196.180.0/24	No ROA	Other IRR onlyRADB	671 100%	69
38.27.1.0/24	No ROA	Other IRR onlyRADB	670 100%	67
38.65.118.0/24	No ROA	Other IRR onlyRADB	670 100%	67
2604:73c0:1000::/40	Valid	Nonecovered by 2604:73c0::/32	635 100%	67
23.152.204.0/24	Valid	RIR databaseARIN, RADB	673 100%	67

AS-SET

AS15005'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 11 are in fix.csv.

ROA: none4
Route object: none1
Route object: RIR4
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.80.64.0/23	No ROA covers it. Add a ROA for AS15005, maxLength 23.	673 of 673
Route object: RIR	38.80.64.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	38.196.180.0/24	No ROA covers it. Add a ROA for AS15005, maxLength 24.	671 of 673
Route object: RIR	38.196.180.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	38.27.1.0/24	No ROA covers it. Add a ROA for AS15005, maxLength 24.	670 of 673
Route object: RIR	38.27.1.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	38.65.118.0/24	No ROA covers it. Add a ROA for AS15005, maxLength 24.	670 of 673
Route object: RIR	38.65.118.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: none	2604:73c0:1000::/40	No route object for it. A route object for 2604:73c0::/32 with origin AS15005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15005 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.80.64.0/23

No ROA covers it. Add a ROA for AS15005, maxLength 23.

673 of 673

Route object: RIR

38.80.64.0/23

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

673 of 673

ROA: none

38.196.180.0/24

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

671 of 673

Route object: RIR

38.196.180.0/24

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

671 of 673

ROA: none

38.27.1.0/24

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

670 of 673

Route object: RIR

38.27.1.0/24

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

670 of 673

ROA: none

38.65.118.0/24

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

670 of 673

Route object: RIR

38.65.118.0/24

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

670 of 673

Route object: none

2604:73c0:1000::/40

No route object for it. A route object for 2604:73c0::/32 with origin AS15005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15005 in the RIR database for the space.

635 of 636

Route objects not announced

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


67.155.95.0/24	RADB	No ROA
2604:73c0::/32	ARIN, RADB	Valid

67.155.95.0/24

RADB

No ROA

2604:73c0::/32

ARIN, RADB

Valid

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.