bgpreport

Network · data from 2026-11-12

AS270385 CONECTA - PROVEDOR DE INTERNET LTDA.

Registry name: AS270385 - CONECTA - PROVEDOR DE INTERNET LTDA., BR · PeeringDB

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

Announced routes

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

190.89.80.0/24 No ROA Other IRR onlyRADB 670 100% 67
190.89.83.0/24 No ROA Other IRR onlyBBOI, NTTCOM, RADB 670 100% 67
190.89.82.0/24 No ROA Other IRR onlyRADB 666 99% 67
190.89.81.0/24 No ROA Other IRR onlyRADB 664 99% 66
2804:6b34::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:6b34:c000::/40 No ROA Other IRR onlyRADB 634 100% 67
2804:6b34:c400::/40 No ROA Other IRR onlyRADB 634 100% 67
2804:6b34:c500::/48 No ROA Other IRR onlyRADB 634 100% 67
2804:6b34:c600::/44 No ROA Other IRR onlyRADB 634 100% 67
2804:6b34:c100::/40 No ROA Other IRR onlyRADB 630 99% 67
2804:6b34:c200::/40 No ROA Other IRR onlyRADB 630 99% 69

AS-SET

AS270385'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 31 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none190.89.80.0/24No ROA covers it. Add a ROA for AS270385, maxLength 24.670 of 673
Route object: RIR190.89.80.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.89.83.0/24No ROA covers it. Add a ROA for AS270385, maxLength 24.670 of 673
Route object: RIR190.89.83.0/24Route object only in BBOI, NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.89.82.0/24No ROA covers it. Add a ROA for AS270385, maxLength 24.666 of 673
Route object: RIR190.89.82.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none190.89.81.0/24No ROA covers it. Add a ROA for AS270385, maxLength 24.664 of 673
Route object: RIR190.89.81.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none2804:6b34::/34No ROA covers it. Add a ROA for AS270385, maxLength 34.634 of 636
Route object: RIR2804:6b34::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6b34:c000::/40No ROA covers it. Add a ROA for AS270385, maxLength 40.634 of 636
Route object: RIR2804:6b34:c000::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6b34:c400::/40No ROA covers it. Add a ROA for AS270385, maxLength 40.634 of 636
Route object: RIR2804:6b34:c400::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6b34:c500::/48No ROA covers it. Add a ROA for AS270385, maxLength 48.634 of 636
Route object: RIR2804:6b34:c500::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6b34:c600::/44No ROA covers it. Add a ROA for AS270385, maxLength 44.634 of 636
Route object: RIR2804:6b34:c600::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6b34:c100::/40No ROA covers it. Add a ROA for AS270385, maxLength 40.630 of 636
Route object: RIR2804:6b34:c100::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
ROA: none2804:6b34:c200::/40No ROA covers it. Add a ROA for AS270385, maxLength 40.630 of 636
Route object: RIR2804:6b34:c200::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

190.89.80.0/22RADB, TCNo ROA
190.89.82.0/23RADBNo ROA
2804:6b34::/32RADB, TCNo ROA
2804:6b34:8000::/40RADBNo ROA
2804:6b34:8100::/40RADBNo ROA
2804:6b34:c400::/41RADBNo ROA
2804:6b34:c480::/41RADBNo ROA
2804:6b34:c500::/40RADBNo ROA
2804:6b34:c600::/40RADBNo 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.