bgpreport

Network · data from 2026-11-12

AS269405 CONECT TEC TELECOMUNICACOES LTDA

Registry name: AS269405 - CONECT TEC TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269405, 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:6418:fec1::/48 Invalid: maxLength Nonecovered by 2804:6418::/32 76 12% 38
45.185.227.0/24 Valid Nonecovered by 45.185.224.0/22 670 100% 67
45.185.224.0/24 Valid Nonecovered by 45.185.224.0/22 669 99% 67
45.185.225.0/24 Valid Nonecovered by 45.185.224.0/22 665 99% 67
45.185.226.0/24 Valid Nonecovered by 45.185.224.0/22 665 99% 67
2804:6418:4000::/39 Valid Nonecovered by 2804:6418::/32 634 100% 67
2804:6418::/32 Valid Other IRR onlyRADB 633 100% 67

AS-SET

AS269405's PeeringDB record names no 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 9 are in fix.csv.

  • ROA: maxLength1
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:6418:fec1::/48ROA 2804:6418::/32 AS269405 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2804:6418:fec1::/48.76 of 636
Route object: none2804:6418:fec1::/48No route object for it. A route object for 2804:6418::/32 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.76 of 636
Route object: none45.185.227.0/24No route object for it. A route object for 45.185.224.0/22 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.670 of 673
Route object: none45.185.224.0/24No route object for it. A route object for 45.185.224.0/22 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.669 of 673
Route object: none45.185.225.0/24No route object for it. A route object for 45.185.224.0/22 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.665 of 673
Route object: none45.185.226.0/24No route object for it. A route object for 45.185.224.0/22 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.665 of 673
Route object: none2804:6418:4000::/39No route object for it. A route object for 2804:6418::/32 with origin AS269405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269405 in the RIR database for the space.634 of 636
Route object: RIR2804:6418::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.185.224.0/22RADBNo 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.