bgpreport

Network · data from 2026-11-12

AS268538 AS268538 - Conecta Network Telecom LTDA

Registry name: AS268538 - Conecta Network Telecom LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268538, 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:52bc::/33 No ROA Nonecovered by 2804:52bc::/32 74 12% 32
2804:52bc:8000::/33 No ROA Nonecovered by 2804:52bc::/32 74 12% 32
45.162.196.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 670 100% 66
2804:52bc::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 634 100% 67
45.162.196.0/23 No ROA Other IRR onlyRADB, TC 89 13% 33
45.162.198.0/23 No ROA Other IRR onlyRADB, TC 89 13% 33

AS-SET

AS268538 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 16 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:52bc::/33No ROA covers it. Add a ROA for AS268538, maxLength 33.74 of 636
Route object: none2804:52bc::/33No route object for it. A route object for 2804:52bc::/32 with origin AS268538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268538 in the RIR database for the space.74 of 636
ROA: none2804:52bc:8000::/33No ROA covers it. Add a ROA for AS268538, maxLength 33.74 of 636
Route object: none2804:52bc:8000::/33No route object for it. A route object for 2804:52bc::/32 with origin AS268538 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268538 in the RIR database for the space.74 of 636
ROA: none45.162.196.0/22No ROA covers it. Add a ROA for AS268538, maxLength 22.670 of 673
Route object: RIR45.162.196.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:52bc::/32No ROA covers it. Add a ROA for AS268538, maxLength 32.634 of 636
Route object: RIR2804:52bc::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none45.162.196.0/23No ROA covers it. Add a ROA for AS268538, maxLength 23.89 of 673
Route object: RIR45.162.196.0/23Route object only in RADB, TC. Add it in the RIR database for the space.89 of 673
ROA: none45.162.198.0/23No ROA covers it. Add a ROA for AS268538, maxLength 23.89 of 673
Route object: RIR45.162.198.0/23Route object only in RADB, TC. Add it in the RIR database for the space.89 of 673

Route objects not announced

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

45.162.196.0/24TCNo ROA
45.162.197.0/24TCNo ROA
45.162.198.0/24TCNo ROA
45.162.199.0/24TCNo 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.