bgpreport

Network · data from 2026-11-12

AS395559 Force Broadband

Registry name: FORCE-BROADBAND - Force Broadband LLC, US · PeeringDB

22IPv4 routes 63.6% 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
8No ROA 0 with no route object for this origin
14Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS395559, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS395559, 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.
162.216.68.0/23 No ROA Other IRR onlyRADB 671 100% 68
140.235.40.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
140.235.40.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
140.235.41.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
140.235.42.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
140.235.43.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
162.216.68.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
162.216.69.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
66.187.196.0/24 Valid RIR databaseARIN, RADB 671 100% 68
149.2.24.0/23 Valid RIR databaseARIN, RADB 671 100% 68
154.9.120.0/21 Valid RIR databaseARIN 671 100% 68
192.69.136.0/22 Valid RIR databaseARIN, RADB 671 100% 68
199.188.116.0/22 Valid RIR databaseARIN, RADB 671 100% 68
203.24.247.0/24 Valid RIR databaseARIN, RADB 671 100% 68
2605:b440::/32 Valid RIR databaseARIN, RADB 635 100% 69
192.69.136.0/24 Valid RIR databaseARIN 2 0%low visibility 2
192.69.137.0/24 Valid RIR databaseARIN 2 0%low visibility 2
192.69.138.0/24 Valid RIR databaseARIN 2 0%low visibility 2
192.69.139.0/24 Valid RIR databaseARIN 2 0%low visibility 2
199.188.116.0/24 Valid RIR databaseARIN 2 0%low visibility 2
199.188.117.0/24 Valid RIR databaseARIN 2 0%low visibility 2
199.188.118.0/24 Valid RIR databaseARIN 2 0%low visibility 2
199.188.119.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS395559: AS-FORCEBB. 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 (AS395559 isn't in the set, or no route object for AS395559 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 objectsAS395559 in itNot covered
AS-FORCEBB ARIN 1123 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 9 are in fix.csv.

  • ROA: none8
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none162.216.68.0/23No ROA covers it. Add a ROA for AS395559, maxLength 23.671 of 673
Route object: RIR162.216.68.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none140.235.40.0/22No ROA covers it. Add a ROA for AS395559, maxLength 22.671 of 673
ROA: none140.235.40.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673
ROA: none140.235.41.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673
ROA: none140.235.42.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673
ROA: none140.235.43.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673
ROA: none162.216.68.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673
ROA: none162.216.69.0/24No ROA covers it. Add a ROA for AS395559, maxLength 24.2 of 673

Route objects not announced

Every route object with origin AS395559 is announced.

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.