bgpreport

Network · data from 2026-11-12

AS266877 COLOMBIATEL TELECOMUNICACIONES

Registry name: AS266877 - COLOMBIATEL TELECOMUNICACIONES, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266877, 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:de80:2000::/38 Valid Nonecovered by 2803:de80:2000::/36 636 100% 67
2803:de80:1003::/48 Valid Nonecovered by 2803:de80::/32 632 99% 67
2803:de80:1057::/48 Valid Nonecovered by 2803:de80::/32 632 99% 67
2803:de80:1058::/48 Valid Nonecovered by 2803:de80::/32 632 99% 67
2803:de80:1059::/48 Valid Nonecovered by 2803:de80::/32 632 99% 67
2803:de80:1061::/48 Valid Nonecovered by 2803:de80::/32 632 99% 67
2803:de80:1062::/48 Valid Nonecovered by 2803:de80::/32 631 99% 67
2803:de80:1063::/48 Valid Nonecovered by 2803:de80::/32 630 99% 67
2803:de80::/38 Valid Nonecovered by 2803:de80::/32 583 92% 66
152.231.24.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
152.231.31.0/24 Valid RIR databaseLACNIC 672 100% 67
38.4.152.0/21 Valid RIR databaseARIN, RADB 670 100% 67
38.4.152.0/24 Valid RIR databaseARIN 669 99% 67
38.4.154.0/24 Valid RIR databaseARIN 669 99% 67
38.4.155.0/24 Valid RIR databaseARIN 669 99% 67
38.4.156.0/24 Valid RIR databaseARIN 669 99% 67
152.231.25.0/24 Valid RIR databaseLACNIC 664 99% 66
152.231.27.0/24 Valid RIR databaseLACNIC, RADB 664 99% 66
152.231.28.0/24 Valid RIR databaseLACNIC, RADB 664 99% 66

AS-SET

AS266877'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 20 are in fix.csv.

  • Route object: none9
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none2803:de80:2000::/38No route object for it. A route object for 2803:de80:2000::/36 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.636 of 636
Route object: none2803:de80:1003::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.632 of 636
Route object: none2803:de80:1057::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.632 of 636
Route object: none2803:de80:1058::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.632 of 636
Route object: none2803:de80:1059::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.632 of 636
Route object: none2803:de80:1061::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.632 of 636
Route object: none2803:de80:1062::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.631 of 636
Route object: none2803:de80:1063::/48No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.630 of 636
Route object: none2803:de80::/38No route object for it. A route object for 2803:de80::/32 with origin AS266877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266877 in the RIR database for the space.583 of 636

Route objects not announced

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

38.4.153.0/24ARINValid
38.4.157.0/24ARINValid
38.4.158.0/24ARINValid
38.4.159.0/24ARINValid
38.226.221.0/24ARINInvalid: origin
152.231.24.0/21RADBNo ROA
152.231.26.0/24LACNICValid
152.231.29.0/24LACNICValid
2803:de80::/32LACNIC, RADBValid
2803:de80:1001::/48RADBValid
2803:de80:2000::/36RADBValid

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.