bgpreport

Network · data from 2026-11-12

AS270919 VIANET TELECOM Brazil

Registry name: AS270919 - VIANET TELECOM LTDA, BR · PeeringDB

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

Announced routes

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

2804:7380:fe00::/40 No ROA Other IRR onlyRADB 635 100% 67
2804:7380:fe00::/41 Valid Nonecovered by 2804:7380:fe00::/40 3 0%low visibility 3
2804:7380:fe80::/41 Valid Nonecovered by 2804:7380:fe00::/40 3 0%low visibility 3
138.185.68.0/23 Valid Other IRR onlyRADB 672 100% 66
138.185.70.0/24 Valid Other IRR onlyRADB 672 100% 66
138.185.68.0/24 Valid Other IRR onlyRADB 669 99% 66
138.185.69.0/24 Valid Other IRR onlyRADB 669 99% 66
138.185.71.0/24 Valid Other IRR onlyRADB 668 99% 66
2804:7380::/33 Valid Other IRR onlyRADB 635 100% 69
2804:7380::/40 Valid Other IRR onlyRADB 635 100% 69
2804:7380:100::/40 Valid Other IRR onlyRADB 635 100% 69
2804:7380:ff00::/40 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS270919'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 15 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:7380:fe00::/40No ROA covers it. Add a ROA for AS270919, maxLength 40.635 of 636
Route object: RIR2804:7380:fe00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none2804:7380:fe00::/41No route object for it. A route object for 2804:7380:fe00::/40 with origin AS270919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270919 in the RIR database for the space.3 of 636
Route object: none2804:7380:fe80::/41No route object for it. A route object for 2804:7380:fe00::/40 with origin AS270919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270919 in the RIR database for the space.3 of 636
Route object: RIR138.185.68.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.68.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR138.185.69.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR138.185.71.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:7380::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:7380::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:7380:100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:7380:ff00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

138.185.68.0/22RADB, TCNo ROA
2804:7380::/32RADB, TCNo 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.