bgpreport

Network · data from 2026-11-12

AS265693 Caldas Data Company LTDA

Registry name: AS265693 - Caldas Data Company LTDA, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265693, 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.253.76.0/23 Valid Other IRR onlyRADB 5 1%low visibility 5
38.253.78.0/23 Valid Other IRR onlyRADB 5 1%low visibility 5
38.253.76.0/24 Valid Other IRR onlyRADB 1 0%low visibility 2
38.253.77.0/24 Valid Other IRR onlyRADB 1 0%low visibility 2
38.253.78.0/24 Valid Other IRR onlyRADB 1 0%low visibility 2
38.253.79.0/24 Valid Other IRR onlyRADB 1 0%low visibility 2
38.253.76.0/22 Valid RIR databaseARIN 670 100% 66
45.179.202.0/24 Valid RIR databaseLACNIC 670 100% 66
143.137.96.0/22 Valid RIR databaseLACNIC, RADB 670 100% 66
2803:7640::/32 Valid RIR databaseLACNIC 636 100% 67
143.137.96.0/23 Valid RIR databaseLACNIC 5 1%low visibility 5
143.137.98.0/23 Valid RIR databaseLACNIC 5 1%low visibility 5
143.137.96.0/24 Valid RIR databaseLACNIC, RADB 1 0%low visibility 2
143.137.97.0/24 Valid RIR databaseLACNIC, RADB 1 0%low visibility 2
143.137.98.0/24 Valid RIR databaseLACNIC, RADB 1 0%low visibility 2
143.137.99.0/24 Valid RIR databaseLACNIC 1 0%low visibility 2

AS-SET

AS265693'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 12 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR38.253.76.0/23Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR38.253.78.0/23Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR38.253.76.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR38.253.77.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR38.253.78.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR38.253.79.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

2803:7640:10::/44LACNICValid
2803:7640:20::/44LACNICValid
2803:7640:30::/44LACNICValid
2803:7640:40::/44LACNIC, RADBValid
2803:7640:60::/44LACNICValid
2803:7640:70::/44LACNICValid

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.