bgpreport

Network · data from 2026-11-12

AS35682 BESTINTERNETSOLUTION-AS BEST INTERNET SOLUTION XK

Registry name: BESTINTERNETSOLUTION-AS BEST INTERNET SOLUTION XK, UZ · not in PeeringDB

13IPv4 routes 76.9% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS35682, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35682, 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.
5.182.26.0/24 No ROA RIR databaseRIPE 673 100% 66
45.138.159.0/24 No ROA RIR databaseRIPE 673 100% 66
95.130.227.0/24 No ROA RIR databaseRIPE 673 100% 66
45.92.173.0/24 Valid RIR databaseRIPE 673 100% 66
45.130.148.0/24 Valid RIR databaseRIPE 673 100% 66
45.138.158.0/24 Valid RIR databaseRIPE 673 100% 66
77.83.206.0/24 Valid RIR databaseRIPE 673 100% 66
138.249.7.0/24 Valid RIR databaseRIPE 673 100% 66
170.168.6.0/24 Valid RIR databaseRIPE 673 100% 66
176.101.56.0/24 Valid RIR databaseRIPE 673 100% 66
185.191.141.0/24 Valid RIR databaseRIPE 673 100% 66
185.217.131.0/24 Valid RIR databaseRIPE 673 100% 66
189.74.96.0/21 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS35682 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none5.182.26.0/24No ROA covers it. Add a ROA for AS35682, maxLength 24.673 of 673
ROA: none45.138.159.0/24No ROA covers it. Add a ROA for AS35682, maxLength 24.673 of 673
ROA: none95.130.227.0/24No ROA covers it. Add a ROA for AS35682, maxLength 24.673 of 673

Route objects not announced

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