bgpreport

Network · data from 2026-11-12

AS273526 AS273526 - VILANET TELECOMUNICACOES LTDA

Registry name: AS273526 - VILANET TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273526, 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.
189.89.255.0/24 No ROA Other IRR onlyTC 669 99% 67
2804:8ffc::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:8ffc::/33 No ROA Other IRR onlyRADB 634 100% 67
2804:8ffc:8000::/33 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

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

  • ROA: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none189.89.255.0/24No ROA covers it. Add a ROA for AS273526, maxLength 24.669 of 673
Route object: RIR189.89.255.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:8ffc::/32No ROA covers it. Add a ROA for AS273526, maxLength 32.634 of 636
Route object: RIR2804:8ffc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8ffc::/33No ROA covers it. Add a ROA for AS273526, maxLength 33.634 of 636
Route object: RIR2804:8ffc::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:8ffc:8000::/33No ROA covers it. Add a ROA for AS273526, maxLength 33.634 of 636
Route object: RIR2804:8ffc:8000::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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