bgpreport

Network · data from 2026-11-12

AS270654 CONECTA GOLD PROVEDORES DE ACESSO LTDA

Registry name: AS270654 - CONECTA GOLD PROVEDORES DE ACESSO LTDA, BR · PeeringDB

5IPv4 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
8No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS270654, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270654, 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:6f58:3::/48 No ROA Nonecovered by 2804:6f58::/32 630 99% 67
2804:6f58:110::/44 No ROA Nonecovered by 2804:6f58::/32 630 99% 67
190.11.218.0/24 No ROA Other IRR onlyRADB 670 100% 67
190.11.216.0/22 No ROA Other IRR onlyALTDB, RADB, TC 668 99% 67
190.11.217.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.11.219.0/24 No ROA Other IRR onlyRADB 667 99% 67
190.11.216.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:6f58::/32 No ROA Other IRR onlyALTDB, RADB, TC 633 100% 67

AS-SET

AS270654'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 18 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:6f58:3::/48No ROA covers it. Add a ROA for AS270654, maxLength 48.630 of 636
Route object: none2804:6f58:3::/48No route object for it. A route object for 2804:6f58::/32 with origin AS270654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270654 in the RIR database for the space.630 of 636
ROA: none2804:6f58:110::/44No ROA covers it. Add a ROA for AS270654, maxLength 44.630 of 636
Route object: none2804:6f58:110::/44No route object for it. A route object for 2804:6f58::/32 with origin AS270654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270654 in the RIR database for the space.630 of 636
ROA: none190.11.218.0/24No ROA covers it. Add a ROA for AS270654, maxLength 24.670 of 673
Route object: RIR190.11.218.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none190.11.216.0/22No ROA covers it. Add a ROA for AS270654, maxLength 22.668 of 673
Route object: RIR190.11.216.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none190.11.217.0/24No ROA covers it. Add a ROA for AS270654, maxLength 24.667 of 673
Route object: RIR190.11.217.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.11.219.0/24No ROA covers it. Add a ROA for AS270654, maxLength 24.667 of 673
Route object: RIR190.11.219.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none190.11.216.0/24No ROA covers it. Add a ROA for AS270654, maxLength 24.666 of 673
Route object: RIR190.11.216.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:6f58::/32No ROA covers it. Add a ROA for AS270654, maxLength 32.633 of 636
Route object: RIR2804:6f58::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

190.11.216.0/23RADBNo ROA
190.11.218.0/23RADBNo 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.