bgpreport

Network · data from 2026-11-12

AS265724 Teneda Corporacin CIA. LTDA

Registry name: AS265724 - Teneda Corporacion CIA. LTDA, EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265724, 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.
2803:9dc0::/33 Valid Nonecovered by 2803:9dc0::/32 634 100% 67
2803:9dc0:8000::/33 Valid Nonecovered by 2803:9dc0::/32 634 100% 67
45.6.224.0/24 Valid Nonecovered by 45.6.224.0/22 7 1%low visibility 4
45.6.225.0/24 Valid Other IRR onlyRADB 7 1%low visibility 4
45.6.226.0/24 Valid Other IRR onlyRADB 7 1%low visibility 4
45.6.227.0/24 Valid Other IRR onlyRADB 7 1%low visibility 4
45.6.224.0/22 Valid RIR databaseLACNIC 673 100% 67
45.171.109.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
2803:9dc0::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

AS265724'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 6 are in fix.csv.

  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2803:9dc0::/33No route object for it. A route object for 2803:9dc0::/32 with origin AS265724 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265724 in the RIR database for the space.634 of 636
Route object: none2803:9dc0:8000::/33No route object for it. A route object for 2803:9dc0::/32 with origin AS265724 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265724 in the RIR database for the space.634 of 636
Route object: none45.6.224.0/24No route object for it. A route object for 45.6.224.0/22 with origin AS265724 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265724 in the RIR database for the space.7 of 673
Route object: RIR45.6.225.0/24Route object only in RADB. Add it in the RIR database for the space.7 of 673
Route object: RIR45.6.226.0/24Route object only in RADB. Add it in the RIR database for the space.7 of 673
Route object: RIR45.6.227.0/24Route object only in RADB. Add it in the RIR database for the space.7 of 673

Route objects not announced

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