bgpreport

Network · data from 2026-11-12

AS273755 AS273755 - VIVA NET TELECOM LTDA

Registry name: AS273755 - VIVA NET TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273755, 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.
38.9.210.0/23 No ROA None 212 32% 55
38.9.211.0/24 No ROA None 114 17% 46
177.131.109.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
38.9.210.0/24 No ROA Other IRR onlyRADB 141 21% 52
2804:8bbc::/33 Valid Nonecovered by 2804:8bbc::/32 634 100% 67
2804:8bbc:8000::/33 Valid Nonecovered by 2804:8bbc::/32 634 100% 67
2804:8bbc::/32 Valid Other IRR onlyTC 635 100% 69

AS-SET

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

  • ROA: none4
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.9.210.0/23No ROA covers it. Add a ROA for AS273755, maxLength 23.212 of 673
Route object: none38.9.210.0/23No route object for it. Add a route object with origin AS273755 in the RIR database for the space.212 of 673
ROA: none38.9.211.0/24No ROA covers it. Add a ROA for AS273755, maxLength 24.114 of 673
Route object: none38.9.211.0/24No route object for it. Add a route object with origin AS273755 in the RIR database for the space.114 of 673
ROA: none177.131.109.0/24No ROA covers it. Add a ROA for AS273755, maxLength 24.671 of 673
Route object: RIR177.131.109.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.9.210.0/24No ROA covers it. Add a ROA for AS273755, maxLength 24.141 of 673
Route object: RIR38.9.210.0/24Route object only in RADB. Add it in the RIR database for the space.141 of 673
Route object: none2804:8bbc::/33No route object for it. A route object for 2804:8bbc::/32 with origin AS273755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273755 in the RIR database for the space.634 of 636
Route object: none2804:8bbc:8000::/33No route object for it. A route object for 2804:8bbc::/32 with origin AS273755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273755 in the RIR database for the space.634 of 636
Route object: RIR2804:8bbc::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:8b0:d000::/36ALTDB, RADBNo 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.