bgpreport

Network · data from 2026-11-12

AS61793 AS61793 - ELLONET SOLUCOES EM TECNOLOGIA LTDA - ME

Registry name: AS61793 - ELLONET SOLUCOES EM TECNOLOGIA LTDA - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61793, 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:1968:8000::/33 No ROA Nonecovered by 2804:1968::/32 631 99% 67
2804:1968:8000::/40 No ROA Nonecovered by 2804:1968::/32 627 99% 67
2804:1968:8a00::/40 No ROA Nonecovered by 2804:1968::/32 627 99% 67
201.130.28.0/23 No ROA Other IRR onlyRADB 667 99% 67
201.130.30.0/23 No ROA Other IRR onlyRADB 667 99% 67
201.130.28.0/24 No ROA Other IRR onlyRADB 665 99% 67
201.130.29.0/24 No ROA Other IRR onlyRADB 665 99% 67
201.130.30.0/24 No ROA Other IRR onlyRADB 664 99% 67
201.130.31.0/24 No ROA Other IRR onlyRADB 664 99% 67

AS-SET

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

  • ROA: none9
  • Route object: none3
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:1968:8000::/33No ROA covers it. Add a ROA for AS61793, maxLength 33.631 of 636
Route object: none2804:1968:8000::/33No route object for it. A route object for 2804:1968::/32 with origin AS61793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61793 in the RIR database for the space.631 of 636
ROA: none2804:1968:8000::/40No ROA covers it. Add a ROA for AS61793, maxLength 40.627 of 636
Route object: none2804:1968:8000::/40No route object for it. A route object for 2804:1968::/32 with origin AS61793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61793 in the RIR database for the space.627 of 636
ROA: none2804:1968:8a00::/40No ROA covers it. Add a ROA for AS61793, maxLength 40.627 of 636
Route object: none2804:1968:8a00::/40No route object for it. A route object for 2804:1968::/32 with origin AS61793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61793 in the RIR database for the space.627 of 636
ROA: none201.130.28.0/23No ROA covers it. Add a ROA for AS61793, maxLength 23.667 of 673
Route object: RIR201.130.28.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none201.130.30.0/23No ROA covers it. Add a ROA for AS61793, maxLength 23.667 of 673
Route object: RIR201.130.30.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none201.130.28.0/24No ROA covers it. Add a ROA for AS61793, maxLength 24.665 of 673
Route object: RIR201.130.28.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none201.130.29.0/24No ROA covers it. Add a ROA for AS61793, maxLength 24.665 of 673
Route object: RIR201.130.29.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none201.130.30.0/24No ROA covers it. Add a ROA for AS61793, maxLength 24.664 of 673
Route object: RIR201.130.30.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none201.130.31.0/24No ROA covers it. Add a ROA for AS61793, maxLength 24.664 of 673
Route object: RIR201.130.31.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673

Route objects not announced

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

201.130.28.0/22ALTDB, RADBNo ROA
2804:1968::/32ALTDB, 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.