bgpreport

Network · data from 2026-11-12

AS62948 ALSAT-WIRELESS

Registry name: ALRB - Air Link Rural Broadband, LLC, US · PeeringDB

11IPv4 routes 36.4% RPKI valid · 100.0% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
5No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS62948, seen from no peer

Announced routes

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

104.192.158.0/24 Invalid: origin RIR databaseARIN 30 4%low visibility 23
162.219.61.0/24 Invalid: origin RIR databaseARIN 30 4%low visibility 23
38.123.52.0/22 No ROA Other IRR onlyRADB 670 100% 68
44.46.20.0/24 No ROA Other IRR onlyRADB 670 100% 68
44.46.24.0/24 No ROA Other IRR onlyRADB 670 100% 68
198.212.36.0/24 No ROA RIR databaseARIN, RADB 670 100% 68
207.174.224.0/23 No ROA RIR databaseARIN 670 100% 68
65.110.32.0/21 Valid RIR databaseARIN 670 100% 68
74.119.4.0/22 Valid RIR databaseARIN 670 100% 68
162.254.128.0/22 Valid RIR databaseARIN 670 100% 68
209.131.232.0/22 Valid RIR databaseARIN 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS62948: AS62948:AS-ALL. 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 (AS62948 isn't in the set, or no route object for AS62948 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.

NameDatabaseASNsSets Route objectsAS62948 in itNot covered
AS62948:AS-ALL ARINlists itself further down 221,856 No 11

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

  • ROA: origin2
  • ROA: none5
  • Route object: RIR3
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin104.192.158.0/24ROAs covering it name AS62943, not AS62948. If AS62948 should announce it, add a ROA for AS62948.30 of 673
ROA: origin162.219.61.0/24ROAs covering it name AS62943, not AS62948. If AS62948 should announce it, add a ROA for AS62948.30 of 673
ROA: none38.123.52.0/22No ROA covers it. Add a ROA for AS62948, maxLength 22.670 of 673
Route object: RIR38.123.52.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.46.20.0/24No ROA covers it. Add a ROA for AS62948, maxLength 24.670 of 673
Route object: RIR44.46.20.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.46.24.0/24No ROA covers it. Add a ROA for AS62948, maxLength 24.670 of 673
Route object: RIR44.46.24.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.212.36.0/24No ROA covers it. Add a ROA for AS62948, maxLength 24.670 of 673
ROA: none207.174.224.0/23No ROA covers it. Add a ROA for AS62948, maxLength 23.670 of 673
AS-SET: own ASNAS62948:AS-ALLAS62948 isn't in AS62948:AS-ALL (ARIN) once expanded. Add AS62948 to it.

Route objects not announced

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

2602:fedb::/36ARINNo 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.