bgpreport

Network · data from 2026-11-12

AS265437 tecnet provedor telecom ltda me

Registry name: AS265437 - INTERNET CORPORATE & SOLAR LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265437, 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.
168.195.176.0/24 Valid Nonecovered by 168.195.176.0/23 672 100% 66
168.195.178.0/24 Valid Nonecovered by 168.195.178.0/23 672 100% 66
168.195.177.0/24 Valid Nonecovered by 168.195.176.0/23 671 100% 66
168.195.179.0/24 Valid Nonecovered by 168.195.178.0/23 9 1%low visibility 8
168.195.176.0/23 Valid Other IRR onlyRADB 672 100% 66
168.195.178.0/23 Valid Other IRR onlyRADB 672 100% 66
168.195.176.0/22 Valid Other IRR onlyRADB 671 100% 66
2804:3420::/32 Valid Other IRR onlyRADB 635 100% 67
2804:3420::/33 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:3420:8000::/33 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS265437'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 10 are in fix.csv.

  • Route object: none4
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none168.195.176.0/24No route object for it. A route object for 168.195.176.0/23 with origin AS265437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265437 in the RIR database for the space.672 of 673
Route object: none168.195.178.0/24No route object for it. A route object for 168.195.178.0/23 with origin AS265437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265437 in the RIR database for the space.672 of 673
Route object: none168.195.177.0/24No route object for it. A route object for 168.195.176.0/23 with origin AS265437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265437 in the RIR database for the space.671 of 673
Route object: none168.195.179.0/24No route object for it. A route object for 168.195.178.0/23 with origin AS265437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265437 in the RIR database for the space.9 of 673
Route object: RIR168.195.176.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.195.178.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.195.176.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3420::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3420::/33Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:3420:8000::/33Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

Every route object with origin AS265437 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.