bgpreport

Network · data from 2026-11-12

AS61941 Enove Internet

Registry name: AS61941 - Enove Solucoes em Comunicacao Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61941, 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.
201.139.216.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
2804:1894::/32 Valid Other IRR onlyRADB, TC 634 100% 67
201.139.216.0/22 Valid Other IRR onlyRADB 208 31% 56
201.139.218.0/24 Valid Other IRR onlyRADB 208 31% 56
201.139.219.0/24 Valid Other IRR onlyRADB 208 31% 56
201.139.220.0/22 Valid Other IRR onlyRADB 208 31% 56

AS-SET

PeeringDB's irr_as_set for AS61941: AS61941. 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 (AS61941 isn't in the set, or no route object for AS61941 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 objectsAS61941 in itNot covered
AS61941 A single AS number, not a set: AS61941 (this network), 12 route objects.

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.

  • Route object: RIR6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR201.139.216.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:1894::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR201.139.216.0/22Route object only in RADB. Add it in the RIR database for the space.208 of 673
Route object: RIR201.139.218.0/24Route object only in RADB. Add it in the RIR database for the space.208 of 673
Route object: RIR201.139.219.0/24Route object only in RADB. Add it in the RIR database for the space.208 of 673
Route object: RIR201.139.220.0/22Route object only in RADB. Add it in the RIR database for the space.208 of 673

Route objects not announced

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

201.139.216.0/24RADBValid
201.139.217.0/24RADBValid
201.139.220.0/24RADBValid
201.139.221.0/24RADBValid
201.139.222.0/24RADBValid
201.139.223.0/24RADBValid

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.