bgpreport

Network · data from 2026-11-12

AS265833 AS265833 - COMUNICACIONES WIFI COLOMBIA S.A.S

Registry name: AS265833 - COMUNICACIONES WIFI COLOMBIA S.A.S, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265833, 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.
151.246.172.0/24 Valid Nonecovered by 151.246.172.0/23 671 100% 67
151.246.173.0/24 Valid Nonecovered by 151.246.172.0/23 671 100% 67
45.70.170.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66
45.70.171.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66
151.246.172.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
151.246.169.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
2803:dc20:600::/40 Valid RIR databaseLACNIC 635 100% 67
2803:dc20::/40 Valid RIR databaseLACNIC, RADB 605 95% 67
2803:dc20:400::/40 Valid RIR databaseLACNIC 605 95% 67
2803:dc20:800::/40 Valid RIR databaseLACNIC 605 95% 67
2803:dc20:a00::/40 Valid RIR databaseLACNIC 605 95% 67
2803:dc20:1000::/40 Valid RIR databaseLACNIC, RADB 605 95% 67

AS-SET

AS265833 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none151.246.172.0/24No route object for it. A route object for 151.246.172.0/23 with origin AS265833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265833 in the RIR database for the space.671 of 673
Route object: none151.246.173.0/24No route object for it. A route object for 151.246.172.0/23 with origin AS265833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265833 in the RIR database for the space.671 of 673

Route objects not announced

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

2803:dc20::/32LACNICValid
2803:dc20:200::/40LACNICValid

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.