bgpreport

Network · data from 2026-11-12

AS273656 OAC TECNOLOGIA LTDA

Registry name: AS273656 - OAC TECNOLOGIA EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273656, 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.
38.188.104.0/22 No ROA None 671 100% 67
38.226.118.0/23 No ROA None 671 100% 67
38.188.104.0/24 No ROA None 670 100% 67
38.188.105.0/24 No ROA None 670 100% 67
38.188.106.0/24 No ROA None 670 100% 67
38.188.107.0/24 No ROA None 670 100% 67
38.226.119.0/24 No ROA None 670 100% 67
2804:8a3c::/32 No ROA Other IRR onlyTC 633 100% 67
154.216.129.0/24 Valid RIR databaseAFRINIC 658 98% 67
154.216.130.0/24 Valid RIR databaseAFRINIC 658 98% 67

AS-SET

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

  • ROA: none8
  • Route object: none7
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.188.104.0/22No ROA covers it. Add a ROA for AS273656, maxLength 22.671 of 673
Route object: none38.188.104.0/22No route object for it. Add a route object with origin AS273656 in the RIR database for the space.671 of 673
ROA: none38.226.118.0/23No ROA covers it. Add a ROA for AS273656, maxLength 23.671 of 673
Route object: none38.226.118.0/23No route object for it. Add a route object with origin AS273656 in the RIR database for the space.671 of 673
ROA: none38.188.104.0/24No ROA covers it. Add a ROA for AS273656, maxLength 24.670 of 673
Route object: none38.188.104.0/24No route object for it. Add a route object with origin AS273656 in the RIR database for the space.670 of 673
ROA: none38.188.105.0/24No ROA covers it. Add a ROA for AS273656, maxLength 24.670 of 673
Route object: none38.188.105.0/24No route object for it. Add a route object with origin AS273656 in the RIR database for the space.670 of 673
ROA: none38.188.106.0/24No ROA covers it. Add a ROA for AS273656, maxLength 24.670 of 673
Route object: none38.188.106.0/24No route object for it. Add a route object with origin AS273656 in the RIR database for the space.670 of 673
ROA: none38.188.107.0/24No ROA covers it. Add a ROA for AS273656, maxLength 24.670 of 673
Route object: none38.188.107.0/24No route object for it. Add a route object with origin AS273656 in the RIR database for the space.670 of 673
ROA: none38.226.119.0/24No ROA covers it. Add a ROA for AS273656, maxLength 24.670 of 673
Route object: none38.226.119.0/24No route object for it. Add a route object with origin AS273656 in the RIR database for the space.670 of 673
ROA: none2804:8a3c::/32No ROA covers it. Add a ROA for AS273656, maxLength 32.633 of 636
Route object: RIR2804:8a3c::/32Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS273656 is announced.

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.