bgpreport

Network · data from 2026-11-12

AS30539 Flowfinity Wireless Inc

Registry name: FLOWFINITY - Flowfinity Wireless Inc, CA · PeeringDB

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

Announced routes

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

192.40.100.0/23 No ROA Other origin onlycovered by 192.40.96.0/21 671 100% 67
192.40.102.0/24 No ROA Nonecovered by 192.40.96.0/21 671 100% 67
199.101.212.0/24 No ROA Other origin onlycovered by 199.101.212.0/22 671 100% 68
192.40.98.0/24 No ROA Nonecovered by 192.40.96.0/21 670 100% 68
2620:103:2008::/46 No ROA Nonecovered by 2620:103:2000::/44 635 100% 69
2620:103:200f::/48 No ROA Nonecovered by 2620:103:2000::/44 634 100% 69
192.40.99.0/24 No ROA Nonecovered by 192.40.96.0/21 164 24% 54
199.101.213.0/24 No ROA Other IRR onlyRADB 671 100% 67
199.101.215.0/24 No ROA Other IRR onlyRADB 671 100% 67
192.40.96.0/21 No ROA RIR databaseARIN 671 100% 68
199.101.212.0/22 No ROA RIR databaseARIN, RADB 671 100% 68

AS-SET

AS30539's PeeringDB record names no 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 23 are in fix.csv.

  • ROA: none11
  • Route object: none7
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none192.40.100.0/23No ROA covers it. Add a ROA for AS30539, maxLength 23.671 of 673
Route object: none192.40.100.0/23Route objects for it name AS13768. A route object for 192.40.96.0/21 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.671 of 673
ROA: none192.40.102.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.671 of 673
Route object: none192.40.102.0/24No route object for it. A route object for 192.40.96.0/21 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.671 of 673
ROA: none199.101.212.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.671 of 673
Route object: none199.101.212.0/24Route objects for it name AS13768. A route object for 199.101.212.0/22 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.671 of 673
ROA: none192.40.98.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.670 of 673
Route object: none192.40.98.0/24No route object for it. A route object for 192.40.96.0/21 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.670 of 673
ROA: none2620:103:2008::/46No ROA covers it. Add a ROA for AS30539, maxLength 46.635 of 636
Route object: none2620:103:2008::/46No route object for it. A route object for 2620:103:2000::/44 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.635 of 636
ROA: none2620:103:200f::/48No ROA covers it. Add a ROA for AS30539, maxLength 48.634 of 636
Route object: none2620:103:200f::/48No route object for it. A route object for 2620:103:2000::/44 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.634 of 636
ROA: none192.40.99.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.164 of 673
Route object: none192.40.99.0/24No route object for it. A route object for 192.40.96.0/21 with origin AS30539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30539 in the RIR database for the space.164 of 673
ROA: none199.101.213.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.671 of 673
Route object: RIR199.101.213.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.101.215.0/24No ROA covers it. Add a ROA for AS30539, maxLength 24.671 of 673
Route object: RIR199.101.215.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.40.96.0/21No ROA covers it. Add a ROA for AS30539, maxLength 21.671 of 673
ROA: none199.101.212.0/22No ROA covers it. Add a ROA for AS30539, maxLength 22.671 of 673

Route objects not announced

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

198.245.176.0/23RADBNo ROA
199.101.214.0/24RADBNo ROA
2620:103:2000::/44ARINNo 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.