bgpreport

Network · data from 2026-11-12

AS131199 NEXEON-AS-AP - Nexeon Technologies, Inc.

Registry name: NEXEON-AS-AP - Nexeon Technologies, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131199, 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.
107.175.102.0/24 No ROA Other origin only 673 100% 67
103.243.188.0/22 No ROA Other origin only 671 100% 69
118.103.188.0/22 No ROA Other origin only 671 100% 69
2404:1980::/32 No ROA Other origin only 634 100% 69
64.44.118.0/24 Valid None 673 100% 67
64.44.84.0/24 Valid None 671 100% 68
64.44.87.0/24 Valid None 671 100% 68
172.93.132.0/24 Valid None 671 100% 67
172.93.177.0/24 Valid None 671 100% 67
5.104.76.0/24 Valid RIR databaseRADB, RIPE 3 0%low visibility 3
192.166.245.0/24 Valid RIR databaseRADB, RIPE 3 0%low visibility 3

AS-SET

AS131199 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 13 are in fix.csv.

  • ROA: none4
  • Route object: none9
ChangePrefix or setDetailFull-table peers
ROA: none107.175.102.0/24No ROA covers it. Add a ROA for AS131199, maxLength 24.673 of 673
Route object: none107.175.102.0/24Route objects for it name AS20278. Add a route object with origin AS131199 in the RIR database for the space.673 of 673
ROA: none103.243.188.0/22No ROA covers it. Add a ROA for AS131199, maxLength 22.671 of 673
Route object: none103.243.188.0/22Route objects for it name AS20278. Add a route object with origin AS131199 in the RIR database for the space.671 of 673
ROA: none118.103.188.0/22No ROA covers it. Add a ROA for AS131199, maxLength 22.671 of 673
Route object: none118.103.188.0/22Route objects for it name AS7643, AS20278, AS38893. Add a route object with origin AS131199 in the RIR database for the space.671 of 673
ROA: none2404:1980::/32No ROA covers it. Add a ROA for AS131199, maxLength 32.634 of 636
Route object: none2404:1980::/32Route objects for it name AS20278, AS21245. Add a route object with origin AS131199 in the RIR database for the space.634 of 636
Route object: none64.44.118.0/24No route object for it. Add a route object with origin AS131199 in the RIR database for the space.673 of 673
Route object: none64.44.84.0/24No route object for it. Add a route object with origin AS131199 in the RIR database for the space.671 of 673
Route object: none64.44.87.0/24No route object for it. Add a route object with origin AS131199 in the RIR database for the space.671 of 673
Route object: none172.93.132.0/24No route object for it. Add a route object with origin AS131199 in the RIR database for the space.671 of 673
Route object: none172.93.177.0/24No route object for it. Add a route object with origin AS131199 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS131199 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.