bgpreport

Network · data from 2026-11-12

AS46970 ALLBANDCOMMUNICATIONS - Allband Communications Cooperative

Registry name: ALLBANDCOMMUNICATIONS - Allband Communications Cooperative, US · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 71.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS46970, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46970, 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.65.228.0/23 No ROA Other IRR onlyRADB 671 100% 67
38.77.154.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.103.122.0/24 No ROA Other IRR onlyRADB 670 100% 67
199.242.28.0/24 Valid Nonecovered by 199.242.28.0/22 671 100% 67
199.242.30.0/24 Valid Nonecovered by 199.242.28.0/22 671 100% 67
192.189.40.0/24 Valid RIR databaseARIN, RADB 671 100% 67
199.242.28.0/22 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.65.228.0/23No ROA covers it. Add a ROA for AS46970, maxLength 23.671 of 673
Route object: RIR38.65.228.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.77.154.0/24No ROA covers it. Add a ROA for AS46970, maxLength 24.670 of 673
Route object: RIR38.77.154.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.103.122.0/24No ROA covers it. Add a ROA for AS46970, maxLength 24.670 of 673
Route object: RIR38.103.122.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none199.242.28.0/24No route object for it. A route object for 199.242.28.0/22 with origin AS46970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46970 in the RIR database for the space.671 of 673
Route object: none199.242.30.0/24No route object for it. A route object for 199.242.28.0/22 with origin AS46970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46970 in the RIR database for the space.671 of 673

Route objects not announced

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

207.74.90.0/23ARINInvalid: origin
207.75.104.0/22ARINInvalid: origin

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.