bgpreport

Network · data from 2026-11-12

AS268470 AS268470 - CONECTAR TELECOM BANDA LARGA LTDA

Registry name: AS268470 - CONECTAR TELECOM BANDA LARGA LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268470, 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.
45.161.179.0/24 Valid Nonecovered by 45.161.178.0/23 670 100% 67
45.161.176.0/24 Valid Nonecovered by 45.161.176.0/23 665 99% 67
45.161.177.0/24 Valid Nonecovered by 45.161.176.0/23 665 99% 67
45.161.178.0/24 Valid Nonecovered by 45.161.178.0/23 665 99% 67
45.161.176.0/23 Valid Other IRR onlyRADB 672 100% 67
45.161.178.0/23 Valid Other IRR onlyRADB 672 100% 67
2804:51b0::/32 Valid Other IRR onlyRADB 634 100% 67

AS-SET

AS268470 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 8 are in fix.csv.

  • Route object: none4
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none45.161.179.0/24No route object for it. A route object for 45.161.178.0/23 with origin AS268470 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268470 in the RIR database for the space.670 of 673
Route object: none45.161.176.0/24No route object for it. A route object for 45.161.176.0/23 with origin AS268470 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268470 in the RIR database for the space.665 of 673
Route object: none45.161.177.0/24No route object for it. A route object for 45.161.176.0/23 with origin AS268470 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268470 in the RIR database for the space.665 of 673
Route object: none45.161.178.0/24No route object for it. A route object for 45.161.178.0/23 with origin AS268470 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268470 in the RIR database for the space.665 of 673
Route object: RIR45.161.176.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.161.178.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:51b0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.161.176.0/22RADBValid

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.