Network · data from 2026-11-12

AS62516 ABB-ASN - Alamo Broadband Inc.

Registry name: ABB-ASN - Alamo Broadband Inc., US · not in PeeringDB

6IPv4 routes 33.3% 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

3Route objects not announced registered with origin AS62516, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62516, 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.103.216.0/23	No ROA	Other IRR onlyRADB	670 100%	68
38.103.218.0/23	No ROA	Other IRR onlyRADB	670 100%	68
38.128.144.0/22	No ROA	Other IRR onlyRADB	670 100%	68
38.128.160.0/21	No ROA	Other IRR onlyRADB	670 100%	68
23.140.104.0/24	Valid	RIR databaseARIN, RADB	670 100%	68
169.128.84.0/22	Valid	RIR databaseARIN, RADB	670 100%	68
2604:4940::/32	Valid	RIR databaseARIN	635 100%	69

AS-SET

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

ROA: none4
Route object: RIR4
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.103.216.0/23	No ROA covers it. Add a ROA for AS62516, maxLength 23.	670 of 673
Route object: RIR	38.103.216.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	38.103.218.0/23	No ROA covers it. Add a ROA for AS62516, maxLength 23.	670 of 673
Route object: RIR	38.103.218.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	38.128.144.0/22	No ROA covers it. Add a ROA for AS62516, maxLength 22.	670 of 673
Route object: RIR	38.128.144.0/22	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	38.128.160.0/21	No ROA covers it. Add a ROA for AS62516, maxLength 21.	670 of 673
Route object: RIR	38.128.160.0/21	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

ROA: none

38.103.216.0/23

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

670 of 673

Route object: RIR

38.103.216.0/23

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

670 of 673

ROA: none

38.103.218.0/23

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

670 of 673

Route object: RIR

38.103.218.0/23

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

670 of 673

ROA: none

38.128.144.0/22

No ROA covers it. Add a ROA for AS62516, maxLength 22.

670 of 673

Route object: RIR

38.128.144.0/22

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

670 of 673

ROA: none

38.128.160.0/21

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

670 of 673

Route object: RIR

38.128.160.0/21

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

670 of 673

Route objects not announced

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


38.103.216.0/22	RADB	No ROA
199.193.218.0/24	RADB	No ROA
199.193.219.0/24	RADB	No ROA

38.103.216.0/22

RADB

No ROA

199.193.218.0/24

RADB

No ROA

199.193.219.0/24

RADB

No ROA

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.