bgpreport

Network · data from 2026-11-12

AS14091 THRIVE-SE2 - Thrive Operations, LLC

Registry name: THRIVE-SE2 - Thrive Operations, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14091, 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.31.192.0/24 No ROA Other origin onlycovered by 198.31.192.0/22 673 100% 67
198.31.193.0/24 No ROA Other origin onlycovered by 198.31.192.0/22 673 100% 67
198.31.194.0/24 No ROA Other origin onlycovered by 198.31.192.0/22 673 100% 67
198.31.195.0/24 No ROA Other origin onlycovered by 198.31.192.0/22 673 100% 67
198.31.196.0/24 No ROA Other origin onlycovered by 198.31.196.0/23 673 100% 67
198.31.197.0/24 No ROA Other origin onlycovered by 198.31.196.0/23 673 100% 67
162.216.32.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.216.33.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.216.34.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.216.35.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.216.36.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.138.187.0/24 No ROA Other IRR onlyRADB 673 100% 67
204.90.102.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS14091 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 32 are in fix.csv.

  • ROA: none13
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none198.31.192.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.192.0/24Route objects for it name AS46887. A route object for 198.31.192.0/22 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none198.31.193.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.193.0/24Route objects for it name AS46887. A route object for 198.31.192.0/22 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none198.31.194.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.194.0/24Route objects for it name AS46887. A route object for 198.31.192.0/22 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none198.31.195.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.195.0/24Route objects for it name AS46887. A route object for 198.31.192.0/22 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none198.31.196.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.196.0/24Route objects for it name AS46887. A route object for 198.31.196.0/23 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none198.31.197.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: none198.31.197.0/24Route objects for it name AS46887. A route object for 198.31.196.0/23 with origin AS14091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14091 in the RIR database for the space.673 of 673
ROA: none162.216.32.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR162.216.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.216.33.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR162.216.33.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.216.34.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR162.216.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.216.35.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR162.216.35.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.216.36.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR162.216.36.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.138.187.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR192.138.187.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.90.102.0/24No ROA covers it. Add a ROA for AS14091, maxLength 24.673 of 673
Route object: RIR204.90.102.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

64.46.96.0/20RADBNo ROA
74.220.93.0/24ARINValid
192.216.132.0/24RADBNo ROA
198.31.192.0/22RADBNo ROA
198.31.196.0/23RADBNo ROA
208.83.132.0/22RADBNo 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.