bgpreport

Network · data from 2026-11-12

AS274350 RENOVE SOLUCOES DE TELECOMUNICACOES LTDA

Registry name: AS274350 - RENOVE SOLUCOES DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274350, 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:96a8:110::/44 Invalid: maxLength Nonecovered by 2804:96a8:100::/40 2 0%low visibility 1
186.196.100.0/24 Valid None 672 100% 67
186.196.101.0/24 Valid None 671 100% 67
2804:96a8::/40 Valid Other IRR onlyALTDB, TC 636 100% 67
2804:96a8:100::/40 Valid Other IRR onlyALTDB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS274350: ALTDB::AS274350:AS-RENOVEBR. 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 (AS274350 isn't in the set, or no route object for AS274350 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 objectsAS274350 in itNot covered
ALTDB::AS274350:AS-RENOVEBR ALTDB 2123 No 5

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: maxLength1
  • Route object: none3
  • Route object: RIR2
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:96a8:110::/44ROA 2804:96a8:100::/40 AS274350 has maxLength 40; the route is a /44. Raise the maxLength, or add a ROA for 2804:96a8:110::/44.2 of 636
Route object: none2804:96a8:110::/44No route object for it. A route object for 2804:96a8:100::/40 with origin AS274350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274350 in the RIR database for the space.2 of 636
Route object: none186.196.100.0/24No route object for it. Add a route object with origin AS274350 in the RIR database for the space.672 of 673
Route object: none186.196.101.0/24No route object for it. Add a route object with origin AS274350 in the RIR database for the space.671 of 673
Route object: RIR2804:96a8::/40Route object only in ALTDB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:96a8:100::/40Route object only in ALTDB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: own ASNALTDB::AS274350:AS-RENOVEBRAS274350 isn't in AS274350:AS-RENOVEBR (ALTDB) once expanded. Add AS274350 to it.

Route objects not announced

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

2804:96a8::/32TCNo 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.