Network · data from 2026-11-12

AS265185 VIANET LTDA ME

Registry name: AS265185 - VIANET LTDA ME, BR · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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 AS265185, seen from no peer

Announced routes

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


167.250.0.0/22	Valid	Other IRR onlyRADB, TC	672 100%	66
168.196.16.0/22	Valid	Other IRR onlyRADB, TC	672 100%	66
168.196.17.0/24	Valid	Other IRR onlyRADB, TC	672 100%	67
168.196.19.0/24	Valid	Other IRR onlyTC	672 100%	66
167.250.3.0/24	Valid	Other IRR onlyTC	671 100%	67
167.250.1.0/24	Valid	Other IRR onlyTC	669 99%	67
2804:2bf8::/32	Valid	Other IRR onlyRADB, TC	634 100%	67
167.250.0.0/23	Valid	Other IRR onlyTC	197 29%	54
167.250.2.0/23	Valid	Other IRR onlyTC	197 29%	54
168.196.16.0/23	Valid	Other IRR onlyTC	197 29%	54
168.196.18.0/23	Valid	Other IRR onlyTC	197 29%	54

AS-SET

AS265185'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 11 are in fix.csv.

Route object: RIR11

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	167.250.0.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	168.196.16.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	168.196.17.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	168.196.19.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	167.250.3.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	167.250.1.0/24	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:2bf8::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	167.250.0.0/23	Route object only in TC. Add it in the RIR database for the space.	197 of 673
Route object: RIR	167.250.2.0/23	Route object only in TC. Add it in the RIR database for the space.	197 of 673
Route object: RIR	168.196.16.0/23	Route object only in TC. Add it in the RIR database for the space.	197 of 673
Route object: RIR	168.196.18.0/23	Route object only in TC. Add it in the RIR database for the space.	197 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

167.250.0.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

168.196.16.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

168.196.17.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

168.196.19.0/24

Route object only in TC. Add it in the RIR database for the space.

672 of 673

Route object: RIR

167.250.3.0/24

Route object only in TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

167.250.1.0/24

Route object only in TC. Add it in the RIR database for the space.

669 of 673

Route object: RIR

2804:2bf8::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

634 of 636

Route object: RIR

167.250.0.0/23

Route object only in TC. Add it in the RIR database for the space.

197 of 673

Route object: RIR

167.250.2.0/23

Route object only in TC. Add it in the RIR database for the space.

197 of 673

Route object: RIR

168.196.16.0/23

Route object only in TC. Add it in the RIR database for the space.

197 of 673

Route object: RIR

168.196.18.0/23

Route object only in TC. Add it in the RIR database for the space.

197 of 673

Route objects not announced

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