bgpreport

Network · data from 2026-11-12

AS61762 CONECTABR SISTEMAS DE COMUNICAÇÕES LTDA

Registry name: AS61762 - CONECTABR SISTEMAS DE COMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61762, 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.172.0/23 No ROA Nonecovered by 201.139.172.0/22 671 100% 66
201.139.172.0/24 No ROA Nonecovered by 201.139.172.0/22 671 100% 66
201.139.173.0/24 No ROA Nonecovered by 201.139.172.0/22 670 100% 66
2804:18e8::/33 No ROA Nonecovered by 2804:18e8::/32 636 100% 67
2804:18e8:8000::/34 No ROA Nonecovered by 2804:18e8::/32 635 100% 67
201.139.175.0/24 No ROA Other IRR onlyRADB 671 100% 66
201.139.174.0/24 No ROA Other IRR onlyRADB 670 100% 66

AS-SET

PeeringDB's irr_as_set for AS61762: AS61762. 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 (AS61762 isn't in the set, or no route object for AS61762 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 objectsAS61762 in itNot covered
AS61762 A single AS number, not a set: AS61762 (this network), 6 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 18 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none201.139.172.0/23No ROA covers it. Add a ROA for AS61762, maxLength 23.671 of 673
Route object: none201.139.172.0/23No route object for it. A route object for 201.139.172.0/22 with origin AS61762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61762 in the RIR database for the space.671 of 673
ROA: none201.139.172.0/24No ROA covers it. Add a ROA for AS61762, maxLength 24.671 of 673
Route object: none201.139.172.0/24No route object for it. A route object for 201.139.172.0/22 with origin AS61762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61762 in the RIR database for the space.671 of 673
ROA: none201.139.173.0/24No ROA covers it. Add a ROA for AS61762, maxLength 24.670 of 673
Route object: none201.139.173.0/24No route object for it. A route object for 201.139.172.0/22 with origin AS61762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61762 in the RIR database for the space.670 of 673
ROA: none2804:18e8::/33No ROA covers it. Add a ROA for AS61762, maxLength 33.636 of 636
Route object: none2804:18e8::/33No route object for it. A route object for 2804:18e8::/32 with origin AS61762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61762 in the RIR database for the space.636 of 636
ROA: none2804:18e8:8000::/34No ROA covers it. Add a ROA for AS61762, maxLength 34.635 of 636
Route object: none2804:18e8:8000::/34No route object for it. A route object for 2804:18e8::/32 with origin AS61762 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61762 in the RIR database for the space.635 of 636
ROA: none201.139.175.0/24No ROA covers it. Add a ROA for AS61762, maxLength 24.671 of 673
Route object: RIR201.139.175.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none201.139.174.0/24No ROA covers it. Add a ROA for AS61762, maxLength 24.670 of 673
Route object: RIR201.139.174.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

201.139.172.0/22ALTDB, RADBNo ROA
201.139.174.0/23RADBNo ROA
2804:18e8::/32ALTDB, RADBNo ROA
2804:18e8:c000::/34RADBNo 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.