bgpreport

Network · data from 2026-11-12

AS269274 VIANET TELECOM

Registry name: AS269274 - VIANET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269274, 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:6214::/33 No ROA Nonecovered by 2804:6214::/32 634 100% 67
2804:6214:8000::/33 No ROA Nonecovered by 2804:6214::/32 634 100% 67
45.182.168.0/22 No ROA Other IRR onlyRADB, TC 670 100% 66
45.182.168.0/23 No ROA Other IRR onlyRADB 668 99% 66
45.182.170.0/23 No ROA Other IRR onlyRADB 668 99% 66
2804:6214::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS269274'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 12 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none2804:6214::/33No ROA covers it. Add a ROA for AS269274, maxLength 33.634 of 636
Route object: none2804:6214::/33No route object for it. A route object for 2804:6214::/32 with origin AS269274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269274 in the RIR database for the space.634 of 636
ROA: none2804:6214:8000::/33No ROA covers it. Add a ROA for AS269274, maxLength 33.634 of 636
Route object: none2804:6214:8000::/33No route object for it. A route object for 2804:6214::/32 with origin AS269274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269274 in the RIR database for the space.634 of 636
ROA: none45.182.168.0/22No ROA covers it. Add a ROA for AS269274, maxLength 22.670 of 673
Route object: RIR45.182.168.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none45.182.168.0/23No ROA covers it. Add a ROA for AS269274, maxLength 23.668 of 673
Route object: RIR45.182.168.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.182.170.0/23No ROA covers it. Add a ROA for AS269274, maxLength 23.668 of 673
Route object: RIR45.182.170.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:6214::/32No ROA covers it. Add a ROA for AS269274, maxLength 32.635 of 636
Route object: RIR2804:6214::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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