bgpreport

Network · data from 2026-11-12

AS271201 Vianet Telecomunicações

Registry name: AS271201 - Vianet Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271201, 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.
179.49.184.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
179.49.185.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
179.49.186.0/24 No ROA Other IRR onlyRADB 668 99% 67
179.49.187.0/24 No ROA Other IRR onlyRADB 668 99% 67
179.49.186.0/23 No ROA Other IRR onlyRADB, TC 666 99% 67
2804:77d0::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:77d0::/33 No ROA Other IRR onlyRADB, TC 103 16% 40
2804:77d0:8000::/33 No ROA Other IRR onlyRADB, TC 103 16% 40
2804:77d0::/34 No ROA Other IRR onlyTC 3 0%low visibility 3
2804:77d0:4000::/34 No ROA Other IRR onlyTC 3 0%low visibility 3
2804:77d0:8000::/34 No ROA Other IRR onlyTC 3 0%low visibility 3
2804:77d0:c000::/34 No ROA Other IRR onlyTC 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS271201: AS271201:AS-GLOBAL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS271201 isn't in the set, or no route object for AS271201 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS271201 in itNot covered
AS271201:AS-GLOBAL TClists itself further down2 member sets in no database: AS264262:AS-GLOBAL, AS266486:AS-GLOBAL 87171,679 Yes 0

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

  • ROA: none12
  • Route object: RIR12
  • AS-SET: missing member2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none179.49.184.0/24No ROA covers it. Add a ROA for AS271201, maxLength 24.668 of 673
Route object: RIR179.49.184.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none179.49.185.0/24No ROA covers it. Add a ROA for AS271201, maxLength 24.668 of 673
Route object: RIR179.49.185.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none179.49.186.0/24No ROA covers it. Add a ROA for AS271201, maxLength 24.668 of 673
Route object: RIR179.49.186.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none179.49.187.0/24No ROA covers it. Add a ROA for AS271201, maxLength 24.668 of 673
Route object: RIR179.49.187.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none179.49.186.0/23No ROA covers it. Add a ROA for AS271201, maxLength 23.666 of 673
Route object: RIR179.49.186.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:77d0::/32No ROA covers it. Add a ROA for AS271201, maxLength 32.631 of 636
Route object: RIR2804:77d0::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:77d0::/33No ROA covers it. Add a ROA for AS271201, maxLength 33.103 of 636
Route object: RIR2804:77d0::/33Route object only in RADB, TC. Add it in the RIR database for the space.103 of 636
ROA: none2804:77d0:8000::/33No ROA covers it. Add a ROA for AS271201, maxLength 33.103 of 636
Route object: RIR2804:77d0:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.103 of 636
ROA: none2804:77d0::/34No ROA covers it. Add a ROA for AS271201, maxLength 34.3 of 636
Route object: RIR2804:77d0::/34Route object only in TC. Add it in the RIR database for the space.3 of 636
ROA: none2804:77d0:4000::/34No ROA covers it. Add a ROA for AS271201, maxLength 34.3 of 636
Route object: RIR2804:77d0:4000::/34Route object only in TC. Add it in the RIR database for the space.3 of 636
ROA: none2804:77d0:8000::/34No ROA covers it. Add a ROA for AS271201, maxLength 34.3 of 636
Route object: RIR2804:77d0:8000::/34Route object only in TC. Add it in the RIR database for the space.3 of 636
ROA: none2804:77d0:c000::/34No ROA covers it. Add a ROA for AS271201, maxLength 34.3 of 636
Route object: RIR2804:77d0:c000::/34Route object only in TC. Add it in the RIR database for the space.3 of 636
AS-SET: missing memberAS271201:AS-GLOBALAS271201:AS-GLOBAL (TC) lists AS264262:AS-GLOBAL; no IRR database read has it.
AS-SET: missing memberAS271201:AS-GLOBALAS271201:AS-GLOBAL (TC) lists AS266486:AS-GLOBAL; no IRR database read has it.

Route objects not announced

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

179.49.184.0/22RADB, TCNo ROA
179.49.184.0/23RADBNo 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.