bgpreport

Network · data from 2026-11-12

AS206766 PROXYWING Travchis LLC

Registry name: PROXYWING Travchis LLC, US · not in PeeringDB

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

Announced routes

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

82.153.99.0/24 Valid Other IRR onlyRADB 673 100% 66
87.76.201.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
87.229.52.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
2.27.114.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
77.105.14.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
78.108.62.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.175.115.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.110.106.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
86.109.78.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
87.83.233.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
87.192.50.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
91.211.32.0/22 Valid RIR databaseRIPE 672 100% 67
92.62.240.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
109.122.2.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
146.103.27.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
166.0.15.0/24 Valid RIR databaseARIN, RADB 672 100% 67
188.209.133.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
188.255.227.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
195.3.146.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
212.180.122.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
212.189.39.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
217.147.166.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
31.59.198.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
36.255.94.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
45.12.80.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
64.7.248.0/22 Valid RIR databaseARIN 671 100% 66
77.246.211.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
82.38.13.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
87.76.168.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
91.199.166.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.62.36.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
169.40.114.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
188.255.198.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
217.217.31.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
13.141.20.0/23 Valid RIR databaseRADB, RIPE 670 100% 67
37.202.192.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
81.168.38.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
109.229.220.0/23 Valid RIR databaseRADB, RIPE 670 100% 67
140.233.186.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
62.84.163.0/24 Valid RIR databaseRADB, RIPE 669 99% 68

AS-SET

AS206766 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 1 are in fix.csv.

  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: RIR82.153.99.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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