bgpreport

Network · data from 2026-11-12

AS36698 Fatbanana Broadband

Registry name: FATBANANA-BROADBAND - Fatbanana Broadband Inc., CA · PeeringDB

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

Announced routes

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

74.122.215.0/24 No ROA Nonecovered by 74.122.208.0/21 1 0%low visibility 1
205.150.124.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
207.176.142.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
207.176.226.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
207.176.229.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
216.94.9.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
216.94.40.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
216.95.238.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
74.122.208.0/21 No ROA RIR databaseARIN, RADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS36698: AS-RIGSTAR. 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 (AS36698 isn't in the set, or no route object for AS36698 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 objectsAS36698 in itNot covered
AS-RIGSTAR ARIN 1111 Yes 0

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: none9
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none74.122.215.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.1 of 673
Route object: none74.122.215.0/24No route object for it. A route object for 74.122.208.0/21 with origin AS36698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36698 in the RIR database for the space.1 of 673
ROA: none205.150.124.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR205.150.124.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none207.176.142.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR207.176.142.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none207.176.226.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR207.176.226.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none207.176.229.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR207.176.229.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none216.94.9.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR216.94.9.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none216.94.40.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR216.94.40.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none216.95.238.0/24No ROA covers it. Add a ROA for AS36698, maxLength 24.2 of 673
Route object: RIR216.95.238.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none74.122.208.0/21No ROA covers it. Add a ROA for AS36698, maxLength 21.1 of 673

Route objects not announced

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

206.174.207.0/24RADBNo ROA
208.118.98.0/23RADBNo ROA
2606:21c0::/32RADBNo 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.