bgpreport

Network · data from 2026-11-12

AS7961 RBC - Raw Bandwidth Communications, Inc.

Registry name: RBC - Raw Bandwidth Communications, Inc., US · not in PeeringDB

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

Announced routes

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

198.144.192.0/23 No ROA Nonecovered by 198.144.192.0/19 671 100% 68
198.144.196.0/23 No ROA Other origin onlycovered by 198.144.192.0/19 671 100% 68
198.144.196.0/24 No ROA Other origin onlycovered by 198.144.192.0/19 671 100% 68
66.181.128.0/20 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 67
198.144.192.0/19 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 67
204.75.32.0/19 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none198.144.192.0/23No ROA covers it. Add a ROA for AS7961, maxLength 23.671 of 673
Route object: none198.144.192.0/23No route object for it. A route object for 198.144.192.0/19 with origin AS7961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7961 in the RIR database for the space.671 of 673
ROA: none198.144.196.0/23No ROA covers it. Add a ROA for AS7961, maxLength 23.671 of 673
Route object: none198.144.196.0/23Route objects for it name AS32959. A route object for 198.144.192.0/19 with origin AS7961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7961 in the RIR database for the space.671 of 673
ROA: none198.144.196.0/24No ROA covers it. Add a ROA for AS7961, maxLength 24.671 of 673
Route object: none198.144.196.0/24Route objects for it name AS32959. A route object for 198.144.192.0/19 with origin AS7961 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7961 in the RIR database for the space.671 of 673
ROA: none66.181.128.0/20No ROA covers it. Add a ROA for AS7961, maxLength 20.673 of 673
Route object: RIR66.181.128.0/20Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.144.192.0/19No ROA covers it. Add a ROA for AS7961, maxLength 19.673 of 673
Route object: RIR198.144.192.0/19Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.75.32.0/19No ROA covers it. Add a ROA for AS7961, maxLength 19.673 of 673
Route object: RIR204.75.32.0/19Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

66.181.128.0/21ALTDBNo ROA
66.181.136.0/21ALTDBNo ROA
192.58.220.0/24ALTDB, NTTCOM, RADBNo ROA
192.67.166.0/24ALTDB, NTTCOM, RADBNo ROA
198.144.193.0/24RADBNo ROA
199.233.135.0/24ALTDB, NTTCOM, RADBNo ROA
204.89.252.0/24ALTDB, NTTCOM, RADBNo ROA
2607:f818::/32ALTDBNo 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.