bgpreport

Network · data from 2026-11-12

AS61729 CB NET TELECOM

Registry name: AS61729 - CB NET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61729, 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.

131.0.204.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
45.168.128.0/22 No ROA Other IRR onlyTC 671 100% 66
2804:1b74::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
45.168.128.0/23 No ROA Other IRR onlyTC 147 22% 49
45.168.130.0/23 No ROA Other IRR onlyTC 147 22% 49
131.0.204.0/23 No ROA Other IRR onlyRADB 147 22% 49
131.0.206.0/23 No ROA Other IRR onlyRADB 147 22% 49
2804:1b74::/33 No ROA Other IRR onlyRADB 60 9%low visibility 32
2804:1b74:8000::/33 No ROA Other IRR onlyRADB 60 9%low visibility 32
2804:1b74:200::/40 No ROA Other IRR onlyRADB 59 9%low visibility 32

AS-SET

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

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none131.0.204.0/22No ROA covers it. Add a ROA for AS61729, maxLength 22.672 of 673
Route object: RIR131.0.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.168.128.0/22No ROA covers it. Add a ROA for AS61729, maxLength 22.671 of 673
Route object: RIR45.168.128.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:1b74::/32No ROA covers it. Add a ROA for AS61729, maxLength 32.635 of 636
Route object: RIR2804:1b74::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none45.168.128.0/23No ROA covers it. Add a ROA for AS61729, maxLength 23.147 of 673
Route object: RIR45.168.128.0/23Route object only in TC. Add it in the RIR database for the space.147 of 673
ROA: none45.168.130.0/23No ROA covers it. Add a ROA for AS61729, maxLength 23.147 of 673
Route object: RIR45.168.130.0/23Route object only in TC. Add it in the RIR database for the space.147 of 673
ROA: none131.0.204.0/23No ROA covers it. Add a ROA for AS61729, maxLength 23.147 of 673
Route object: RIR131.0.204.0/23Route object only in RADB. Add it in the RIR database for the space.147 of 673
ROA: none131.0.206.0/23No ROA covers it. Add a ROA for AS61729, maxLength 23.147 of 673
Route object: RIR131.0.206.0/23Route object only in RADB. Add it in the RIR database for the space.147 of 673
ROA: none2804:1b74::/33No ROA covers it. Add a ROA for AS61729, maxLength 33.60 of 636
Route object: RIR2804:1b74::/33Route object only in RADB. Add it in the RIR database for the space.60 of 636
ROA: none2804:1b74:8000::/33No ROA covers it. Add a ROA for AS61729, maxLength 33.60 of 636
Route object: RIR2804:1b74:8000::/33Route object only in RADB. Add it in the RIR database for the space.60 of 636
ROA: none2804:1b74:200::/40No ROA covers it. Add a ROA for AS61729, maxLength 40.59 of 636
Route object: RIR2804:1b74:200::/40Route object only in RADB. Add it in the RIR database for the space.59 of 636

Route objects not announced

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

45.168.128.0/24TCNo ROA
45.168.129.0/24TCNo ROA
45.168.130.0/24TCNo ROA
45.168.131.0/24TCNo ROA
131.0.205.0/24RADBNo ROA
131.0.206.0/24RADBNo ROA
131.0.207.0/24RADBNo ROA
2804:1b74::/34RADBNo ROA
2804:1b74:100::/40RADBNo ROA
2804:1b74:300::/40RADBNo ROA
2804:1b74:1300::/40RADBNo ROA
2804:1b74:2400::/40RADBNo ROA
2804:1b74:4000::/34RADBNo ROA
2804:1b74:8000::/34RADBNo ROA
2804:1b74: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.